Skip to main content
Agentic Wallets give AI agents their own self-custodial crypto wallets. Each wallet is a programmable spending account that AI services can use to send payments, pay for x402 paywalled APIs, and keep an immutable audit trail of every dollar spent. Built for the agentic economy — where AI agents need to pay for services, tools, and data autonomously.

​
How It Works

1

Create a wallet

Create an agentic wallet from the dashboard or via API. Each wallet gets its own on-chain address with USDC funding support.
2

Activate with 2FA

Activate the wallet using email OTP and/or TOTP verification. This ensures only the wallet owner can authorize the wallet for agent use.
3

Add connectors

Generate API keys (connectors) that your AI agent uses to authenticate. Each connector can have its own spending limits and permissions.
4

Fund the wallet

Deposit USDC into the wallet’s on-chain address, or use the manual funding endpoint to top up from your main account.
5

Let your agent transact

The agent uses its connector API key to send payments, pay for x402 APIs, and check balances — all with per-transaction audit trails.

​
Key Features

Per-Agent API Keys

Each connector gets a unique API key (yac_...) with configurable spending limits. Revoke a connector without affecting the wallet.

x402 Protocol Support

Built-in support for the x402 payment protocol. Your agent can fetch paywalled APIs and the wallet auto-pays the 402 response.

Spending Limits

Set per-transaction, daily, and monthly limits at the wallet level and per connector. Enforce budget controls before the agent can overspend.

Full Audit Trail

Every transaction records the service name, URL, payment reason, and category. Built for compliance and cost attribution.

Auto-Funding

Configure automatic top-ups when the wallet balance drops below a threshold. Funds are pulled from your main account.

Multi-Chain Support

Wallets support USDC across multiple chains. Pay services on any supported network.

​
Wallet Lifecycle

StatusDescription
createdWallet exists but cannot transact until activated
activatingOTP verification in progress
activeFully operational — agents can transact
suspendedTemporarily halted by admin (e.g., suspicious activity)
deactivatedPermanently disabled by the owner

​
Connectors

Connectors are API keys tied to a specific wallet. Think of them as “agent credentials” — each AI agent or service integration gets its own connector.
FieldDescription
nameHuman-readable label (e.g., “Production Agent”)
api_keyStarts with yac_ — used by the agent for authentication
per_transaction_limitMax USD amount per single transaction
daily_limitMax USD amount per 24-hour period
monthly_limitMax USD amount per calendar month
statusactive or revoked
You can have multiple connectors per wallet for different agents or environments.

​
Agent API

Once a connector is active, the agent authenticates with its API key and hits the Agent API directly:
EndpointDescription
POST /agent/transactSend a crypto payment
GET /agent/balanceCheck wallet balance
GET /agent/transactionsList recent transactions
POST /agent/x402-fetchFetch a URL with automatic x402 payment

​
Send a Payment

curl -X POST 'https://crypto-api.yativo.com/api/v1/agent/transact' \
  -H 'Authorization: Bearer yac_connector_api_key' \
  -H 'Content-Type: application/json' \
  -d '{
    "wallet_id": "aw_01abc123",
    "amount": 5.00,
    "asset": "USDC",
    "recipient_address": "0x9F8b3A2c1E4D7F6B5A4C3D2E1F0A9B8C7D6E5F4",
    "service_name": "OpenAI API",
    "service_url": "https://api.openai.com",
    "payment_reason": "GPT-4 inference for customer support bot",
    "payment_category": "ai_service"
  }'
Response
{
  "success": true,
  "data": {
    "transaction_id": "atx_01pqr456",
    "tx_hash": "0xabc123...",
    "amount": 5.00,
    "asset": "USDC",
    "recipient_address": "0x9F8b...",
    "chain": "base",
    "status": "completed",
    "fee": 0.00,
    "is_free_transaction": true
  }
}

​
x402 Protocol Fetch

The x402 protocol enables HTTP-native micropayments. When your agent fetches a URL that returns HTTP 402 (Payment Required), the wallet automatically pays and retries: 
curl -X POST 'https://crypto-api.yativo.com/api/v1/agent/x402-fetch' \
  -H 'Authorization: Bearer yac_connector_api_key' \
  -H 'Content-Type: application/json' \
  -d '{
    "wallet_id": "aw_01abc123",
    "url": "https://api.example.com/premium-data",
    "method": "GET"
  }'
Response
{
  "success": true,
  "data": {
    "status": 200,
    "paid": true,
    "payment": {
      "amount_usd": 0.01,
      "asset": "USDC",
      "network": "base",
      "pay_to": "0x..."
    },
    "body": { "premium_data": "..." }
  }
}

​
Payment Categories

Every agent transaction requires a payment_category for audit and analytics:
CategoryUse Case
ai_servicePaying for AI model inference, embeddings, etc.
prediction_marketPlacing bets or funding prediction contracts
legal_escrowEscrow payments for legal or contractual obligations
subscriptionRecurring service subscriptions
purchaseOne-time purchases or API credits
transferWallet-to-wallet transfers
settlementSettling invoices or outstanding balances
otherAnything not covered above

​
Pricing

Agentic wallet pricing is tier-based. Check the current pricing: 
curl -X GET 'https://crypto-api.yativo.com/api/v1/agentic-wallets/pricing' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Each plan includes a number of free transactions per month. Transactions beyond the free tier incur a small per-transaction fee.

​
MCP Server Integration

For AI agents using the Model Context Protocol, install the @yativo/mcp-server package. It exposes agentic wallet operations as MCP tools that any MCP-compatible AI agent can call directly.

​
Next Steps

API Reference

Full endpoint reference for all agentic wallet operations.

MCP Server

Connect AI agents via the Model Context Protocol.

Sandbox

Test agentic wallets in the sandbox environment.

Webhooks

Get notified on agent transaction events.