Viatika — AI Agent Payment Infrastructure
What is Viatika
Viatika is an enterprise platform that lets AI agents pay for resources using the x402 protocol. When your agent hits an HTTP 402 Payment Required response, Viatika evaluates policies, checks budgets, signs the payment with EIP-712 cryptography, and returns headers so the agent can retry and access the resource. The agent never holds private keys or manages wallets.
Viatika handles: authentication → policy evaluation → budget enforcement → EIP-712 signing → audit logging. Your agent handles: detecting 402 → calling Viatika → retrying with payment headers.
The Problem Viatika Solves
AI services increasingly return 402 Payment Required instead of API keys. The response contains a structured x402 payload specifying how much to pay, where to pay, and on which blockchain. Without Viatika, your agent would need:
- A funded crypto wallet with private key access
- Logic to parse x402 payloads and construct EIP-712 signatures
- Budget controls to prevent runaway spending
- Audit trails for compliance
Viatika handles all of this. Your agent makes one API call.
Integration Paths
| Path | Best for | Setup time | How it works |
|---|---|---|---|
| MCP Server | Claude Desktop, coding agents with MCP support | 5 min | Binary runs locally, exposes pay_for_resource and check_balance tools via stdio |
| REST API | Any HTTP client, custom agents, scripts | 5 min | Direct POST /v1/x402/sign-payment calls |
→ Quickstart Guide
→ MCP Integration
→ REST API Reference
Key Concepts
Credits: Viatika's internal unit of account. 1 credit = $0.001 USD. Organizations purchase credits; Viatika's platform wallet pays on-chain.
Policy Engine: Every payment request is evaluated against Cedar policies, budget limits, and whitelists before signing. Denied requests never produce a signature.
Payment Signing: Viatika signs ERC-3009 transferWithAuthorization payloads using EIP-712 typed data. The signature authorizes USDC transfer from Viatika's platform wallet to the service provider.
x402 Protocol: An HTTP-native payment protocol. Services return 402 with a JSON payload describing accepted payment methods. Clients respond with signed payment in X-Payment headers.
→ Deep Dive: Concepts
→ Agent Prompt Guide
Documentation Map
| Document | Contents |
|---|---|
| Quickstart | Get running in 5 minutes |
| API Reference | Full REST API with JSON schemas and curl examples |
| MCP Integration | MCP server setup for Claude and other agents |
| Concepts | x402 protocol, credits, policies, EIP-712, settlement |
| Agent Prompt Guide | System prompt snippets for teaching agents to pay |