Glide for AI agents

Banking for Agents

Give your AI agent a real account: US dollar and euro bank details, USDC wallets on EVM and Solana with the gas paid by Glide, and a budget it cannot exceed.

Connect your agent Read the docs

Works with Claude, Cursor, Codex and any other MCP client. New connections start read-only.

Terminal

$ npx @glideco/cli connect

  Sign-in code: KXQB-7M2D

  https://glide.co/dashboard/agent-connect?code=KXQB-7M2D

  Waiting for browser sign-in

  Connected.
  MCP endpoint: https://mcp.glide.co

Networks with gas paidEthereum, Base, Arbitrum, Polygon, Solana: 5
Bank account currenciesA US account and routing number, and a euro IBAN: 2
Local payout currenciesFrom the live currency registry: 50
Glide fee on x402 receiptsUSDC lands in your own wallet: 0

Your agent pays in USDC. Glide pays the network fee.

Sends from a Glide wallet on Ethereum, Base, Arbitrum, Polygon and Solana go out with the gas paid by Glide. Neither you nor your agent has to buy or hold ETH, POL or SOL to move your own stablecoins.

On EVM chains the send runs as a sponsored transaction through EIP-7702, so a plain wallet with no gas balance can still pay.
On Solana, Glide is the fee payer and also covers the rent to open a recipient's token account the first time you pay them.
Safe vaults are sponsored through an ERC-4337 paymaster once the module is enabled for that chain.
Sponsorship is decided on Glide's servers, behind the same limits and sanctions screening as the send itself.

Network fees on a USDC send

Networks where Glide pays the gas on a send, and the gas token you no longer need to hold.
Network	Gas token	Gas paid by
Ethereum	ETH	Glide
Base	ETH	Glide
Arbitrum	ETH	Glide
Polygon	POL	Glide
Solana	SOL	Glide

x402 compatible

Any agent can pay your account over HTTP 402.

x402 turns a payment into an HTTP request. Every Glide account gets an x402 endpoint on Base and on Solana. A paying agent requests it, gets a 402 with the price and the address, and retries with a signed USDC payment in the X-PAYMENT header.

USDC settles to the account holder's own wallet. Glide takes no cut.
Glide confirms each settlement on chain itself before it acknowledges the payment, rather than trusting the facilitator's receipt.
The connector's get_wallets tool returns the endpoint for each chain, so your agent can hand it to whoever is paying.
Glide's x402 facilitator is open source as @glideco/x402-facilitator, with sanctions screening built into verify and settle.

Receiving over x402 is live. Paying other x402 endpoints from a Glide account is not available yet.

Paying a Glide account over x402

GET /api/x402/{account}?network=solana
402 Payment Required
{
  "x402Version": 1,
  "accepts": [
    {
      "scheme": "exact",
      "network": "solana",
      "maxAmountRequired": "1000000",
      "payTo": "7Hq3…4mNw",
      "asset": "EPjFWdd5…Dt1v"
    }
  ]
}

POST /api/x402/{account}?network=solana
X-PAYMENT: eyJ4NDAyVmVyc2lvbiI6MSwic2NoZW1lIjoi…
200 OK // settled and confirmed on chain

Fiat bank accounts

US dollar and euro bank details your agent can hand out.

Once the account holder verifies their identity, the account gets a US account and routing number for dollar bank transfers, and a euro IBAN for SEPA. Your agent reads them with the deposit.fiat tool and can put them on an invoice or send them to a payer.

Most accounts open in about two minutes. Your agent can start verification with kyc.start, but the account holder completes it.
Wallets work from the first minute with no verification. Bank details appear once verification is approved.
Accounts are provided by Glide's licensed banking partners, under their custody and deposit-protection rules.

US dollar account

USD

Account number: •••• •••• 4821
Routing number: •••• •2093
Receives: US bank transfers

Euro account

EUR

IBAN: •••• •••• •••• 3017
BIC: ••••••••
Receives: SEPA transfers

Illustrative. Real details appear in the app and through deposit.fiat once verification is approved.

Cross-border payments

Pay out to local bank accounts in 50 currencies.

From a dollar or USDC balance, pay a bank account abroad in its own currency, over local rails like SEPA in Europe, Faster Payments in the UK, PIX in Brazil and SPEI in Mexico.

Your agent prices a payout with payments.payout.quote. A quote never moves money.
The rate and the fee are shown before anything is sent. Transfer fees are published per rail.
Bank payouts are sent from the Glide app, by a person on the account.

Pricing a payout

