{
  "name": "MagicPay",
  "lastUpdated": "2026-08-20",
  "summary": "MagicPay is Mercuryo-backed payment infrastructure for personal AI agents. It combines MagicCard, MagicBrowse, MagicSearch, MagicPay Memory, MagicPay Memory fill, Mercuryo Bridge, and omnichannel approvals so user-authorized agents can complete purchases without exposing card data, passwords, identity fields, OTPs, or final payment confirmations to LLM context.",
  "support": "support@mercuryo.ai",
  "primaryRoutes": {
    "landing": "https://magiccard.ai/",
    "docs": "https://magiccard.ai/docs",
    "skill": "https://magiccard.ai/skill.md",
    "llms": "https://magiccard.ai/llms.txt",
    "fullDocs": "https://magiccard.ai/llms-full.txt",
    "openapi": "https://magiccard.ai/docs/openapi.json"
  },
  "agentRules": [
    "Use MagicSearch for provider discovery.",
    "Use MagicBrowse for ordinary commerce navigation.",
    "Use MagicPay requests for Memory data, choices, approvals, and payment execution.",
    "Never place card data, passwords, identity fields, OTPs, or final payment confirmation values into LLM-visible context.",
    "Stop at protected boundaries and wait for MagicPay."
  ],
  "docsGroups": [
    {
      "id": "overview",
      "label": "Overview",
      "summary": "Understand MagicPay as payment infrastructure for personal AI agents before choosing a component or guide.",
      "pages": [
        {
          "title": "MagicPay Docs",
          "url": "https://magiccard.ai/docs",
          "markdown": "https://magiccard.ai/docs/index.md",
          "summary": "MagicPay gives personal AI agents one user-authorized payment stack: MagicCard, Memory requests, and routing across browser, API, and agentic payment rails."
        }
      ]
    },
    {
      "id": "components",
      "label": "Components",
      "summary": "Learn the modules behind agent payments and protected checkout execution.",
      "pages": [
        {
          "title": "MagicPay Components",
          "url": "https://magiccard.ai/docs/components",
          "markdown": "https://magiccard.ai/docs/components.md",
          "summary": "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."
        },
        {
          "title": "MagicCard",
          "url": "https://magiccard.ai/docs/magiccard",
          "markdown": "https://magiccard.ai/docs/magiccard.md",
          "summary": "MagicCard turns agentic payments, crypto, APIs, browser checkout, and new payment protocols into one simple top-up balance."
        },
        {
          "title": "MagicBrowse",
          "url": "https://magiccard.ai/docs/components/magicbrowse",
          "markdown": "https://magiccard.ai/docs/components/magicbrowse.md",
          "summary": "MagicBrowse helps agents use legacy commerce websites by combining browser automation, checkout-specific behavior, and a growing site memory."
        },
        {
          "title": "MagicSearch",
          "url": "https://magiccard.ai/docs/components/magicsearch",
          "markdown": "https://magiccard.ai/docs/components/magicsearch.md",
          "summary": "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."
        },
        {
          "title": "MagicPay Memory",
          "url": "https://magiccard.ai/docs/components/memory",
          "markdown": "https://magiccard.ai/docs/components/memory.md",
          "summary": "MagicPay Memory stores user-owned items and protected fields so agents can request the right data during a workflow without seeing raw values."
        },
        {
          "title": "MagicPay Memory fill",
          "url": "https://magiccard.ai/docs/components/memory-fill",
          "markdown": "https://magiccard.ai/docs/components/memory-fill.md",
          "summary": "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."
        },
        {
          "title": "Mercuryo Bridge",
          "url": "https://magiccard.ai/docs/components/mercuryo-bridge",
          "markdown": "https://magiccard.ai/docs/components/mercuryo-bridge.md",
          "summary": "Mercuryo Bridge is the backend connectivity layer that gives agents a simple MagicPay interface while payment operations run through Mercuryo-backed infrastructure."
        },
        {
          "title": "Omnichannel UI",
          "url": "https://magiccard.ai/docs/components/omnichannel-ui",
          "markdown": "https://magiccard.ai/docs/components/omnichannel-ui.md",
          "summary": "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."
        }
      ]
    },
    {
      "id": "guide",
      "label": "Guide",
      "summary": "Task-oriented walkthroughs for setup, purchase flows, Memory, and subscriptions.",
      "pages": [
        {
          "title": "Getting Started",
          "url": "https://magiccard.ai/docs/getting-started",
          "markdown": "https://magiccard.ai/docs/getting-started.md",
          "summary": "Install the MagicPay skill, let `magicpay setup next` guide account connection, then top up MagicCard before the first low-risk payment session."
        },
        {
          "title": "Set Up Your Account",
          "url": "https://magiccard.ai/docs/guides/account-setup",
          "markdown": "https://magiccard.ai/docs/guides/account-setup.md",
          "summary": "Follow this guide when you are preparing a user account for the first real payment session."
        },
        {
          "title": "Connect An Agent",
          "url": "https://magiccard.ai/docs/guides/connect-agent",
          "markdown": "https://magiccard.ai/docs/guides/connect-agent.md",
          "summary": "Use this guide to install the MagicPay skill, let setup choose the right branch, verify status, and run the first Memory-managed workflow."
        },
        {
          "title": "E2E Purchase Flow",
          "url": "https://magiccard.ai/docs/guides/e2e-purchase",
          "markdown": "https://magiccard.ai/docs/guides/e2e-purchase.md",
          "summary": "The built-in agent clarifies intent, searches providers, selects a channel, uses MagicBrowse or an agentic protocol, and raises user requests during the session."
        },
        {
          "title": "SDK Purchase Flow",
          "url": "https://magiccard.ai/docs/guides/sdk-purchase",
          "markdown": "https://magiccard.ai/docs/guides/sdk-purchase.md",
          "summary": "Your own agent can search, browse, and reason independently, then call MagicPay SDK to resolve a protected value or run a protected payment action."
        },
        {
          "title": "Manage Memory",
          "url": "https://magiccard.ai/docs/guides/manage-secrets",
          "markdown": "https://magiccard.ai/docs/guides/manage-secrets.md",
          "summary": "Saved Memory items reduce repeated questions while protected values stay behind MagicPay requests."
        },
        {
          "title": "Manage Subscriptions",
          "url": "https://magiccard.ai/docs/guides/subscriptions",
          "markdown": "https://magiccard.ai/docs/guides/subscriptions.md",
          "summary": "Subscription purchases use a dedicated static card and store renewal and cancellation context so users can manage recurring payments in one place."
        },
        {
          "title": "Troubleshooting",
          "url": "https://magiccard.ai/docs/guides/troubleshooting",
          "markdown": "https://magiccard.ai/docs/guides/troubleshooting.md",
          "summary": "Use this page when a checkout, a Memory request, a value that will not resolve, or a payment action is stuck."
        },
        {
          "title": "Agent Operating Guide",
          "url": "https://magiccard.ai/docs/agents",
          "markdown": "https://magiccard.ai/docs/agents.md",
          "summary": "Agents should use this page as the compact source of truth for MagicPay routing, protected steps, and safe checkout behavior."
        },
        {
          "title": "Agent Skills",
          "url": "https://magiccard.ai/docs/integrations/agent-skills",
          "markdown": "https://magiccard.ai/docs/integrations/agent-skills.md",
          "summary": "Agent skills package the instructions, rules, and commands an AI runtime needs to use MagicPay safely."
        },
        {
          "title": "MagicPay SDK",
          "url": "https://magiccard.ai/docs/integrations/sdk",
          "markdown": "https://magiccard.ai/docs/integrations/sdk.md",
          "summary": "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."
        },
        {
          "title": "ChatGPT App",
          "url": "https://magiccard.ai/docs/integrations/chatgpt",
          "markdown": "https://magiccard.ai/docs/integrations/chatgpt.md",
          "summary": "The ChatGPT app gives users a familiar place to start sessions and review payment-related state while MagicPay keeps protected values outside model context."
        },
        {
          "title": "Claude App",
          "url": "https://magiccard.ai/docs/integrations/claude",
          "markdown": "https://magiccard.ai/docs/integrations/claude.md",
          "summary": "Claude can use MagicPay through the same MagicBrowse plus MagicPay skill model used by other supported agents."
        },
        {
          "title": "Telegram Miniapp",
          "url": "https://magiccard.ai/docs/integrations/telegram",
          "markdown": "https://magiccard.ai/docs/integrations/telegram.md",
          "summary": "The Telegram miniapp delivers requests, shows approvals, hands off KYC, and keeps session work out of the chat."
        }
      ]
    },
    {
      "id": "api",
      "label": "API",
      "summary": "HTTP API entry points, authentication, schema, and generated OpenAPI reference.",
      "pages": [
        {
          "title": "API Reference",
          "url": "https://magiccard.ai/docs/api",
          "markdown": "https://magiccard.ai/docs/api.md",
          "summary": "Use this page when you need the HTTP API: integration rules and the generated OpenAPI contract in one place."
        }
      ]
    },
    {
      "id": "reference",
      "label": "Reference",
      "summary": "Stable lookup pages for entities, payment methods, trust rules, and terms.",
      "pages": [
        {
          "title": "Entities",
          "url": "https://magiccard.ai/docs/reference/entities",
          "markdown": "https://magiccard.ai/docs/reference/entities.md",
          "summary": "Use this page when you need the stable nouns used across product, SDK, API, and agent flows."
        },
        {
          "title": "Payment Methods",
          "url": "https://magiccard.ai/docs/reference/payment-methods",
          "markdown": "https://magiccard.ai/docs/reference/payment-methods.md",
          "summary": "MagicPay hides payment method details from users while routing agent sessions through the best available rail."
        },
        {
          "title": "Trust System",
          "url": "https://magiccard.ai/docs/reference/trust-system",
          "markdown": "https://magiccard.ai/docs/reference/trust-system.md",
          "summary": "Agentic commerce needs trust signals across the open internet. MagicPay can store purchase outcomes, provider reputation, and flow hints after sessions."
        },
        {
          "title": "Glossary",
          "url": "https://magiccard.ai/docs/glossary",
          "markdown": "https://magiccard.ai/docs/glossary.md",
          "summary": "Use this page when a docs page mentions a term you do not recognize."
        }
      ]
    }
  ],
  "routeCount": 28
}