Coin Railz · Service view
Multi-chain x402 micropayment infrastructure for AI agents. 60 pay-per-call API services for crypto analytics, trading signals, security audits, satellite data (NASA/ESA), real estate, banking, market intelligence, prediction markets, IoT/DePIN data, and AI inference. Native Coinbase Agentic Wallet compatible. Pay with USDC on Ethereum or Base - prices from $0.05 to $10.00 per request.
Manifest refresh updates matching endpoints, adds newly declared ones, and then queues reverification. Missing endpoints are left in place for safety instead of being auto-deleted.
No alternate registry records currently resolve to this service's public identity.
This service currently appears as a single-source public identity.
Hourly service-level snapshots are appended whenever endpoint/service health recomputes.
No observed service-level price history is available yet.
No observed service-level price history has been recorded yet.
Hourly Build 2 telemetry from provider-installed middleware. This is where revenue, conversion, latency, and agent traffic start compounding back into the registry.
No provider telemetry has been ingested for this service yet.
No endpoint-level analytics slices have been matched for this service yet.
No method-level telemetry yet.
No intent-level telemetry yet.
No agent cohorts have been derived for this service yet.
Trust distribution will appear once this service has recent agent traffic and trust history.
Strong recent payment history and the healthiest trust mix in the current traffic window.
Positive recent history, but still building toward stronger evidence and broader provider coverage.
Thin-file or watchlisted traffic that should usually stay under shadowing or small enforced rollouts first.
Traffic without enough shared history yet to earn a trust record.
Docker MCP Registry · POST /contracts/solidity/mcp
Docker MCP Registry · POST /contracts/cairo/mcp
Docker MCP Registry · POST /contracts/stylus/mcp
Docker MCP Registry · POST /contracts/stellar/mcp
Tempo RPC · POST /
1 of 1 route(s)
0 of 1 route(s)
0 of 1 route(s)
0 of 1 route(s)
0 of 1 route(s)
No approval or lease lifecycle events have been ingested yet.
Open route class
Trust enforcement telemetry appears once providers start recording advisory, shadow, or enforced trust decisions through the analytics pipeline.
No analytics alerts are open for this service right now.
No recent analytics events have been recorded for this service yet.
This Build 2 slice accepts provider telemetry through a service-scoped ingest key and rolls it up hourly for revenue, conversion, latency, and agent-activity views.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
1 endpoint(s) in this service have stale monitoring evidence.
POST
https://coinrailz.com/a2a/v1
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint still has usable evidence, but freshness or workflow proof is aging out.