MagicPay Docs

MagicPay gives personal AI agents one user-authorized payment stack: MagicCard, Memory requests, and routing across browser, API, and agentic payment rails. Use this page for magicpay docs decisions, implementation details, and safe agent routing. MagicCard, requests, secrets, and approvals stay under the human owner's control.

What MagicPay Is

MagicPay is designed to be the universal payment tool for a personal AI agent. The agent can use Mercuryo-backed cards and payment operations, APIs, crypto rails, browser checkout, and agent-native protocols to get the job done, while the user sees a simple MagicCard with one balance. MagicCard makes payments in the complex world of agentic protocols, new payment standards, and crypto feel as simple as topping up a card.

MagicPay Overview

MagicPay is payment infrastructure for personal AI agents. The goal is to feel as simple as Apple Pay for users and their agents while hiding wallets, cards, protocols, approval routing, and Memory-managed execution behind one MagicCard interface.

Memory-managed Requests Approvals, secrets, identity details, and payment execution move through user-controlled requests instead of model context when users choose the MagicPay path. Commerce Routing MagicSearch, MagicBrowse, SDK, API, and agentic protocols pick the best payment path for each agent purchase.

Purchase Loop

Every purchase is a session: the personal agent clarifies intent, MagicPay raises requests when user authority is needed, and execution continues through the best available payment rail.

Intent To Session The user asks their agent for a purchase, and MagicPay turns it into a tracked payment session with events. User Authority KYC, balance, approvals, secrets, and final confirmations stay owned by the human. Payment Execution The session can finish through x402, MCP/API, SDK calls, or Memory-managed browser checkout.

Build With MagicPay

Use the built-in payment agent for end-to-end purchases, or connect your own personal agent runtime through the SDK and API while the user stays in control through MagicPay UI surfaces.

Built-In Payment Agent Searches providers, coordinates MagicBrowse, ranks payment channels, and asks the user when Memory-managed action is needed. MagicPay SDK Bridges agents to Mercuryo payment infrastructure and MagicPay backend services for sessions, auth, and preferences. Human UI Web, mobile, ChatGPT, Claude, Telegram, and email surfaces handle approvals, sessions, card state, and confirmations.

Choose Your Path

Use the docs path that matches what you want to do next.

Set up an account Create the user account, pass KYC, top up the MagicCard balance, and connect your first agent. Understand the product Start with MagicCard, Memory requests, MagicBrowse, MagicSearch, and the SDK. Run a purchase Follow the built-in agent purchase flow from intent discovery to provider selection and user approval. Integrate the SDK Use MagicPay from your own agent, worker, MCP tool, or browser runtime.

Recommended Path

Most users and builders should follow the same staged path before a real payment. This keeps setup, safety, and payment authority understandable for both humans and agents.

Create a MagicPay account and complete account, KYC, and balance prerequisites.
Connect one agent runtime and verify that MagicPay and MagicBrowse are available.
Run a browser-only task so the agent proves it can navigate without Memory data.
Run a low-risk Memory request such as a shipping or test payment form handoff.
Add reusable MagicPay Memory values only after the user understands what will be stored.
Move to SDK, API, or full purchase flows once request handling is observable end to end.

Use Case Entry Points

Start from the workflow you are trying to ship. The components underneath are modular, but each path has a different trust boundary.

I want my agent to buy something Use the end-to-end purchase guide to combine MagicSearch, MagicBrowse, approvals, and payment execution. I want Memory-managed form fill Use MagicPay Memory fill when the agent reaches card, login, identity, or confirmation fields. I want to integrate the SDK Use MagicPay SDK when your app owns the surrounding agent or browser runtime. I want Mercuryo-backed payments Use Mercuryo Bridge docs for account linking, KYC, card state, top-up, and provider callbacks. I want agent-readable rules Use the agent operating guide for machine-readable boundaries, routing rules, and discoverability hints. Something is stuck Use troubleshooting for checkout, request, Memory, payment, and Mercuryo failure modes.