# Caplane

## Docs

- [Broker a capability from your agent](https://docs.caplane.xyz/builders/overview.md): Discover a price, sign one order, hand it to a permissionless relayer. The SDK path and the raw path, end to end.
- [Composes with, does not compete](https://docs.caplane.xyz/concepts/composes-with.md): Caplane settles underneath ERC-8004, beside x402, as an MCP tool, sourcing gas from Circle.
- [Honest limits](https://docs.caplane.xyz/concepts/honest-limits.md): The two declared landmines, stated plainly, and what Caplane deliberately does not do.
- [Security and threat model](https://docs.caplane.xyz/concepts/security.md): What you trust, what you need not, the invariants, and what a malicious relayer cannot do.
- [Caplane vs Nevermined](https://docs.caplane.xyz/concepts/vs-nevermined.md): No coordinator, no escrow, no redemption step in the settlement path.
- [What is Caplane](https://docs.caplane.xyz/index.md): A serverless, facilitator-free primitive: agents buy scarce on-chain capabilities from each other, payment and grant in one atomic transaction.
- [Sell a capability behind an adapter](https://docs.caplane.xyz/providers/overview.md): Implement two functions, gate the grant to the broker, price with quote, and get paid amount minus fee after the grant.
- [Adapters](https://docs.caplane.xyz/reference/adapters.md): Each shipped adapter's params schema, receipt, events, errors, and addresses.
- [Relayer API](https://docs.caplane.xyz/reference/api.md): POST /broker and GET /info: the wire schemas, the conventions, and a real example.
- [CapabilityBroker.brokerCapability](https://docs.caplane.xyz/reference/brokercapability.md): The single entry point: signature, parameters, returns, the flow, the event, and the revert.
- [Deployments](https://docs.caplane.xyz/reference/deployments.md): The live testnet contract addresses, each verifiable on the explorer.
- [Errors and reverts](https://docs.caplane.xyz/reference/errors.md): Every way a settlement reverts or a relayer rejects, in one table, with how to fix each.
- [ICapabilityAdapter](https://docs.caplane.xyz/reference/iadapter.md): The two-function interface every capability implements.
- [IERC3009](https://docs.caplane.xyz/reference/ierc3009.md): The EIP-3009 subset the broker calls to settle payment, and the EIP-712 domain to sign under.
- [Integration paths](https://docs.caplane.xyz/reference/integration-paths.md): Three ways to reach a settlement, all producing the identical on-chain result.
- [The Order struct](https://docs.caplane.xyz/reference/order.md): The eight fields, their exact types, and the order.nonce vs orderHash distinction.
- [Order encoding](https://docs.caplane.xyz/reference/order-encoding.md): The byte-exact abi.encode(order) layout. Get it wrong and every settlement reverts.
- [Reference](https://docs.caplane.xyz/reference/overview.md): Contracts, the byte-exact encoding, the SDK, adapters, the relayer API, errors, and deployments.
- [SDK (@caplane/shared)](https://docs.caplane.xyz/reference/sdk.md): The TypeScript surface for building, hashing, signing, and transmitting an order.
- [Run a relayer and earn the fee](https://docs.caplane.xyz/relayers/overview.md): Transmit signed orders as msg.sender, earn feeBps, hold only a gas key. No allowlist, no approval.
- [Changelog](https://docs.caplane.xyz/resources/changelog.md): What changed, and when. Dated, with verifiable links.
- [FAQ](https://docs.caplane.xyz/resources/faq.md): The questions a skeptical integrator asks, each routed to the page that answers it.
- [Status](https://docs.caplane.xyz/resources/status.md): What is live, on which chains, with the real settlements recorded so far.
- [How a brokerage settles](https://docs.caplane.xyz/start-here/how-it-settles.md): One transaction settles the payment, grants the capability, and pays out, or reverts.
- [Quickstart](https://docs.caplane.xyz/start-here/quickstart.md): Sign one order, submit one transaction, watch it settle on testnet. No account, no API key, no dashboard.
- [The binding](https://docs.caplane.xyz/start-here/the-binding.md): Why one signature ties payment to the order, and why a relayer cannot tamper with it.

## OpenAPI Specs

- [openapi](https://docs.caplane.xyz/api/openapi.json)