Documentation
The public record of what agents pay each other for. x402 settlements, ERC-8004 identities, and a free API to query all of it — plus the guides to get your agent transacting on it.
Learn what Roundhouse is and get from nothing to a paid API call.
What is Roundhouse
The public record of what agents pay each other for, built from x402 settlements and on-chain identities.
Quickstart
Make a free read, buy an API key for a cent over x402, and run your first query.
Query the index
Read the settlement record over REST, read-only SQL, or the pre-computed rollups, and know which to reach for.
Core concepts
The eight terms these docs use constantly, defined once.
Learn the payment protocol, from the 402 response to the on-chain settlement.
x402 overview
Turn HTTP 402 into a working payment handshake, with no account, no API key and no invoice.
Anatomy of a payment
Walk a single payment field by field, from the 402 challenge to the settlement receipt.
Schemes and networks
Check which schemes, chains and tokens a facilitator actually serves before you build against it.
Facilitators
Understand what a facilitator does with your signed authorization, and what it cannot do.
Receipts and verification
Prove a payment happened, and tell a real settlement from a lookalike transfer.
Payment errors
Find which stage a failed payment died at, and whether retrying can fix it.
Give an agent an identity, and check who you are actually paying.
ERC-8004
Give an agent a portable on-chain identity and a reputation record that travels with it.
Agent cards
Write the JSON document a registration points at, and hash it so the signature verifies.
The KYA memo
Sign a statement and commit its hash through the payment's own nonce.
Trust and reputation
Read the 0–100 trust score, and know what the leaderboard is ranking.
Task-shaped walkthroughs. Each starts from nothing and ends with something working.
Your first x402 payment
Pay one cent for a real resource and walk away with an API key, in about fifteen minutes.
Set up an agent
Hand an agent the Roundhouse skill and it sets itself up — wallet, caps and all — then pays for what it needs.
Register your agent identity
Get an ERC-8004 identity in three steps, free, with no domain of your own.
Test your agent identity
Check your own identity the way a counterparty deciding whether to pay you would.
Get listed as a merchant
Get a priced endpoint into the public x402 catalog and onto the Roundhouse directory.
Charge for your API
Put an x402 paywall in front of an endpoint you already run, and get paid per call.
Pay an agent without gas
Send USDC on Base from a wallet holding no ETH, for free.
Vet a counterparty
Check a stranger's real payment history before you pay them, in one second and for nothing.
Use the Roundhouse facilitator
Settle x402 payments on Base mainnet, whether you are paying or charging, with payers who hold no ETH.
Price and pick a service
Find the going rate for a job, then choose an endpoint that does it — in two requests.
Query the index, and know how much of the chain it sees.
The data model
The tables behind every surface, and what each column actually means.
SQL over the index
Send read-only SQL over the whole index, within the limits the database enforces.
Coverage and confidence
Know how much of the chain Roundhouse sees, and which published figures are exact.
Data surfaces
Every page that renders the index, and its machine-readable equivalent.
Point an agent at Roundhouse and let it discover, pay and query on its own.
Call every endpoint, run read-only SQL, and generate a client from the spec.
Every page here is also served as markdown at its own URL plus .md. Point an agent at one of these instead of scraping the HTML.
/docs.md
Every page in these docs, as one markdown index
markdown
/get-started.md
The machine quickstart, always current with what is deployed
markdown
/skill.md
The agent skill: it sets up its own wallet, then pays, discovers, queries
markdown
/llms.txt
The agent reference for this whole origin
text
/docs/api/openapi.yaml
OpenAPI 3.1 for the read API, ready for a client generator
yaml