payments.payout.quote
{
  "amount_cents": 250000,
  "input_currency": "USDC",
  "output_currency": "EUR",
  "country": "DE"
}
// returns quote_id, rate, fee, output_amount, expires_at
// state: "quote_only", nothing has moved

50 payout currencies

How it works

Three steps from terminal to budget

Connect your agent
Run npx @glideco/cli connect in the terminal your agent works in, or add https://mcp.glide.co as a server in your MCP client.
https://mcp.glide.co
Sign in and approve
The CLI shows a sign-in code and opens glide.co in your browser. Sign in, check the code matches, and approve. The agent gets a token that expires after an hour and refreshes from the same approval.
Give it a budget
Set a per-payment cap, a daily cap and who it may pay. Anything above the approval threshold you choose waits for you.

Safety

An agent spends what you allow, and nothing else

The limits are checked on Glide's servers before money moves. Nothing in the agent's prompt or tool call can widen them.

Policy envelopes
Every payment an agent attempts is checked against its policy before money moves: per-payment, daily and lifetime caps, allowed counterparties and chains, how many payments per hour and per day, and the hours it may act. A payment outside the policy is refused.
Step-up approvals
Above the threshold you set, the agent gets a link instead of a payment. You approve it on glide.co. The approval is bound to that tool, amount, recipient and chain, so it cannot be reused for a different payment.
Multisig vaults
Hold the agent's funds in a Safe vault on EVM or a Squads vault on Solana. With an M-of-N vault, an agent payment becomes a proposal your co-signers approve before it broadcasts.
Read-only by default
A new connection can read balances, simulate payments and start verification. Moving money needs scopes you grant, and you can revoke an agent from the dashboard at any time.

A payment above the approval threshold

payments.initiate
{
  "counterparty": {
    "address": "0x8f3c…a41e",
    "chain": "base",
    "token": "USDC"
  },
  "amount_cents": 120000,
  "currency": "USD",
  "idempotency_key": "inv-2026-0412"
}

// response
{
  "kind": "pending_step_up",
  "risk_verdict": "allow_with_step_up",
  "step_up_url": "https://glide.co/step-up/…"
}

Straight answers

Questions about agent banking

Is Glide a bank?

Glide is a fintech company, not a bank and not a money transmitter. Holding funds, executing payments, converting currency and issuing cards are provided by licensed partner fintechs and banks under their own permissions.

Which agents work with Glide?

Any client that speaks the Model Context Protocol, including Claude, Cursor and Codex. Add https://mcp.glide.co as a server, or run npx @glideco/cli connect to sign in from the terminal. The AI connections page in settings has the steps for each client.

Who pays the gas?

Glide does, on sends from Glide wallets on Ethereum, Base, Arbitrum, Polygon and Solana. You never need to hold ETH, POL or SOL. Safe vaults are sponsored once the 4337 module is enabled for that chain.

What does x402 support mean on Glide?

Every Glide account has an x402 endpoint on Base and Solana, so another agent can pay it USDC with an ordinary HTTP request. Payments settle to your own wallet and Glide takes no fee. Paying other x402 endpoints from a Glide account is not available yet.

Can my agent open a bank account without me?

It can create the account and start verification, and the wallets work straight away. The bank details only appear once the account holder has verified their identity with Glide's regulated partner. An agent cannot complete that step on anyone's behalf.

What can an agent do without my approval?

Only what its policy allows. A new connection is read-only. Once you grant payment scopes, payments under your approval threshold and inside your caps go through. Anything above the threshold waits for you, and anything outside the policy is refused.

Which currencies can I pay out in?

50 local currencies, including EUR, GBP, BRL, MXN, INR, NGN and PHP. The full list, with the rail each one uses, is on the currency coverage page.

Does the agent ever hold my keys?

No. The agent holds a scoped token that expires after an hour. Wallet keys stay with Glide's wallet infrastructure or in your Safe or Squads vault, and revoking the agent from the dashboard stops the token from working.

Every tool your agent can call is listed in the MCP tool reference. Currency rails are on the currency coverage page.

Give your agent an account

Connect in a few minutes from the terminal or your MCP client. Start read-only, then add a budget when you are ready.

Connect your agent MCP tool reference

Regulated services provided by partner fintechs and banks

Banking for Agents

Your agent pays in USDC. Glide pays the network fee.

Any agent can pay your account over HTTP 402.

US dollar and euro bank details your agent can hand out.

Pay out to local bank accounts in 50 currencies.

Three steps from terminal to budget

Connect your agent

Sign in and approve

Give it a budget

An agent spends what you allow, and nothing else

Policy envelopes

Step-up approvals

Multisig vaults

Read-only by default

Questions about agent banking

Give your agent an account