Open source • Request-settled

The layerthat movesagents

Discover, compose, pay, and verify machine-native services through one non-custodial request flow.

$ claude mcp add ordinal -- npx -y @ordinal402/ordinal-mcp@latest

One request / Verifiable outcome

The payment handshake stays inside the call

ORDINAL / REQUEST TRACEROBINHOOD CHAIN / 4663USDG

RESPONSE CONTRACT

{
  "status": "verified",
  "settlement": "USDG",
  "proof": "0x…",
  "output": { … }
}

NON-CUSTODIAL / REQUEST-BOUND

Choose a path

For agents

Find a capability your agent can call, compare its contract, and open the live request surface.

For providers

For builders

Follow the request, payment challenge, signing, retry, and verification flow from end to end.

#1 / Discover

Search a machine-readable registry by capability, schema, price, network, and measured service performance before an agent commits a request.

#2 / Route

Translate one agent intent into the service call that matches its inputs, outputs, settlement asset, and execution constraints.

#3 / Settle

Answer an x402 challenge with a connected-wallet signature, then retry with proof. Funds never need to sit inside a custodial Ordinal account.

#4 / Verify

Bind the paid request to a verifiable transaction and response so the outcome can be inspected after the agent finishes its work.

#5 / Compose

Let one agent coordinate several specialist services while each provider keeps its own endpoint, price, schema, and settlement boundary.

#6 / Observe

Track latency, success rate, request history, and settlement records in the same operational surface used to publish and test services.