Before your agent bridges USDC: three worked examples
Copy-paste examples of the check an AI agent can run before it moves USDC between blockchains: what to send, what Recta answers, and when to go ahead with the route the agent already had. Free, no wallet, no API key.
The rule your agent follows
Before the agent sends USDC from one network to another, it asks Recta one question: is there a cheaper route than the one I am about to use, for this exact transfer? Recta is a check, not a gate: whatever it answers, the agent can go ahead with its own route.
SAVING_FOUND: a cheaper route exists, and the answer says by how much at least. To use it, sign the same request (see example 3). The signed evaluation runs again on fresh data: if the saving still holds, it names the route and its transactions; if not, it says so and nothing is owed. If the agent executes the route, Recta charges exactly 5 % of the saving it verifies on chain afterwards.NO_SAVING: Recta compared and could not prove anything cheaper.NO_SAVING_EXPECTED: Recta's record shows a saving here too rarely, so it did not search. In both cases, continue with your own route. Nothing is charged.NOT_PROVEN, or a refusal markedretryable: Recta could not complete the comparison this time. Continue with your own route, or ask again in a minute. Nothing is charged.- Any other refusal: fix the body as its
helpsays, or continue with your own route. Nothing is charged.
The examples below use the free trial: unsigned, no wallet, 3 a day per IP address, and it names no route. No wallet is needed for the trial: its sender may be any EVM address other than the zero address and its recipient any address of the destination network's kind (0x, or a base58 key toward Solana), even ones you do not control, because nothing is sent, signed or charged. The address you would really send from gives the most exact figure, since the trial reads that address's token approval on chain. The examples use 0x2222222222222222222222222222222222222222 as sender and recipient; replace it with yours. Each answer shown was read on 14 November 2026 for the same transfer from another example address; the figures change block by block, so yours will differ.
Example 1: Base to Arbitrum, 1 000 USDC, when you would use Stargate
Your agent is about to move 1 000 USDC from Base to Arbitrum through Stargate v2. Before it signs, it runs:
curl -s -X POST 'https://api.recta.build/v1/golden-corridor/trial-evaluation' \
-H 'content-type: application/json' \
-d '{
"schema": "RECTA_COMMERCIAL_ECONOMIC_REQUEST_V1",
"source_network": "base",
"source_asset": "USDC",
"destination_network": "arbitrum",
"destination_asset": "USDC",
"amount": "1000",
"constraints": {
"guarantee_class": "ANY",
"latency_class": "ANY",
"destination_execution": "NONE"
},
"sender": "0x2222222222222222222222222222222222222222",
"recipient": "0x2222222222222222222222222222222222222222",
"baseline_provider": "stargate_v2",
"execution_authority": {
"headroom": "0.2",
"source_max_fee_per_gas_wei": "100000000",
"source_max_priority_fee_per_gas_wei": "1000000"
}
}'
The two gas fields are the most your agent accepts to pay for gas on the source network, in wei (here 0.1 gwei and 0.001 gwei, ample on Base and on Arbitrum, the source of example 2). Recta answered (abridged):
{
"status": "TRIAL",
"outcome": "SAVING_FOUND",
"saving_usdc": "1.745768",
"recta_fee_usdc": "0.087288",
"you_keep_usdc": "1.65848",
"route": "withheld",
"valid_for_seconds": 60
}
Decision: a route at least 1.74 USDC cheaper than Stargate existed for this transfer. If that is worth it to you, sign the same body (example 3): if the signed evaluation confirms the saving on fresh data, it names the route; after you execute it, Recta charges 5 % of the saving it verifies (about 0.09 USDC here), and you keep the rest. If you do not sign, nothing happens and nothing is owed.
Example 2: Arbitrum to Ethereum, 1 000 USDC, when you would use Across
Declare the route you would really use, here Across, and Recta tells you whether to stay with it:
curl -s -X POST 'https://api.recta.build/v1/golden-corridor/trial-evaluation' \
-H 'content-type: application/json' \
-d '{
"schema": "RECTA_COMMERCIAL_ECONOMIC_REQUEST_V1",
"source_network": "arbitrum",
"source_asset": "USDC",
"destination_network": "ethereum",
"destination_asset": "USDC",
"amount": "1000",
"constraints": {
"guarantee_class": "ANY",
"latency_class": "ANY",
"destination_execution": "NONE"
},
"sender": "0x2222222222222222222222222222222222222222",
"recipient": "0x2222222222222222222222222222222222222222",
"baseline_provider": "across",
"execution_authority": {
"headroom": "0.2",
"source_max_fee_per_gas_wei": "100000000",
"source_max_priority_fee_per_gas_wei": "0"
}
}'
{
"status": "TRIAL",
"outcome": "NO_SAVING",
"message": "Recta could not prove a saving over your declared route right now, so a signed evaluation would charge nothing. ..."
}
Decision: at that moment Recta could not prove a cheaper route, so continue with Across. Nothing is charged. Always declare the route you would really use: the saving and the 5 % are measured against it, so declaring a worse route only makes you pay more.
Example 3: get the route, from an MCP agent or from code
The trial shows whether a saving exists; the route itself needs the same request signed by the wallet that sends the funds. Recta never receives a key: your agent signs locally.
- MCP agents (Claude, Cursor and others): add this server to the client's configuration. Without
RECTA_PRIVATE_KEYit offers only the free toolsrecta_fitandrecta_trial_evaluation. SetRECTA_ADDRESSto the real 0x address you would send from (it is optional; a malformed value stops the server), or leave it out and give thesenderin your question.
{
"mcpServers": {
"recta": {
"command": "npx",
"args": ["-y", "@recta/mcp"],
"env": { "RECTA_ADDRESS": "0x2222222222222222222222222222222222222222" }
}
}
}
- Then ask your agent, in plain words: "Before sending 1000 USDC from Base to Arbitrum with Stargate, check with Recta whether there is a cheaper route."
- To let it get and execute the route, give it a dedicated wallet:
RECTA_PRIVATE_KEY(a wallet that holds only what the agent may move) andRECTA_ALLOW_EXECUTE=yes. By default the server refuses, before signing, a transfer aboveRECTA_MAX_AMOUNT(1000 tokens) or to any recipient other than that wallet. - Code:
npm install @recta/clientbuilds, checks and signs the request, and checks every transaction before your wallet sends it. Plain HTTP: the signing rule is in llms.txt.
What Recta can and cannot do with your wallet, and what is proven so far: trust guide.