Getting Started
Shatale is payment infrastructure for AI agents. Publishers integrate Shatale to let their agents request, authorize, and complete purchases on behalf of users — while enforcing user-approved spending policies. Shatale separates agent intent from user approval, giving publishers a secure delegation layer for payments.
Core Concepts
Agent
An AI application that can initiate purchase requests. Agents never receive raw payment credentials and operate through delegated permissions.
Delegation
A user-granted authorization allowing an agent to act within defined boundaries — time-limited, merchant-scoped, amount-limited, and revocable.
Policy
Rules controlling what an agent can buy: spending limits, merchant allowlists, category restrictions, and approval requirements. Evaluated on every purchase.
Purchase
A payment intent created by an agent. Can be auto-approved, require user confirmation, be declined by policy, or return a virtual card for checkout.
Credential
A relay email + password generated for agent checkout on merchant sites. Temporary, merchant-scoped, and revocable by the user.
How It Works
Publisher registers an agent and configures capabilities
User grants delegation — defines what the agent can buy, with limits
Agent calls request_purchase with merchant, amount, and description
Shatale evaluates policy, checks delegation, and runs risk controls
Purchase completes (card issued) or returns for user action
Prerequisites
API Key — create from API Keys page. Use sandbox key (sk_sandbox_*) for testing.
MCP Server — install with npx shatale-mcp-server@2.1.3