Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.relayer.fi/llms.txt

Use this file to discover all available pages before exploring further.

Relayer is the financial platform for stablecoin operators today, and the AI agents they’ll deploy tomorrow. Both layers run on the same self-custodial backend, with the same wallet workspaces, the same compliance, and the same budget enforcement.

​
The two layers

​
Today — stablecoin operators

If your business moves money in stablecoins — OTC desks, payroll, B2B remittance, treasury, payment processors — you need a backend that gives you:
  • Self-custodial wallets with passkey-based signing, so you never hold raw private keys and your users sign every transaction with biometrics
  • Regulated fiat rails with virtual accounts (CLABE/SPEI in Mexico, ACH in the US, more coming), KYB built in, recipient onboarding handled
  • A workspace where your team has individual passkeys, signing policies, approval thresholds, and full audit trail
This is what the Signing Kit and Payout Kit deliver. You can ship a compliant stablecoin product without writing a single line of custody, KYB, or compliance glue.

​
Tomorrow — AI agents that hold wallets

Your team will eventually deploy AI agents alongside human operators. Those agents will need to spend money — LLM tokens, third-party APIs, on-chain payments, x402-gated resources — and they’ll need a wallet to do it from. The hard problem is budget control: how do you let an LLM-driven agent transact autonomously without risking a runaway spend? The Agent Kit solves it with three layers of budget enforcement (infrastructure, tokens, payments) plus a kill switch, all enforced atomically server-side. If the SDK says “no budget”, the payment does not happen. No prompt-injection escape, no model-side override. The agent’s wallet is the same primitive as your team’s wallet. The signing policy that protects your CFO’s wallet also protects your agent’s. The approval flow that gates your operations team’s high-value transactions also gates the agent’s. One platform, two operators: humans and machines.

​
Shared primitives

What makes both layers work on the same backend:
PrimitiveUsed by humans forUsed by agents for
Wallet workspaceTeam’s funds, with team passkeysAgent’s funds, with HMAC-signed runtime auth
Signing policiesRestrict where the team can sendRestrict where the agent can send
ApprovalsCFO signs off on high-value transfersCFO signs off on agent’s threshold spends
BudgetsPer-wallet capsPer-agent caps across 3 layers
OrdersTrack every fiat settlementTrack every x402 payment
Audit logCompliance and reviewSame compliance and review

​
Kit architecture

You only integrate the Kits you need. They share authentication, workspace, and audit infrastructure underneath.

Signing Kit

Self-custodial wallets, prepare/confirm signing, passkeys, recovery, policies, approvals.

Payout Kit

Fiat on/off-ramp rails, virtual accounts, recipient management, and unified orders.

Agent Kit

Budget-enforced AI agents with USDC wallets, signing, and x402 payments.

Widget Kit

Embeddable React components for canonical protocols (swap, transfer, crosschain).

​
API design

All endpoints follow consistent patterns:
  • REST + JSON — standard HTTP methods and JSON request/response bodies
  • Versioned — all endpoints are prefixed with /v1
  • Consistent envelope — every response uses the same structure:
{
  "success": true,
  "message": "Success",
  "data": { },
  "statusCode": 200,
  "timestamp": "2026-03-28T12:00:00.000Z",
  "path": "/v1/signing/wallets"
}
  • Three auth modes — Authorization: ApiKey <key> for backend integrations, Authorization: Bearer <jwt> for browser callers from the dashboard, and X-Agent-Auth: <hmac> for runtime calls from the agent SDK. See Authentication for the full matrix.

​
Next Steps

Authentication

Set up your API key, understand the three auth modes, and learn about environments.

Quickstart

Make your first API call in under 5 minutes.