Proven cheaper USDC bridge route for AI agents (Across, CCTP, Stargate); fee 5% of verified saving
Listed on
First seen 4 Nov 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
1
Directories
Collected by InvokeRank
9
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
0
GitHub stars
From MCP Toplist
Tools
| Tool | Description | Behaviour |
|---|---|---|
| recta_about | Start here. Call Recta before your agent moves stablecoins from one blockchain to another (a bridge or cross-chain transfer): give it the route you would use anyway, and it answers, for free, whether a cheaper route exists at the same chain state and proves the saving. If there is none, nothing is charged. Transfers start on: arbitrum, arc, avalanche, base, bnb_chain, ethereum, hyperevm, ink, linea, monad, optimism, polygon, unichain. They can arrive on: arbitrum, arc, avalanche, base, bnb_chain, ethereum, hyperevm, ink, linea, monad, optimism, polygon, robinhood_chain, solana_mainnet, tron_mainnet, unichain. Assets: USDC, USDC_BINANCE_PEG, USDG, USDT, USDT_BINANCE_PEG, USDT_OP_BRIDGED. Amounts: at least 3.5 tokens of a stablecoin (about 3.5 USD), no maximum. The exact corridors are in the service descriptor. Returns the full guide (llms.txt): what Recta is, the fee (5 % of the verified saving, nothing if none) and the call flow. | Read-only |
| recta_fit_check | Call first, before a cross-chain stablecoin transfer: whether Recta covers the corridor, which routes it compares, which route you can declare as yours, and the contracts a route would touch. Unsigned, free, never reveals a route or a saving. | Read-only |
| recta_prepare_signed_request | Step 1 of a free quote for a cross-chain transfer. Computes the exact message the agent's EVM wallet must sign (EIP-191 personal_sign) for one Recta request, and the headers to send. Holds no key and calls nothing. Then call recta_send_signed_request with the same method, path, idempotency_key, body and issued_at, plus the signature. Start with POST /v1/golden-corridor/commercial-evaluations (body: recta_request_template; its "sender" must be the signing address). If you have no wallet tool that can personal_sign, this server cannot sign for you: No signing code needed: the npm package @recta/client builds, checks and signs the request for you, and @recta/mcp (`npx -y @recta/mcp`) is a local MCP server that does it as tools: without a key it offers only the free fit check and trial; with RECTA_PRIVATE_KEY of a dedicated wallet (kept on your machine) it signs too. Evaluations are free and need no funds. Paying a fee needs the fee in USDC on Base and a USDC allowance to Permit2 (an ERC-20 approve of USDC to Permit2). If the transfer itself starts from USDC on Base, the wallet needs the transfer amount plus the fee. | Read-only |
| recta_request_template | Returns the full body of the evaluation request for a corridor, an amount and the route you would use anyway (baseline_provider): you fill only your sender, recipient and gas ceilings, then sign it with recta_prepare_signed_request and recta_send_signed_request. | Read-only |
| recta_saving_odds | How many recorded decisions on this corridor found a saving, by amount range (counts and dates only, never per route). Unsigned and free; use it to decide whether a signed evaluation is worth it. | Read-only |
| recta_send_signed_request | Step 2: sends the request signed by the agent's own wallet to a Recta route and returns its HTTP status and JSON body. POST /v1/golden-corridor/commercial-evaluations returns, free, the cheapest provable route against the route the agent would use anyway, or an abstention. Executing a decision's route creates a fee of 5 % of the verified saving, capped by the permit the agent signs; no saving, no fee. | Changes data |
| recta_service_descriptor | Call to check whether a planned cross-chain transfer is covered: the supported corridors (source and destination networks and assets), the bridges compared (Across, CCTP, Stargate, USDT0 and others), amount ranges, limits and the JSON Schema of every request and response. | Read-only |
| recta_status | Call before relying on Recta in a run: whether it is ready to evaluate now, and its contract version. | Read-only |
| recta_trial_evaluation | Unsigned trial of an evaluation: send the evaluation request body (from recta_request_template, with a sender and recipient filled: no wallet needed: any sender address other than the zero address, and any recipient of the destination network's kind) and get whether a cheaper provable route exists for this exact transfer, the saving (lower bound, USDC) and Recta's 5 % of it. Names no route, stores nothing, charges nothing; 3 a day per IP address. To get the route, sign the same body with recta_prepare_signed_request and recta_send_signed_request. | Read-only |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Official MCP Registry | Recta | - | 4 Nov 2026 |