Supported corridors
Every corridor settles from USDC into a local currency. The table below shows the destinations available today.Base URL
All Corridor API calls go to the production endpoint below. There is no sandbox subdomain—use your dashboard test credentials for pre-production runs.How it works
The Corridor flow is three steps. You create a corridor once per destination currency, then reuse it for as many payouts as you need.- Create a corridor —
POST /corridorsregisters a new corridor for a given destination currency. The corridor starts inPENDING_KYCstatus and moves toACTIVEafter your organization completes KYC verification in the dashboard. - Get a quote —
GET /corridors/:id/quotereturns a live FX rate, the destination amount after fees, and aquoteIdthat locks the rate for a short window. - Initiate a payout —
POST /corridors/:id/paysubmits the payout using the locked quote. Circle confirms settlement and posts a webhook event back to Meterlane, which updates the payment status fromPENDINGtoSETTLED.
Status lifecycle
A corridor’s status follows a fixed path, and a payment’s status follows its own. Corridor status:Platform fees
Meterlane charges a transaction fee on each payout. The all-in fee, including partner rail costs, is visible in the dashboard quote UI before you confirm.Corridor vs Agent Gateway
Corridor and Agent Gateway are separate products with different payment models. Use this table to pick the right one.Next steps
Quote & Pay
Step-by-step guide to creating a corridor, fetching a live quote, and submitting your first payout.
Webhooks
Configure Circle webhooks to receive real-time payment status updates in your application.