Two tool bands, one URL
The server serves two disjoint tool bands, selected by the credential you connect with:The bands never overlap. An agent-key connection cannot see a management tool, and an
organization-key connection cannot see a spend tool — the server registers one band per
connection, so this is structural rather than a per-call permission check. An agent can therefore
never create, reconfigure, or unpause itself.
Server URL
Configuration
Available tools — agent band
For
check_balance and get_agent_status, spendable_now_cents and limited_by are nullable. If capacity cannot be read, both are null and capacity_unavailable is true; this optional boolean is omitted after a successful capacity read. Wallet holdings and account data are read separately from capacity. Treat null capacity as unknown and retry the capacity read later.
A $0 agent wallet does not block payments: Reinx funds it just in time. check_balance with amount_cents returns funding_check (amount_cents, org_can_fund, reason, checked_at). It is a coarse yes/no/unknown signal, exposes no treasury balance, and does not reserve funds. Funding is re-checked at execution; ORG_TREASURY_INSUFFICIENT is still possible.
Card-rail tools (
request_card_payment, request_spt) ship with the card launch, expanding
this band to 15 tools. A 16th, request_budget_increase, is deferred separately. Neither
affects the management band.Payment results
All MCP input and output fields use snake_case. The payment tools requireamount_cents and idempotency_key.
request_wallet_payment is the default; use submit_approval_request only when you deliberately want human review first. For a first payment to a new EVM address, provide caip2 as a CAIP-2 id or case-insensitive network name (arbitrum, base, optimism, polygon, solana). Do not guess: ask your human or the recipient. Omission uses this agent’s settled history only if it contains exactly one network, or infers Solana from the address format. An explicit choice always wins; new EVM recipients or ambiguous history return CHAIN_REQUIRED. Ask, then retry with the confirmed network and the same idempotency_key. Keep that same key after a timeout or UPSTREAM_ERROR too.
Read allowed_networks on get_spending_rules or get_agent_status for the environment’s alphabetical { name, display_name, caip2 } list. There is no default or recommended network. A failed read returns null with a note; do not invent a list.
An over-threshold request_wallet_payment normally returns status: pending and a request_id. A human decides and Reinx then runs the payment automatically. Poll get_payment_status with that handle while pending or executing, honoring retry_after_seconds. Confirmed on-chain finality is reported as settled, normally with on_chain_tx_hash. A recorded confirmation whose provider hash could not be captured is still final with a null hash; stop polling.
Executing is not settled. The next-poll delay is about 10 seconds for a new executing payment, then 30 seconds; pending starts at 30 seconds and backs off to 300 seconds as it waits. Use wait_seconds (integer 0–60, default 0) for an agent-side long-poll that returns early on a status or step change or a terminal result. Developer webhooks, including approval.completed, are today’s push option for your backend. MCP resource subscriptions are a later design path without a promised date.
See Payment Workflow for all seven wallet-poll statuses, recorded execution steps, and network selection fields (chain_caip2, chain_name, chain_source, chain_source_request_id, chain_source_settled_at).
Requirements
- Every tool call requires a valid API key.
- Every tool call requires a
purposefield (3–500 characters) explaining why the agent is acting — recorded for audit and scoring. - All calls are written to an immutable audit log.
Go deeper
Payment Workflow
The request → poll → learn loop, idempotency, and status semantics.
Tool Reference
Exact parameters and limits for every tool.
Management Band
The 21 tools an organization key sees — provisioning and reconfiguring agents.
Organization Keys
Scopes, container bindings, and quotas for machine principals.