MagicPay SDK Overview
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
The MagicPay SDK and agent surfaces split the payment problem into bounded modules. MagicBrowse handles legacy web execution. MagicSearch finds the best provider and channel before a browser is opened. MagicPay Memory stores reusable Memory data. MagicPay Memory fill injects approved values at the trusted boundary into any target the runtime owns — an API call, a provider SDK, or a browser field. Mercuryo Bridge connects MagicPay sessions to payment account, KYC, card, balance, and transaction services. Omnichannel UI keeps the human in control.
End-To-End Shape
A typical flow starts with user intent, moves through MagicSearch for provider selection, uses MagicBrowse or an API/protocol channel for execution, pauses at Memory boundaries, resolves data or actions through MagicPay Memory and MagicPay Memory fill, and asks the user through Omnichannel UI before Mercuryo-backed payment execution proceeds.