# CoRelayer

> Cooperative Relayer Infrastructure for Autonomous Transactions. Bring your users to MultiversX. Make blockchain adoption effortless. CoRelayer relays the transactions of apps and AI agents on MultiversX. You pay a plan in USDC, priced per transaction and never per user, and your plan covers the network fee. The sender signs each transaction once; a CoRelayer relayer in the sender's shard adds its signature, pays the fee and sends it.

Chain: MultiversX, chain id `1`.
API base: https://api.co-relayer.com
Application: https://app.co-relayer.com
Documentation: https://docs.co-relayer.com

Every page below is also served as Markdown at the same path with `.md` appended.

## Start here

1. Discover: [https://co-relayer.com/.well-known/corelayer.json](https://co-relayer.com/.well-known/corelayer.json) and [https://co-relayer.com/pricing.json](https://co-relayer.com/pricing.json). No key needed. Pin the chain id and the contract address before you sign anything.
2. Price: `GET https://api.co-relayer.com/v1/pricing` returns every plan and price as data; `POST https://api.co-relayer.com/v1/quote` prices one transaction.
3. Pay: inside an HTTP 402 exchange (x402), or sign the contract's `subscribe` call yourself. It is relayed free while the account has no plan to pay with; an account that can pay is billed in Relay Units. [Buying a plan](https://docs.co-relayer.com/agents/buying-a-plan)
4. Relay: `POST https://api.co-relayer.com/v1/relay/assign`, sign the transaction once, then `POST https://api.co-relayer.com/v1/relay`. [Agent quickstart](https://docs.co-relayer.com/agents/quickstart)

## Who pays for a sender

The sender's own plan, or a plan that lists it as a named wallet (per-plan limit). Or a sponsor key (`X-Api-Key`) held on a server, which pays for any sender whose key that server holds or reaches, within its contract allow-list, on Builder, Growth, Scale, Enterprise, Agent Pro and Agent Fleet. The presence proof on `POST /v1/relay/assign` is always a raw Ed25519 signature by the sender's own key: `proof.kind "key"`, or `"sponsor"` when a sponsor key pays for the relay. The assign route never reads `X-Api-Key`. [Sponsoring senders](https://docs.co-relayer.com/plans/sponsoring-senders)

## Product

- [Gasless transactions for MultiversX apps](https://co-relayer.com/): Bring your users to MultiversX. Make blockchain adoption effortless. One plan in USDC covers the network fee on the transactions your app signs for them, priced per transaction, never per user.
- [How it works](https://co-relayer.com/product): Your app signs, you pay one plan in USDC, and it covers the network fee. Pay for the wallets you run or the ones you name, the limits you control, and what happens when something goes wrong.
- [Pricing](https://co-relayer.com/pricing): Plans in USDC, priced per transaction and never per user. From Builder up, one sponsor key pays for every wallet your app runs. Agents can start with no monthly fee.
- [For AI agents](https://co-relayer.com/agents): Your agent finds CoRelayer, checks the price, pays in USDC and starts sending. No account and no monthly fee on Agent Metered. Its plan covers the network fee.
- [CoreLayer Units](https://co-relayer.com/token): What CoreLayer Units are for, how each CoRelayer sale reaches the pool, the supply and its allocation, and the pool's liquidity and volatility.

## Evidence

- [Network](https://co-relayer.com/network): CoRelayer’s relayer list, read straight from the chain, so you can check every relayer yourself.
- [Security](https://co-relayer.com/security): What a relayer can and can’t do with your transactions, how to check a relayer yourself, and how to report a vulnerability.
- [The delivery layer for the machine economy](https://co-relayer.com/finance-computer): Why software that pays should never have to run a gas balance, and where transaction delivery sits in a machine-to-machine financial stack.
- [Papers](https://co-relayer.com/papers): The CoRelayer whitepaper, the CoreLayer Units whitepaper, the one-pager and the API overview, each as a PDF in a dark edition for screens and a print edition.

## Build with it

- [Developers](https://co-relayer.com/developers): SDKs for TypeScript, Go, Rust and Python and a REST API, with quickstarts for sponsoring the wallets your app runs or sending from keys your code holds.
- [Brand and press kit](https://co-relayer.com/brand): CoRelayer logo files, colours, clear space, minimum sizes and the rules for using them — plus how we are allowed to refer to MultiversX.

## Legal

- [Terms of service](https://co-relayer.com/legal/terms): The agreement covering plans, credits, relaying and the limits of the service.
- [Privacy](https://co-relayer.com/legal/privacy): What CoRelayer stores about an account, why, for how long, and who can read it.
- [Payments and refunds](https://co-relayer.com/legal/refunds): Deposits become non-refundable credits. What that means before you pay, and what happens to unused transactions at the end of a period.
- [Imprint](https://co-relayer.com/legal/imprint): Who operates CoRelayer, how to reach a human about billing or security, and the statement that this is an independent project.

## Machine-readable

- [OpenAPI document](https://docs.co-relayer.com/openapi.yaml): the authority for every route, field and error name.
- [https://co-relayer.com/pricing.json](https://co-relayer.com/pricing.json): current plans and prices, and how a transaction is counted.
- [https://co-relayer.com/.well-known/corelayer.json](https://co-relayer.com/.well-known/corelayer.json): chain id, contract address and direct API hosts.
- [https://co-relayer.com/build-info.json](https://co-relayer.com/build-info.json): environment, chain and commit of this deployment.

## Notes for agents

- One user action is one signature. If the assigned relayer becomes unusable after you signed, the API answers `RESIGN_REQUIRED` and nothing was sent.
- Compare the chain id in `/.well-known/corelayer.json` with the chain id of the transaction you are about to sign. Addresses are identical across networks and are not a network identifier.
- Check the assigned relayer against the contract's relayer list, through a MultiversX gateway that is not ours, before signing.
- A transaction that runs and fails counts: the network charges its fee, and the relayer pays it. A transaction that never runs is not billed.
- Every price ceiling you sign (`max_price`, `max_renew_price`, `max_payg_price`) is enforced by the contract.
- We publish measured numbers only.