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
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, with its own limits and capabilities.
Limits must be consistent:
max_per_transaction can’t exceed max_daily_amount, which can’t exceed max_monthly_amount. Any limit you leave out falls back to the wallet’s global limit.
You can have multiple connectors per wallet for different agents or environments.
Capabilities
Every connector has an explicit list of capabilities. A request outside that list is rejected.
New connectors get
transfer only. Add x402 or prediction_market deliberately when you create or update the connector.
Agent API
Once a connector is active, the agent authenticates with its API key (Authorization: Bearer yac_...) and calls the Agent API directly:
The Agent API allows 30 requests per minute.
Discover capabilities
Agents can check what they’re allowed to do before acting:GET /agent/openapi.json returns an OpenAPI description of the same surface, so any OpenAPI-aware agent framework (LangChain, GPT Actions, custom code) can discover it.
Send a Payment
Response
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:Response
Prediction markets
Connectors with theprediction_market capability can trade prediction markets from a Solana agentic wallet, paying in USDC. Every trade goes through the same limits and rules as a payment, and a trade that would move more USDC than authorized is refused.
Search markets
Place a trade
Send an
Idempotency-Key header (or idempotency_key field) so a retried trade isn’t placed twice.
Trade limits (set per connector in prediction_market_config):
max_position_usd— largest single trade.allowed_categories— if set, trades must name one of these categories.allowed_providers— if set, only these providers can be used.
Payment Categories
Every agent transaction requires apayment_category for audit and analytics:
Pricing
Agentic wallet pricing is tier-based. Check the current pricing:Next Steps
API Reference
Full endpoint reference for all agentic wallet operations.
Sandbox
Test agentic wallets in the sandbox environment.
Webhooks
Get notified on agent transaction events.

