Can an agent trust Recta? The fee rule, keys, limits, and what is proven
What Recta can take, who holds the keys, the limits an agent can set, how versions are pinned, and exactly what has been proven with real money so far, and what has not.
The fee rule
- Asking is free. Recta charges only when the agent executes the cheaper route Recta proposed, and then exactly 5 % of the saving Recta verifies on chain after delivery, against the route the agent declared it would use anyway.
- No saving, no charge. If the saving turns out smaller than expected, the fee is smaller too.
- No prepayment, no credit, no account. The agent signs, with each decision, a Permit2 authorization capped at
max_fee_authorization; Recta's collection pulls only the verified 5 %, never more than that cap, in USDC on Base.
Who holds the keys and the funds
- Recta never receives a key and never holds funds. The agent's own wallet signs and sends every transaction.
- Where the key lives is the wallet's choice: a Coinbase CDP account keeps it at Coinbase; MetaMask Agent Wallet in server mode keeps it at MetaMask;
npx @recta/mcpwithRECTA_PRIVATE_KEYkeeps it on the agent's machine, in plain text in its configuration. Use a dedicated wallet that holds only what the agent may move. - What Recta can take is only what the fee permit you sign allows: the verified 5 %, up to the permit's cap.
Limits you control
Recta itself sets no maximum amount and delivers to the recipient your request names, so cap both on your side. @recta/mcp enforces these limits locally:
- before anything is signed (from version 0.1.14): it refuses a transfer above
RECTA_MAX_AMOUNT(default 1000 tokens), or to a recipient other than the wallet itself or an address inRECTA_ALLOWED_RECIPIENTS; - before the fee permit is signed: it refuses a permit above
RECTA_MAX_FEE_USDC(default 1 USDC); - before any transaction is sent: it refuses a route that does not guarantee the recipient at least 99 % of the amount (
RECTA_MIN_OUTPUT_BPS, default 9900), or whose transactions carry native value (RECTA_MAX_NATIVE_WEI, default 0); - the gas price ceilings it declares in the request are never above
RECTA_MAX_FEE_GWEI(default 50 gwei) andRECTA_MAX_PRIORITY_FEE_GWEI(default 2 gwei); - until you set
RECTA_ALLOW_EXECUTE=yesit signs only free requests: no fee permit and no transaction.
These limits protect against an agent acting through its tools, not against one that can edit the server's configuration or run commands. For a wallet-level barrier, use your wallet's own policy: Recta publishes the contracts and approvals to allow, and the packages refuse any transaction outside them (approvals of exactly the amount to the pinned Across, CCTP V2, Stargate and LayerZero OFT contracts, their deposit calls, and the bounded fee approval to Permit2 on Base).
Versions
- The request contract is versioned:
RECTA_COMMERCIAL_EVALUATION_CONTRACT_V23, published in the service descriptor. @recta/clientand@recta/mcppin Recta's routes, contracts and fee addresses per release, and refuse a service that no longer matches them.- Pin the exact package version you reviewed (no ranges, no
@latest). Both are open source (MIT, github.com/RectaBuild/recta) and published from GitHub Actions with npm provenance: check withnpm audit signatures.
Proven with real money
- The whole circuit, twice. Two transfers of about 10 USDC with Recta's own funds (Base to Arbitrum on 10 November 2026, Arbitrum to Base on 11 November): decision against the route declared, the wallet executing the cheaper route itself, delivery verified on chain, and exactly 5 % of the saving collected in USDC on Base. Every hash and the full proof: proof of operation and
GET https://api.recta.build/v1/golden-corridor/proof-of-operation. - A standard x402 client. On 13 November 2026 another transfer with Recta's own funds paid through Recta's x402 route, and Coinbase's facilitator settled the fee; that is how Recta entered Coinbase's x402 Bazaar.
- MetaMask Agent Wallet, first step. On 12 November 2026 the
mmplugin of@recta/mcp(the code published as version 0.1.13), installed in a real MetaMask Agent Wallet (server mode,mm7.3.0), signed and sent the fee approval on Base (transaction0x44a6c753945589dc7f4940f139f5257247d41ab23e4ffea9e4fb6cc048c6ec94). The plugin re-read the mined transaction: MetaMask kept the nonce, gas and fee caps the plugin committed.
Not proven yet
- External use. As of 14 November 2026, no external agent had executed a transfer through Recta. The public savings ledger lists only external agents' verified savings, with their transaction hashes, so the first one will show there; Recta's own tests are kept out of it.
- MetaMask, the full transfer. A route transfer sent by MetaMask Agent Wallet (
mm recta move --execute) has not been completed: the one attempt, with 10 USDC, stopped before sending anything because Recta could not bound the price at that moment (INSUFFICIENT_DATA), so no route was offered. Bring-your-own-key mode in MetaMask is untested. - Smart accounts. Coinbase Smart Wallet support in the packages is tested in code, not yet with a real account on chain.
- Independent review. Recta has audited its service, packages and fee contract adversarially itself; there has been no independent external audit. The server is not open source; what you can check without trusting it is published: the packages check every transaction locally before signing, and each verified saving is listed with its transaction hashes.
- The bridges. Across, CCTP, Stargate and LayerZero are run by third parties, and some of their contracts are upgradeable. Recta pins their addresses, not their code, and picks the cheapest route it can prove, not the safest.
Start with small amounts. The full safety notes are in llms.txt, section Safety.