Reference for domain terms used throughout the Relayer documentation.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.
A
Agent Kit The Relayer Kit that lets you ship budget-enforced AI agents — each agent holds a USDC wallet, can sign Solana transactions, and pays for x402-gated resources. Enforces a 3-layer budget guard plus a kill switch. Accessed via/v1/agents/*.
API Key
A secret credential that identifies an integrator workspace and authorizes requests to the Relayer API. Format: rk_client_key_v1_.... Passed in the Authorization: ApiKey <key> header.
Approval
A human-in-the-loop gate for signing. Transactions above a configured threshold enter a pending queue and must be approved (passkey-stamped) by an authorized team member before they are signed.
I
Integrator A workspace (operator or developer) building a product on top of Relayer. Each integrator has its own wallets, API keys, team, and signing policies. Multiple integrators can sit under the same operator account.K
Kit A domain-scoped module in the Relayer API. Each Kit covers a distinct area of functionality (Signing, Agent, Payout, Widget) and exposes its own set of endpoints under the/v1 prefix.
M
Metadata Mode The Widget Kit integration mode where the widget returns transaction routing and calldata to your application, and you sign and broadcast with your own wallet stack (MPC, HSM, MetaMask, etc.). Compare with Passkey Signing.O
Operator A business or developer who has an account with Relayer and integrates the API into their product. Operators receive an API key and configure which Kits and modules are active for their workspace.P
Passkey A WebAuthn credential bound to a user’s device (Face ID, fingerprint, security key). Used to authorize signing and approval actions. The passkey is the only thing that can authorize signing — it cannot be impersonated by an API key or HMAC secret. See Auth & Custody. Passkey Signing The Widget Kit integration mode where the user stamps each transaction with a passkey via WebAuthn. Keys live in a hardware enclave but are inert without the user’s passkey — Relayer does not custody. Compare with Metadata Mode. Payout Kit The Relayer Kit that handles fiat on/off-ramp, virtual accounts, recipient management, and settlement. Accessed via/v1/payout/* and /v1/orders.
Policy
See Signing Policy.
Pre-authorization
A bounded mandate granted by a passkey at setup time (typically by configuring policies + budgets + threshold for an agent). The agent can then act autonomously within those bounds via HMAC at runtime. Above the threshold, a fresh passkey stamp is required. Distinguishes Agent Kit from per-tx passkey signing.
S
Settlement The final transfer of funds that completes a transaction. In payout flows, settlement confirms fiat delivery to the recipient bank. Signing Kit The Relayer Kit that handles self-custodial wallet creation and transaction signing via passkeys. Private keys live inside a hardware-secured enclave — neither Relayer nor the integrator sees raw key material. Accessed via/v1/signing/* and /v1/transactions/*.
Signing Policy
A set of rules attached to a wallet or workspace that controls which transactions can be signed. Policies can restrict by value, destination address, token type, or time window. Enforced before any signing operation.
W
Widget Kit A set of React components and adapters that embed Relayer’s canonical protocol widgets (swap, transfer, crosschain) into a frontend application. Installable via npm —@relayerfi/widget-kit-react.
X
x402 HTTP status code 402 “Payment Required” — used by remote services to request a USDC payment before returning data. The Agent Kit ships anx402fetch helper that handles 402 detection, payment, and retry transparently.