Nuncio Docs
Nuncio gives personal AI agents one user-authorized payment stack: MagicCard, Secrets requests, and routing across browser, API, and agentic payment rails. Product and developer documentation for Nuncio, the payment infrastructure for personal AI agents. MagicCard, requests, secrets, and approvals stay under the human owner's control.
What Nuncio Is
Nuncio is designed to be the universal payment tool for a personal AI agent. The agent can use provider-backed cards and payment operations, APIs, crypto rails, browser checkout, and agent-native protocols to get the job done, while the user sees a simple MagicCard with one balance. MagicCard makes payments in the complex world of agentic protocols, new payment standards, and crypto feel as simple as topping up a card.
Nuncio Overview
Nuncio is payment infrastructure for personal AI agents. The goal is to feel as simple as Apple Pay for users and their agents while hiding wallets, cards, protocols, approval routing, and protected execution behind one MagicCard interface.
Purchase Loop
Every purchase is a session: the personal agent clarifies intent, Nuncio raises requests when user authority is needed, and execution continues through the best available payment rail.
Build With Nuncio
Connect your agent through remote MCP for purchase requests, decisions and payment tracking while the host owns its native browser.
Choose Your Path
Use the docs path that matches what you want to do next.
Recommended Path
Most users and builders should follow the same staged path before a real payment. This keeps setup, safety, and payment authority understandable for both humans and agents.
- Create a Nuncio account and complete account, KYC, and balance prerequisites.
- Connect one agent runtime and verify that Nuncio and built-in browser are available.
- Run a browser-only task so the agent proves it can navigate without any protected data.
- Run a low-risk protected form handoff, such as a shipping address.
- Add reusable Nuncio Secrets values only after the user understands what will be stored.
- Move to MCP, API, or full purchase flows once request handling is observable end to end.
Use Case Entry Points
Start from the workflow you are trying to ship. The components underneath are modular, but each path trusts the agent with a different amount.