Venice.aix402, the internet-native payment standard built for the agent economy, is live on Venice.
Originally created by Coinbase, x402 is a neutral standard for payments over HTTP, and now governed by the Linux Foundation.
Venice is already the inference provider agents should point at: private, uncensored, every major model behind one API. x402 adds the last missing piece — a native way to pay for all of it from a wallet on Base.
x402 on Venice is live across text and reasoning, speech and transcription, embeddings, image generation, image editing, video generation, audio and music generation, and video transcription.
An agent running a multi-step workflow can think, listen, retrieve, generate images, create video, and produce audio using a single payment primitive, without a human ever provisioning an API key or adding a credit card.
Get started with x402 on Venice now.
What Agents and Builders Can Do with x402 on Venice
x402 on Venice lets builders, Claws and other agents:
- Run text and reasoning requests for writing, coding, summarization, classification, planning, and prompt generation.
- Transcribe audio and video, or generate speech with text-to-speech.
- Generate video from text prompts or existing images.
- Generate audio, music, and sound effects.
- Create embeddings for search, retrieval, and agent memory workflows.
Pay with DIEM-backed balance first, or with USDC on Base when needed. Builders can also review balance, transaction history, and top up from the same flow.
Why Every Claw Should Point at Venice
Venice already has what agents need: private and anonymous inference, uncensored models, every major model behind one API, and aggregated services across text, images, video, audio/music, speech, and search.
What was missing was a payment primitive built for agents. Every other provider still requires a human to create an account, add a credit card, and provision API keys before an agent can make its first request. x402 removes that entire step. A funded agent hits Venice, the protocol handles payment inline, and the response comes back.
Give your Claws or agents a wallet on Base, point it at Venice, and it pays for its own writing, coding, transcription, retrieval, image generation, video generation, and audio/music from its own balance.
For builders shipping wallet-native apps on Base, x402 also means users and agents can access Venice without the app ever distributing API keys or forcing a signup wall.
Get started with x402 on Venice now.
x402 activates the HTTP 402 Payment Required status code, reserved since 1995 and only recently put into production by Coinbase. The protocol is now governed by the Linux Foundation. Read the protocol at x402.org.
How It Works Under the Hood
Venice authenticates x402 requests with a signed wallet payload scoped to the endpoint being called. Venice validates the signature, checks the wallet's balance, processes the request, and charges automatically. Any EVM wallet on Base works — Coinbase Wallet, MetaMask, Phantom, and others.
If the wallet has staked DIEM, Venice uses those credits first. When daily DIEM is reached, charges fall through to USDC (on Base).
Get Started
The full setup guide, including wallet auth, supported endpoints, balance checks, top-ups, transaction history, and troubleshooting, is in the Venice docs:
Get started with x402 on Venice now.
You need an EVM wallet on Base with some USDC. If you already have staked DIEM, your daily inference credits work with x402 automatically.
Back to all posts