Glossary

Use this page when a docs page mentions a term you do not recognize.

Core Product Terms

These terms describe the public Aftercard product model.

Term	Meaning
Aftercard	The agent payment layer that owns sessions, requests, approvals, protected-data handling, and payment execution.
Aftercard Card	The simple user-facing payment instrument and balance abstraction given to an agent.
MagicFill	The deliberately small actuator that materializes protected values into exact targets supplied by a host browser.
MagicSearch	The semantic registry used to find provider-method URLs, docs, and guidance.
Aftercard Memory	The user-owned store for reusable data an agent can use — logins, identity, addresses, and payment methods. Often shortened to "Memory".

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 Aftercard or built-in browser.
Remote MCP	The authenticated remote tool server that owns Aftercard sessions, approvals, protected grants, and reconciliation.
Workflow session	One Aftercard server-side task grouping related requests and events.

These terms describe the human-in-the-loop and context-isolation payment model.

Term	Meaning
Request	One user-facing checkpoint for an approval, a choice, a protected value, or an action.
Approval	Explicit user authorization that allows a payment or another sensitive operation to continue.
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 inside the trusted fill path 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.