MagicPay Components

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.

Component Map

MagicPay splits the payment problem into modules with clear edges. built-in browser handles web execution. MagicSearch finds relevant provider-method instructions without executing them. MagicPay Memory stores reusable user data. MagicPay Memory fill writes approved values into any target the runtime owns — an API call, a provider SDK, or a browser field. Payment Bridge connects MagicPay sessions to payment account, KYC, card, balance, and transaction services. Omnichannel UI keeps the human in control.

MagicCard A single balance and payment interface your personal agent can use across provider-backed cards, crypto, swaps, and agentic rails. MagicFill Exact protected-field materialization and clicks behind the host browser bridge. MagicSearch Semantic provider-method lookup with URLs, official docs, and agent guidance. MagicPay Memory User-owned storage for logins, identity details, payment cards, and reusable checkout fields. MagicPay Memory fill Applies user-approved values to the target — a browser field, API header, or provider call — so values never reach the LLM. Payment Bridge Payment backend bridge for account linking, KYC, card issuance, top-up, and execution callbacks. Omnichannel UI Web, mobile, Telegram, ChatGPT, Claude, and browser-extension apps for approvals and supervision.

End-To-End Shape

A typical flow starts with user intent, optionally uses MagicSearch to find provider-method guidance, then lets the agent execute through built-in browser or an API/protocol channel. Protected steps use MagicPay Memory and MagicPay Memory fill, and Omnichannel UI asks the user before payment execution proceeds.

Component Map

End-To-End Shape

Related Docs