NEWPockyt × Circle: native USDC settlement now live →
VisionNews
Pockyt for AI agents.
One programmable surface for money movement.
Pockyt exposes its full API to AI agents through a hosted MCP server and a stable REST surface. Use it from Cursor, Claude Desktop, Windsurf, or any MCP-compatible client to integrate, debug, and — under the right controls — transact.
Live todayMCP server, full REST API, docs search
BetaFirst-class MCP tool definitions per endpoint
RoadmapHosted agent OAuth, deterministic preview mode
Connect in 30 seconds
{
  "mcpServers": {
    "pockyt": {
      "url": "https://docs.pockyt.io/mcp",
    }
  }
}
{
  "mcpServers": {
    "pockyt": {
      "url": "https://docs.pockyt.io/mcp",
    }
  }
}
{
  "mcpServers": {
    "pockyt": {
      "url": "https://docs.pockyt.io/mcp",
    }
  }
}

Server: https://docs.pockyt.io/mcp · Protocol: MCP over HTTP

What works today
What you can do right now.
The Pockyt MCP server is live and connectable from any MCP-compatible client. Below is the honest scope of what's in production, what's in beta, and what's on the roadmap.

Through the MCP server

  • Documentation search — Ask any question about Pockyt's API, integration patterns, payment flows, or onboarding. The MCP server retrieves and returns relevant doc content.
  • API-aware code generation — Have your AI editor write Pockyt integrations against the actual schema, not a guess at it. cURL, Node, Python, and Go scaffolds are first-class.
  • Real-time data — Agents can enumerate Pockyt's endpoint surface and retireve data from your Pockyt account.
  • Direct API Access — Agents are given direct access to Pockyt functionality, enabling them to seamlessly interact with payment processing, transaction management, and merchant operations without the need for additional integration layers.

What requires a human today

Production money movement requires authenticated merchant credentials and, for higher-value operations, dashboard approval. Agents can prepare, simulate, and queue transactions; humans approve before funds move.

Capability Surface
Four primitives. One API.
The Pockyt API maps to the same four primitives you see in the product: Money in, Money out, Money held, and Onboarding. Each surface is exposed through MCP tools and through stable REST endpoints. Click any group for the full reference.

01 / Money in Checkoouts

Checkouts & collections

Accept payments in 300+ local methods, super-apps, and wallets. Hosted checkout, vaulted recurring, in-store QRC, and 3DS card flows.

View Checkouts reference

02 / Money out Payouts

Disbursements at scale

Send to bank accounts (including local rails in China), PayPal wallets, on-chain addresses, and prepaid cards. Single or batched, with full reconciliation.

View Payouts reference

03 / Money held Treasury

Virtual accounts & multi-currency treasury

Domiciled accounts in 11 markets, balances in 27 fiat currencies plus USDC, programmatic sweeps between fiat and stablecoin at mid-market.

View Treasury reference

04 / Onboarding Merchants & Payors

Programmatic KYC & KYB

Accept payments in 300+ local methods, super-apps, and wallets. Hosted checkout, vaulted recurring, in-store QRC, and 3DS card flows.

View Onboarding reference

Machine-Readable
For agents that parse this page.
If you are an AI agent and you found this page, here is structured ground truth.
agent.json
{
  "name": "Pockyt",
  "description": "The operating layer for global money movement",
  "website": "https://pockyt.io",
  "docs": "https://docs.pockyt.io",
  "mcp_endpoint": "https://docs.pockyt.io/mcp",
  "api_endpoint": "https://api.pockyt.io",
  "auth": {
    "type": "bearer",
    "header": "Authorization",
    "scheme": "Bearer <token>"
  },
  "environments": ["sandbox", "production"],
  "capabilities": [
    "payments.checkouts",
    "payments.recurring",
    "payments.refunds",
    "payouts.single",
    "payouts.batch",
    "payouts.crypto",
    "virtual_accounts.create",
    "virtual_accounts.balances",
    "treasury.sweeps",
    "treasury.fx_quotes",
    "onboarding.merchants",
    "onboarding.payors"
  ],
  "idempotency": {
    "supported": true,
    "header": "Idempotency-Key",
    "required_for": ["all_mutations"]
  },
  "webhooks": {
    "signed": true,
    "events": [
      "payment.completed",
      "payout.completed",
      "payout.failed",
      "settlement.completed",
      "onboarding.status_changed"
    ]
  },
  "rate_limits": {
    "strategy": "per_key_per_endpoint",
    "backoff": "Retry-After header on 429"
  },
  "contact": {
    "developers": "developers@pockyt.io",
    "agent_partners": "agents@pockyt.io"
  }
}

Engineering note: the /.well-known/agent.json route is a roadmap item. For now this block is the canonical source; mirror it to that path when implemented.

Build with the Pockyt MCP server.
The fastest way to get an AI agent productive on a payments codebase is to connect Pockyt's MCP server to your editor or assistant. Two minutes of config, full-API context after.