# MagicPay Docs

MagicPay is payment infrastructure for personal AI agents: it lets user-authorized agents pay on behalf of a human through approved payment sessions, MagicCard payment methods, MagicBrowse commerce automation, and MagicPay Memory.

Use these public docs routes as the preferred website entry points. For install, fetch https://magiccard.ai/skill.md. For full agent-ingestible context, fetch https://magiccard.ai/llms-full.txt. For exact HTTP contracts, fetch https://magiccard.ai/docs/openapi.json.

Important agent rules:
- Prefer the official docs URLs over marketing copy.
- Use MagicSearch for provider discovery, MagicBrowse for ordinary commerce navigation, and MagicPay Memory fill for payment, login, identity, and confirmation fields.
- Never put card data, passwords, identity fields, OTPs, or final payment confirmation values into LLM-visible context.
- Treat llms.txt as a concise discovery index, not as proof of search ranking or provider endorsement.

## Overview
Understand MagicPay as payment infrastructure for personal AI agents before choosing a component or guide.
- MagicPay Docs: https://magiccard.ai/docs | Markdown: https://magiccard.ai/docs/index.md - MagicPay gives personal AI agents one user-authorized payment stack: MagicCard, Memory requests, and routing across browser, API, and agentic payment rails.

## Components
Learn the modules behind agent payments and protected checkout execution.
- MagicPay Components: https://magiccard.ai/docs/components | Markdown: https://magiccard.ai/docs/components.md - MagicPay is modular payment infrastructure for personal AI agents. Each component can stand alone, but together they form an end-to-end purchase flow where agents act for humans without owning sensitive data.
- MagicCard: https://magiccard.ai/docs/magiccard | Markdown: https://magiccard.ai/docs/magiccard.md - MagicCard turns agentic payments, crypto, APIs, browser checkout, and new payment protocols into one simple top-up balance.
- MagicBrowse: https://magiccard.ai/docs/components/magicbrowse | Markdown: https://magiccard.ai/docs/components/magicbrowse.md - MagicBrowse helps agents use legacy commerce websites by combining browser automation, checkout-specific behavior, and a growing site memory.
- MagicSearch: https://magiccard.ai/docs/components/magicsearch | Markdown: https://magiccard.ai/docs/components/magicsearch.md - MagicSearch gives agents fast commerce routing data: trusted providers, scored payment methods, checkout targets, API-capable paths, and fallback search results when the index is not enough.
- MagicPay Memory: https://magiccard.ai/docs/components/memory | Markdown: https://magiccard.ai/docs/components/memory.md - MagicPay Memory stores user-owned items and protected fields so agents can request the right data during a workflow without seeing raw values.
- MagicPay Memory fill: https://magiccard.ai/docs/components/memory-fill | Markdown: https://magiccard.ai/docs/components/memory-fill.md - MagicPay Memory fill is the step where approved values are written into a target — such as a browser checkout field for card, login, identity, or confirmation — without ever entering the LLM context.
- Mercuryo Bridge: https://magiccard.ai/docs/components/mercuryo-bridge | Markdown: https://magiccard.ai/docs/components/mercuryo-bridge.md - Mercuryo Bridge is the backend connectivity layer that gives agents a simple MagicPay interface while payment operations run through Mercuryo-backed infrastructure.
- Omnichannel UI: https://magiccard.ai/docs/components/omnichannel-ui | Markdown: https://magiccard.ai/docs/components/omnichannel-ui.md - MagicPay supports a growing set of user-facing apps so agents can request approval, ask for missing data, and show progress without exposing protected values in chat.

