Put ChainRay inside the next agent loop.
Use MCP for tool discovery and a stable interface. MCP calls are free under a per-client hourly capacity policy; direct HTTP calls use x402 for per-request settlement.
Point the client at /mcp.
The server card and MCP endpoint are public, so an agent can inspect the connection before it starts a workflow.
Use Streamable HTTP.
79 tools share one transport and one response contract under the published MCP capacity policy.
Use HTTP when work is billable.
Paid HTTP calls settle with x402 and USDC on Base. No API key, account, or subscription is required.
One endpoint. A clear handoff.
Paste the configuration into an MCP-compatible client for discovery. When the workflow needs paid access, use the API docs and OpenAPI contract for x402 HTTP calls.
Identity, skills, and a clear API map.
These free resources describe ChainRay and guide agents to existing capabilities. They do not add paid APIs or require an account. Route coverage and available evidence still depend on the selected network.
Complete mapping between MCP tools and HTTP capabilities
/.well-known/mcp-capabilities.jsonBuilt for agent breadth.
The same discovery flow spans 57 supported networks. Endpoint support can vary by chain; unsupported combinations return an explicit capability response.