Agent wallet and marketplace
Kawase pays for services per call over x402 from its own agent wallet, inside a daily budget and a per-call cap you set, from Circle's catalog of paid tools on Arc, with every purchase receipted.
x402 is an open standard for paying for a web request with stablecoins: the service answers "402 Payment Required" with a price, the client pays in USDC and gets the result. Kawase uses it to buy answers for you: web search and news, prediction-market odds, DefiLlama yields and prices, stock prices, data enrichment, from Circle's x402 catalog on Arc.
The marketplace
Markets → Marketplace (in the sidebar on a computer) lists every paid tool your agent can call: about 84 on Arc mainnet, by category, each with its seller's mark, its price per call and how many calls a dollar buys.


Search, or browse by category: data, search and research, social, infrastructure, finance, creative, prediction markets.
- Search services
- Categories, with counts
- A service: seller, endpoints, price per call
Each service shows what it returns, how it can be paid (Circle Gateway, or any wallet), its endpoints and price range, and Try it: one real call, paid from the agent wallet.
- Who sells it, and first or third party
- How it can be paid
- Try it for its price
Your agent wallet
Purchases never come out of your main wallet directly. Kawase keeps a separate agent wallet for you, and it can only spend what you put in.


- Its balance
- Ready to pay (Circle Gateway) and on hand (plain USDC)
- Top up from your wallet
- Or buy straight into it
- Top up from your Kawase wallet with a preset. The first top-up asks you to confirm once: Kawase may then move USDC only into your agent wallet, with a daily limit. Or top up with Apple Pay or a card, straight into it.
- Its balance is split between Circle Gateway (ready for nanopayments, which most sellers take) and a part on hand for sellers that take plain USDC. Kawase refills what's on hand from Gateway itself.
- Return to my wallet sends both parts back at any time.
Budgets you set
- a daily budget and a per-call cap;
- ask me before every purchase, or only above the cap, on a consent card in chat;
- the categories Kawase may buy from;
- blocked sellers: tap any purchase to block its seller.
Tightening applies at once; loosening asks you to confirm. A refusal names the rule that stopped it.
Every purchase receipted
Chat shows what Kawase found (the seller's mark, what it returns, the price) and, after paying, a receipt: "Paid 0.002 USDC to …". The seller's answer is labelled unchecked. x402 has no refund standard yet: if a call fails after payment, the receipt says the seller kept it; a payment that Circle reports as failed is marked not charged. Kawase treats outside text as data, never as instructions.
Networks
- Mainnet: Circle's catalog, paid over both rails.
- Testnet: Circle's catalog has no testnet listings, so Kawase runs its own demo seller (
seller.getkawase.xyz) to try it end to end with test money.
Pay for services (x402)
What runs today
- finding paid services in Circle's x402 catalog on Arc (web search and news, prediction-market odds, DefiLlama yields and prices, stock prices, data enrichment) and paying for one call from the person's own agent wallet, within a daily budget and a per-call cap they set
- both payment rails: Circle Gateway nanopayments (most listings) and plain EIP-3009 USDC
- the Agent wallet page: balance (in Gateway and on hand), top up from the Kawase wallet under a capped grant or with Apple Pay or a card through Circle's Onramp, return to the wallet, budget, categories, blocked sellers, history
- on testnet, Kawase's own demo seller (Circle's catalog has no testnet listings)
Not yet
- refunds from sellers (x402 has no refund standard yet; a receipt says so when a seller kept a payment for a failed call)
- subscriptions or streaming payments