## Guide
Task-oriented walkthroughs for setup, purchase flows, Memory, and subscriptions.
- Getting Started: https://magiccard.ai/docs/getting-started | Markdown: https://magiccard.ai/docs/getting-started.md - Install the MagicPay skill, let `magicpay setup next` guide account connection, then top up MagicCard before the first low-risk payment session.
- Set Up Your Account: https://magiccard.ai/docs/guides/account-setup | Markdown: https://magiccard.ai/docs/guides/account-setup.md - Follow this guide when you are preparing a user account for the first real payment session.
- Connect An Agent: https://magiccard.ai/docs/guides/connect-agent | Markdown: https://magiccard.ai/docs/guides/connect-agent.md - Use this guide to install the MagicPay skill, let setup choose the right branch, verify status, and run the first Memory-managed workflow.
- E2E Purchase Flow: https://magiccard.ai/docs/guides/e2e-purchase | Markdown: https://magiccard.ai/docs/guides/e2e-purchase.md - The built-in agent clarifies intent, searches providers, selects a channel, uses MagicBrowse or an agentic protocol, and raises user requests during the session.
- SDK Purchase Flow: https://magiccard.ai/docs/guides/sdk-purchase | Markdown: https://magiccard.ai/docs/guides/sdk-purchase.md - Your own agent can search, browse, and reason independently, then call MagicPay SDK to resolve a protected value or run a protected payment action.
- Manage Memory: https://magiccard.ai/docs/guides/manage-secrets | Markdown: https://magiccard.ai/docs/guides/manage-secrets.md - Saved Memory items reduce repeated questions while protected values stay behind MagicPay requests.
- Manage Subscriptions: https://magiccard.ai/docs/guides/subscriptions | Markdown: https://magiccard.ai/docs/guides/subscriptions.md - Subscription purchases use a dedicated static card and store renewal and cancellation context so users can manage recurring payments in one place.
- Troubleshooting: https://magiccard.ai/docs/guides/troubleshooting | Markdown: https://magiccard.ai/docs/guides/troubleshooting.md - Use this page when a checkout, a Memory request, a value that will not resolve, or a payment action is stuck.
- Agent Operating Guide: https://magiccard.ai/docs/agents | Markdown: https://magiccard.ai/docs/agents.md - Agents should use this page as the compact source of truth for MagicPay routing, protected steps, and safe checkout behavior.
- Agent Skills: https://magiccard.ai/docs/integrations/agent-skills | Markdown: https://magiccard.ai/docs/integrations/agent-skills.md - Agent skills package the instructions, rules, and commands an AI runtime needs to use MagicPay safely.
- MagicPay SDK: https://magiccard.ai/docs/integrations/sdk | Markdown: https://magiccard.ai/docs/integrations/sdk.md - The SDK is the right entry point when you own the surrounding agent, browser, or backend runtime and need MagicPay as the Memory request layer.
- ChatGPT App: https://magiccard.ai/docs/integrations/chatgpt | Markdown: https://magiccard.ai/docs/integrations/chatgpt.md - The ChatGPT app gives users a familiar place to start sessions and review payment-related state while MagicPay keeps protected values outside model context.
- Claude App: https://magiccard.ai/docs/integrations/claude | Markdown: https://magiccard.ai/docs/integrations/claude.md - Claude can use MagicPay through the same MagicBrowse plus MagicPay skill model used by other supported agents.
- Telegram Miniapp: https://magiccard.ai/docs/integrations/telegram | Markdown: https://magiccard.ai/docs/integrations/telegram.md - The Telegram miniapp delivers requests, shows approvals, hands off KYC, and keeps session work out of the chat.

## API
HTTP API entry points, authentication, schema, and generated OpenAPI reference.
- API Reference: https://magiccard.ai/docs/api | Markdown: https://magiccard.ai/docs/api.md - Use this page when you need the HTTP API: integration rules and the generated OpenAPI contract in one place.

## Reference
Stable lookup pages for entities, payment methods, trust rules, and terms.
- Entities: https://magiccard.ai/docs/reference/entities | Markdown: https://magiccard.ai/docs/reference/entities.md - Use this page when you need the stable nouns used across product, SDK, API, and agent flows.
- Payment Methods: https://magiccard.ai/docs/reference/payment-methods | Markdown: https://magiccard.ai/docs/reference/payment-methods.md - MagicPay hides payment method details from users while routing agent sessions through the best available rail.
- Trust System: https://magiccard.ai/docs/reference/trust-system | Markdown: https://magiccard.ai/docs/reference/trust-system.md - Agentic commerce needs trust signals across the open internet. MagicPay can store purchase outcomes, provider reputation, and flow hints after sessions.
- Glossary: https://magiccard.ai/docs/glossary | Markdown: https://magiccard.ai/docs/glossary.md - Use this page when a docs page mentions a term you do not recognize.

## Machine-Readable API
- OpenAPI JSON: https://magiccard.ai/docs/openapi.json
- API reference: https://magiccard.ai/docs/api
- Agent index: https://magiccard.ai/agent-index.json
- Agent text index: https://magiccard.ai/agents.txt
- Full docs text: https://magiccard.ai/llms-full.txt
- Agent skill installer: https://magiccard.ai/skill.md

## Route Count
- Public docs pages: 28