VetoVetoDocs
Getting Started

Getting Started

Install the Veto Checkout SDK, stand up a checkout, and understand the path from zero to a published, agent-discoverable storefront.

Getting a checkout that AI agents can buy from is three moves: describe what you sell, set your policy and receiving address, and mount the SDK. Everything else — discovery, self-describing payment instructions, the acceptance gate, signed receipts — the SDK does for you.

New here? Read this first.

How Veto works — discover, pay, deliver is the whole model in plain English: an agent discovers your checkout, pays you USDC over x402, and then you deliver the goods — triggered by a signed webhook on every sale (the part merchants ask about most: "after the agent pays, how does the buyer get what they paid for?").

On the hosted platform? Start here.

If you're using the hosted control plane at https://merchants.veto-ai.com, the fastest path is Set up Veto end-to-end (hosted) — sign in, mint keys, create a merchant, publish, and watch an AI agent buy your product over x402, with copy-paste curls. No SDK to host. Or hand the whole thing to your coding agent via MCP.

The path

Scaffold or install

The fastest start is the scaffolder, which writes a runnable merchant and a buyer agent that complete a sandbox checkout in one command:

npx @veto-protocol/create-checkout my-shop --template quickstart

Already have a project? Add the SDK directly — it has zero runtime dependencies and runs on Node ≥ 22.6:

npm install @veto-protocol/checkout

Stand up a checkout

createCheckout(config) is the one call you make. See the Quickstart for the 5-minute scaffolded path and the same thing built from scratch.

Publish your manifest

An agent starts at GET /.well-known/agentic-checkout.json and follows the next field in every response. It never needs to read these docs at runtime.

Next