Three independent recomputes on your cross-border payment. Step 1 itemizes the invoice's cost stack: FX spread, method fee, VAT or reverse-charge, documentary-credit, and reconciliation cost, as a percentage of invoice value. Step 2 recomputes the corridor's declared cost gap against the hardcoded G20/FSB roadmap targets for the year you declare. Step 3 models the same corridor on a USDC stablecoin rail so you can see the cheaper alternative side by side. Every figure is caller-declared; the page makes no live FX or rate calls. No personal data is processed.
compute_cross_border_fees{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_cross_border_fees",
"arguments": {
"origin_country": "US",
"dest_country": "GB",
"invoice_amount": 10000,
"fx_spread_bps": 150,
"method_fee": 25,
"vat_rate": 0,
"doc_cost": 0,
"recon_cost": 0
}
},
"id": 1
}
check_g20_corridor_cost_gap{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "check_g20_corridor_cost_gap",
"arguments": {
"as_of": "2026-10-01",
"corridor_pair": {
"send_country": "US",
"receive_country": "MX"
},
"observed_cost_bps": 250,
"send_amount_basis": "USD_200",
"target_year": 2027
}
},
"id": 2
}
model_stablecoin_corridor_economics{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "model_stablecoin_corridor_economics",
"arguments": {
"send_amount_usd": 10000,
"on_ramp_fee_pct": 1.0,
"chain_fee_usd": 0.01,
"off_ramp_fee_pct": 0.8,
"fx_spread_pct": 0.5,
"correspondent_cost_pct": 6.0
}
},
"id": 3
}
aggregate_execution_receipts{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "aggregate_execution_receipts",
"arguments": {
"artifacts": [
""
]
}
},
"id": 4
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: My supplier invoiced $10,000 from Germany with a 1.5% FX spread and $25 wire fee. What is the true all-in cost and does the corridor meet the G20 target?
Run the AINumbers MCP tool `run_chain` with {"chain":"cross-border-payment-cost-check"} and read `art-367-compute-cross-border-fees.total_cost`.
Re-run with `inputs` for `art-367-compute-cross-border-fees`, reusing the values that result echoed, with `fx_spread_bps` set to 300. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/cross-border-payment-cost-check.html