Checks a cross-border payment corridor's observed cost against the G20/FSB roadmap targets: retail cross-border payments by end-2027 (no more than 1% global average, no more than 3% for any corridor) and remittances by 2030 (no more than 3% global average, no more than 5% for any corridor). You declare a send/receive country pair, the corridor's observed cost as basis points (sourced from World Bank Remittance Prices Worldwide, methodology Q325, or your own quote basket), which USD basket size the figure is based on, and the target year to check. This tool recomputes the gap against the hardcoded target arithmetic only, and it never vendors RPW's own corridor cost table.
The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own. Load the exceeds-target demo to see a corridor that fails to meet its target.
It does not fetch a live corridor cost figure from RPW or anywhere else: you declare the observed cost, and this tool never embeds or vendors RPW's own corridor cost table (that would be a live/republished-data problem, not a compute problem). It does not check the US Reg E remittance disclosure arithmetic; see the art-reg-e-remittance-disclosure-check node for that recompute. It issues no recommendation to change corridor pricing and does not enforce the target against any single firm.
The G20/FSB cross-border payments roadmap sets a target cost ceiling for retail payments by end-2027 and remittances by 2030, both as a global average and a per-corridor ceiling; this tool checks a declared corridor's observed cost against the per-corridor ceiling for the year you select and reports the gap.
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `check_g20_corridor_cost_gap`. Task: Recompute a caller-declared cross-border payment corridor's cost gap against the hardcoded G20/FSB roadmap targets: retail cross-border payments end-2027 (no more than 1% global average, no more than 3% any corridor) and remittances 2030 (no more than 3% global average, no more than 5% any corridor).
Call it with arguments: {"policy_parameters":{"as_of":"2026-08-01","corridor_pair":{"send_country":"US","receive_country":"MX"},"observed_cost_bps":250,"send_amount_basis":"USD_200","target_year":2027}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-549-g20-corridor-cost-gap.html#p=v1.H4sIAAAAAAAA_wGcAGP_eyJhc19vZiI6IjIwMjYtMDgtMDEiLCJjb3JyaWRvcl9wYWlyIjp7InNlbmRfY291bnRyeSI6IlVTIiwicmVjZWl2ZV9jb3VudHJ5IjoiTVgifSwib2JzZXJ2ZWRfY29zdF9icHMiOjI1MCwic2VuZF9hbW91bnRfYmFzaXMiOiJVU0RfMjAwIiwidGFyZ2V0X3llYXIiOjIwMjd9VkMzCJwAAAA