The Tator Trader API enables AI agents and autonomous wallets to execute trades, bridge assets, and interact with DeFi protocols using natural language β all without API keys or subscriptions.
Who Is This For?
AI Agent Platforms β Lobster, OpenClaw, Coinbase Agentic Wallets
Autonomous Trading Bots β Agents that manage their own wallets
Developers β Building AI-powered trading interfaces
MCP Integrations β Model Context Protocol tool builders
Key Benefits
π Permissionless Access
No API keys. No registration. No approval process. Just pay per call with USDC and start trading.
π Non-Custodial
You keep your keys. Tator returns unsigned transaction data that your agent signs and broadcasts. We never touch your funds.
π£οΈ Natural Language
Send plain English instructions:
"Buy $50 worth of ETH on Base"
"Bridge 100 USDC from Arbitrum to Optimism"
"What's the price of PEPE?"
βοΈ Multi-Chain
20+ blockchains supported including Ethereum, Base, Arbitrum, Optimism, Polygon, Solana, MegaETH, and more.
π‘οΈ Built-in Security
Every trade is scanned by Quick Intel for honeypots, scams, and risky contracts before execution.
$0.20 per API call β paid in USDC via the x402 protocol.
No subscriptions, no minimums β pay only for what you use.
Note: You are charged per API call regardless of whether the prompt results in a transaction. Unclear or invalid prompts will return a clarifying response but still incur the fee. See Prompt Best Practices below.
Prompt Best Practices
To get the best results and avoid wasted calls, follow these guidelines:
β Good Prompts
β Bad Prompts
Best Practices
Always Include
Why
Chain name
"on Base", "on Arbitrum", "on Ethereum"
Token symbol OR contract address
Use CA for obscure tokens
Amount with unit
"$50 worth" or "100 USDC"
Action
"buy", "sell", "swap", "bridge", "send"
What Happens with Unclear Prompts?
If your prompt is unclear or missing information:
You still pay the API fee ($0.20)
Response type will be info or error
The response text will ask for clarification
Example:
Tip: Validate prompts client-side before sending to avoid unnecessary charges.
Supported Payment Networks
Pay from any of these chains:
Chain
Token
Base
USDC
Ethereum
USDC
Arbitrum
USDC
Optimism
USDC
Polygon
USDC
Avalanche
USDC
Unichain
USDC
Linea
USDC
MegaETH
USDM
Quick Example
Request:
Response:
Your agent then signs the transaction and broadcasts it to the blockchain.
βββββββββββββββββββ
β AI Agent β
β (Your Wallet) β
ββββββββββ¬βββββββββ
β
β 1. Send prompt + x402 payment ($0.20 USDC)
βΌ
βββββββββββββββββββ
β Tator API β
β x402 Gateway β
ββββββββββ¬βββββββββ
β
β 2. Process with AI
βΌ
βββββββββββββββββββ
β Tator Eliza β
β Trading Engine β
ββββββββββ¬βββββββββ
β
β 3. Return unsigned transaction
βΌ
βββββββββββββββββββ
β AI Agent β
β Signs & Sends β
ββββββββββ¬βββββββββ
β
β 4. Broadcast to blockchain
βΌ
βοΈ On-Chain
"Buy $50 worth of ETH on Base"
"Swap 100 USDC for WETH on Arbitrum"
"Bridge 50 USDC from Ethereum to Base"
"What is the price of 0x4ed4e862860bed51a9570b96d89af5e1b0efefed on Base?"
"Send 10 USDC to 0x742d35Cc6634C0532925a3b844Bc9e7595f7AAAA on Base"
"Buy some crypto" β Missing: token, amount, chain
"Get me ETH" β Missing: amount, chain
"Trade tokens" β Missing: everything
"What's the price?" β Missing: token
"Buy XYZ" β Ambiguous token, no chain
{
"success": true,
"type": "info",
"response": "I'd be happy to help you buy tokens! Could you please specify: 1) Which token you want to buy, 2) How much (in USD or token amount), and 3) Which chain (e.g., Base, Ethereum, Arbitrum)?",
"transactions": []
}
curl -X POST https://x402.quickintel.io/v1/tator/prompt \
-H "Content-Type: application/json" \
-H "PAYMENT-SIGNATURE: " \
-d '{
"prompt": "buy $10 worth of ETH on base",
"walletAddress": "0xYourWallet...",
"provider": "your-agent-name"
}'