Glossary
Use this page when a docs page mentions a term you do not recognize.
Core Product Terms
These terms describe the public MagicPay product model.
| Term | Meaning |
|---|---|
| MagicPay | The agent payment layer that owns sessions, requests, approvals, Memory data handling, and payment execution. |
| MagicCard | The simple user-facing payment instrument and balance abstraction given to an agent. |
| MagicBrowse | The commerce-specialized browser automation layer for checkout and payment flows. |
| MagicSearch | The indexed commerce search layer used to find and rank providers. |
| MagicPay Memory | The user-owned store for reusable data an agent can use — logins, identity, addresses, and payment methods. Often shortened to "Memory". |
Runtime Terms
These terms appear in SDK, API, and agent setup docs.
| Term | Meaning |
|---|---|
| Runtime | The environment where the agent runs, such as Codex, Claude, OpenClaw, ChatGPT, or another supported tool. |
| Skill | A reusable instruction bundle that tells a runtime how to use MagicPay or MagicBrowse. |
| CLI | A command-line tool the runtime can execute after reading the skill instructions. |
| Workflow session | One MagicPay server-side task grouping related requests and events. |
Request and Memory Terms
These terms describe the human-in-the-loop and context-isolation payment model.
| Term | Meaning |
|---|---|
| Request | One user-facing checkpoint for approval, choice, Memory data, or action execution. |
| Artifact | The one-time result of a completed request. |
| Memory item | A reusable user-owned record (login, identity, address, payment method) that holds related fields. |
| Handle | An opaque reference to a stored value, materialized only at the trusted boundary and never shown to the model. |
| Secret | A field marked sensitive, such as a password, card number, CVV, or document number. The marker adds stricter handling — redaction, logging, and extra caution — on top of normal Memory handling; it is not a separate release path. |
| Profile fact | Reusable open user-provided data with a flexible key, such as name, preference, or task-specific facts. |
| Trust rule | A policy that decides whether a request can auto-resolve or must ask the user. |