# Aftercard Agent Index Aftercard is payment infrastructure for personal AI agents. It combines Aftercard Card, built-in browser, MagicSearch, Aftercard Memory, Payment Bridge, and omnichannel approvals so user-authorized agents can complete purchases without asking users to paste card data, passwords, identity fields, OTPs, or final payment confirmations into chat. ## Canonical Machine Routes - LLM index: https://aftercard.ai/llms.txt - Full docs text: https://aftercard.ai/llms-full.txt - Agent skill installer: https://aftercard.ai/skill.md - Agent JSON index: https://aftercard.ai/agent-index.json - OpenAPI JSON: https://aftercard.ai/docs/openapi.json - Support: support@aftercard.ai ## Required Agent Rules - Use MagicSearch to find provider-method URLs, official docs, and guidance; execute with your own capabilities. - Use built-in browser for ordinary commerce navigation. - Use Aftercard requests for protected data, choices, approvals, and payments. - Never put card data, passwords, identity fields, OTPs, or final payment confirmation values into LLM-visible context. - Stop at every protected step and wait for Aftercard before continuing. ## Overview Understand Aftercard as payment infrastructure for personal AI agents before choosing a component or guide. - Aftercard Docs: https://aftercard.ai/docs | Markdown: https://aftercard.ai/docs/index.md | Aftercard gives personal AI agents one user-authorized payment stack: Aftercard Card, Memory requests, and routing across browser, API, and agentic payment rails. ## Components Learn the modules behind agent payments and protected checkout execution. - Aftercard Components: https://aftercard.ai/docs/components | Markdown: https://aftercard.ai/docs/components.md | Aftercard 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. - Aftercard Card: https://aftercard.ai/docs/magiccard | Markdown: https://aftercard.ai/docs/magiccard.md | Aftercard Card turns agentic payments, crypto, APIs, browser checkout, and new payment protocols into one simple top-up balance. - MagicFill: https://aftercard.ai/docs/components/magicfill | Markdown: https://aftercard.ai/docs/components/magicfill.md | The host built-in browser analyzes the page; MagicFill only materializes and applies exact protected values and one exact final click. - MagicSearch: https://aftercard.ai/docs/components/magicsearch | Markdown: https://aftercard.ai/docs/components/magicsearch.md | MagicSearch answers natural-language discovery questions with provider and method names, useful URLs, official documentation, and concise operating guidance. The agent performs the work. - Aftercard Memory: https://aftercard.ai/docs/components/memory | Markdown: https://aftercard.ai/docs/components/memory.md | Aftercard Memory stores user-owned items and protected fields so agents can request the right data during a workflow without seeing raw values. - Aftercard Memory fill: https://aftercard.ai/docs/components/memory-fill | Markdown: https://aftercard.ai/docs/components/memory-fill.md | Aftercard 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. - Payment Bridge: https://aftercard.ai/docs/components/payment-bridge | Markdown: https://aftercard.ai/docs/components/payment-bridge.md | Payment Bridge is the backend connectivity layer that gives agents a simple Aftercard interface while payment operations run through provider-backed infrastructure. - Omnichannel UI: https://aftercard.ai/docs/components/omnichannel-ui | Markdown: https://aftercard.ai/docs/components/omnichannel-ui.md | Aftercard 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://aftercard.ai/docs/getting-started | Markdown: https://aftercard.ai/docs/getting-started.md | Install the Aftercard skill, connect the runtime to the remote MCP, then top up Aftercard Card before the first low-risk payment session. - Set Up Your Account: https://aftercard.ai/docs/guides/account-setup | Markdown: https://aftercard.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://aftercard.ai/docs/guides/connect-agent | Markdown: https://aftercard.ai/docs/guides/connect-agent.md | Use this guide to install the native Aftercard plugin, authenticate its remote MCP, verify capabilities, and run the first Memory-managed workflow. - E2E Purchase Flow: https://aftercard.ai/docs/guides/e2e-purchase | Markdown: https://aftercard.ai/docs/guides/e2e-purchase.md | The built-in agent clarifies intent, searches providers, selects a channel, uses built-in browser or an agentic protocol, and raises user requests during the session. - SDK Purchase Flow: https://aftercard.ai/docs/guides/sdk-purchase | Markdown: https://aftercard.ai/docs/guides/sdk-purchase.md | Your own agent can search, browse, and reason independently, then call Aftercard SDK to resolve a protected value or run a protected payment action. - Manage Memory: https://aftercard.ai/docs/guides/manage-secrets | Markdown: https://aftercard.ai/docs/guides/manage-secrets.md | Saved Memory items reduce repeated questions while protected values stay behind Aftercard requests. - Manage Subscriptions: https://aftercard.ai/docs/guides/subscriptions | Markdown: https://aftercard.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://aftercard.ai/docs/guides/troubleshooting | Markdown: https://aftercard.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://aftercard.ai/docs/agents | Markdown: https://aftercard.ai/docs/agents.md | Agents should use this page as the compact source of truth for Aftercard routing, protected steps, and safe checkout behavior. - Agent Skills: https://aftercard.ai/docs/integrations/agent-skills | Markdown: https://aftercard.ai/docs/integrations/agent-skills.md | Agent skills package the instructions, rules, and commands an AI runtime needs to use Aftercard safely. - Aftercard SDK: https://aftercard.ai/docs/integrations/sdk | Markdown: https://aftercard.ai/docs/integrations/sdk.md | The SDK is the right entry point when you own the surrounding agent, browser, or backend runtime and need Aftercard as the Memory request layer. - ChatGPT App: https://aftercard.ai/docs/integrations/chatgpt | Markdown: https://aftercard.ai/docs/integrations/chatgpt.md | The ChatGPT app gives users a familiar place to start sessions and review payment-related state while Aftercard keeps protected values outside model context. - Claude App: https://aftercard.ai/docs/integrations/claude | Markdown: https://aftercard.ai/docs/integrations/claude.md | Claude can use Aftercard through the same built-in browser plus Aftercard skill model used by other supported agents. - Telegram Miniapp: https://aftercard.ai/docs/integrations/telegram | Markdown: https://aftercard.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://aftercard.ai/docs/api | Markdown: https://aftercard.ai/docs/api.md | Use this page when you need the HTTP API: integration rules and the generated OpenAPI contract in one place. - Public Directory: https://aftercard.ai/docs/api/directory | Markdown: https://aftercard.ai/docs/api/directory.md | Use this page when an agent or a page needs to find sellers without an account: natural-language search, the filterable list, one provider method with its guidance, and the trust record behind a hostname. ## Reference Stable lookup pages for entities, payment methods, trust rules, and terms. - Entities: https://aftercard.ai/docs/reference/entities | Markdown: https://aftercard.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://aftercard.ai/docs/reference/payment-methods | Markdown: https://aftercard.ai/docs/reference/payment-methods.md | Aftercard hides payment method details from users while routing agent sessions through the best available rail. - Trust System: https://aftercard.ai/docs/reference/trust-system | Markdown: https://aftercard.ai/docs/reference/trust-system.md | Agentic commerce needs trust signals across the open internet. Aftercard can store purchase outcomes, provider reputation, and flow hints after sessions. - Glossary: https://aftercard.ai/docs/glossary | Markdown: https://aftercard.ai/docs/glossary.md | Use this page when a docs page mentions a term you do not recognize.