CCelo PayGrid

Documentation

Celo PayGrid Overview

Celo PayGrid is an MCP-based payment execution and verification layer for AI agents on Celo Mainnet.

Production endpoints

ResourceURL
MCP endpointhttps://mcp.celopaygrid.xyz/mcp
Agent metadatahttps://mcp.celopaygrid.xyz/.well-known/paygrid-agent.json
API healthhttps://api.celopaygrid.xyz/health
MCP healthhttps://mcp.celopaygrid.xyz/health
Landinghttps://web.celopaygrid.xyz

Network

ItemValue
NetworkCelo Mainnet
Chain ID42220
RPC used by production serviceshttps://forno.celo.org
Agent ID standardERC-8004
Discovery toolget_agent_capabilities

Current production capabilities

  • Remote MCP discovery and tool listing.
  • Payment request creation, lookup and verification.
  • Automatic stablecoin swap quotes and payments.
  • Agent payment activity review.
  • Supported stablecoin discovery.
  • Card checkout preparation through the existing provider abstraction.
  • x402 endpoint calling with caller-provided payment headers.
  • Public agent metadata discovery.
  • Celo Mainnet settlement verification.

Automatic stablecoin swaps

Payment links settle in the token selected by the creator, while payers can use USDC, USDT or USDm. If the payer token differs from the requested token, Paygrid quotes and executes a Mento-routed swap so the recipient still receives the original settlement token.

TokenDecimalsRole
USDC6Supported payer and settlement token
USDT6Supported payer and settlement token
USDm18Supported payer and settlement token

Agents can call quote_payment_request to inspect the route and pay_payment_request to prepare approval and payment transactions.

Mainnet swap proof

Paygrid has a live Celo Mainnet transaction proving the swap-enabled flow.

ItemValue
Transaction0xef8a70228255479df5b42ad57aa708a14b108faff4725c0cbcb4e1a4439ce4d5
FlowUSDT payer token to USDC settlement token
RouterPaygridRouterV2
Swap routeMento Router
Recipient settlementUSDC

The transaction calls PaygridRouterV2, routes through Mento, emits SwapPayment and PaymentReceived, pays the recipient in USDC and marks the payment request as paid onchain.

Mainnet contracts

ContractAddress
PaygridLink0x31Aa9Ba23e4CAC3f41d88fb1C904067c0b3dda89
PaygridRouterV20x8d290c97100f0e87e04Efd1a790F27004fA3f08B
Mento Router0x4861840C2EfB2b98312B0aE34d86fD73E8f9B6f6
Treasury Safe0xc0C019DCeCE7a3a235Ab520F394A57c132F90cD6

ERC-8004 identity

ItemValue
Agent ID9497
Agent wallet0x0AcF80b591eA0fE2cf9b1108ba9E4b278f3330Ce
Metadata URIhttps://mcp.celopaygrid.xyz/.well-known/paygrid-agent.json
ERC-8004 Identity Registry0x8004A169FB4a3325136EB29fA0ceB6D2e539a432
Self Protocol Agent ID172
Self agent address0xEf3481bcDd48Db5FFdaF77A39F5f64BaDC957316

Verify token URI

cast call 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 \
  "tokenURI(uint256)(string)" 9497 \
  --rpc-url https://forno.celo.org

Self Protocol identity

Celo PayGrid supports Self Protocol Agent ID metadata in the MCP service. The current public state is verified for Self Agent ID 172, and the public MCP metadata advertises self-agent-id in supportedTrust when the hosted MCP env is configured with the verified Self values.

Current limitations

Celo PayGrid does not currently claim support for advanced spending policies, ERP automation, enterprise reconciliation, guaranteed fraud protection, banking compliance, insurance or automatic approvals.