# Zanora

> Zanora is the commerce layer for AI agents: sellers make any HTTP API or MCP tool purchasable per call, and buyers' agents discover and pay for those capabilities from their own wallets, inside spending rules a human sets. Payment is the x402 handshake (402 → signed proof → signed receipt) over HTTP or MCP.

Every page below is Markdown. The hosted gateway is https://api.zanora.dev; the human console (signup, approvals, funding) is https://console.zanora.dev. Money on the wire is always a string of integer minor units ("100" = $1.00).

## Get started — Introduction

- [Introduction](https://docs.zanora.dev/index.md): Zanora is the commerce layer for AI agents. Sellers make an API or MCP tool payable per call. Buyers' agents find it and pay from their own wallets, within spending rules a person sets.
- [Quickstart](https://docs.zanora.dev/quickstart.md): Pay for your first capability in about five minutes. You sign up as a buyer, give an agent a funded wallet, and buy one call from the live demo seller.
- [How Zanora works](https://docs.zanora.dev/how-it-works.md): Who is involved, what happens during one paid call, and where the money goes afterwards. The flow is the same over HTTP and MCP.
- [Building with AI agents](https://docs.zanora.dev/agents.md): How an AI agent should read these docs, which onboarding steps it can do alone and which need a person, and the rules it should follow when money is involved.

## Get started — Core concepts

- [Accounts and API keys](https://docs.zanora.dev/concepts/accounts-and-keys.md): Tenants, API keys, scopes and console logins. Everything that authenticates you to Zanora, and how to keep it narrow.
- [Money and amounts](https://docs.zanora.dev/concepts/money.md): How to write an amount, how prices and fees are calculated, and why a balance is always calculated from the ledger and never stored.
- [Capabilities and discovery](https://docs.zanora.dev/concepts/capabilities.md): What a capability is, the two protocols and two kinds of address, how discovery ranks results, and why an unverified seller doesn't appear in it.
- [Receipts](https://docs.zanora.dev/concepts/receipts.md): Every paid call produces a receipt signed by Zanora and bound to the exact response. What it contains, how to check it, and how to find old ones.
- [Errors and refusals](https://docs.zanora.dev/concepts/errors.md): The error envelope, what each error code means, whether any money moved, and what to do next. The page to keep open while you integrate.

## Get started — Tooling

- [Packages](https://docs.zanora.dev/packages.md): The six npm packages. What each is for, who installs it, and which one to pick for your role and protocol.
- [Hosted and local environments](https://docs.zanora.dev/environments.md): The hosted platform is the default for everything. How to point a package at a different gateway, and how to run one locally for development.

## Buyers — Get started

- [Buyer overview](https://docs.zanora.dev/buyers/overview.md): What a buyer sets up once — a workspace, wallets, policies — and the three ways an agent can then buy. Pick your path here.
- [Buyer quickstart](https://docs.zanora.dev/buyers/quickstart.md): From nothing to a verified purchase using only the API — signup, keypair, wallet, funding, policy, discover, pay. Every step is a copy-paste command.

## Buyers — Set up

- [Create a workspace](https://docs.zanora.dev/buyers/signup.md): Sign up as a buyer from the console or the API, confirm your email, and keep the root key safe. Nothing is created until the address is confirmed.
- [Wallets and agent keys](https://docs.zanora.dev/buyers/wallets.md): Each agent gets a wallet and an ed25519 keypair. The wallet holds the public key and the agent holds the private key. How to create both, and how to look after them.
- [Funding a wallet](https://docs.zanora.dev/buyers/funding.md): Top up by card or bank, or send USDC on Base to a deposit address. Money is credited when the payment rail confirms it. Ask the gateway which options it offers before you choose one.
- [Spending policies and budgets](https://docs.zanora.dev/buyers/policies.md): Rules the gateway applies to every purchase before any money moves — deny, require approval, or allow-list — plus a daily budget for the whole workspace.
- [Approvals](https://docs.zanora.dev/buyers/approvals.md): When a policy holds a purchase for a person, how they approve or deny it, how the agent finds out, and how to make sure a model can never approve its own spend.

## Buyers — Buy

- [Buy from an MCP client](https://docs.zanora.dev/buyers/mcp.md): Add @zanora/mcp to Claude, Cursor or any MCP client, and the model can discover, pay for and verify capabilities from its own wallet with no integration code.
- [Buy from code with the SDK](https://docs.zanora.dev/buyers/sdk.md): @zanora/sdk in TypeScript: discover capabilities, pay for REST and MCP ones with the same call, verify receipts, handle refusals, and cancel safely.
- [Use one seller's tools directly](https://docs.zanora.dev/buyers/mcp-proxy.md): @zanora/mcp-proxy puts one paid MCP server in front of your agent. Its tools appear under their own names with their own schemas, and each call is paid for as it's made.
- [Running seller packages](https://docs.zanora.dev/buyers/local-packages.md): Some MCP capabilities are a pinned npm package that you run locally, rather than a server you call. This is off by default. Here's how to allow a specific package, and what protects you when you do.

## Buyers — After the purchase

- [Purchases, ledger and ratings](https://docs.zanora.dev/buyers/history.md): What your agents bought, what moved in each wallet, and how to rate sellers so discovery keeps ranking good ones first.
- [Buyer troubleshooting](https://docs.zanora.dev/buyers/troubleshooting.md): The problems buyers run into most, what causes each one, and the fix.

## Sellers — Get started

- [Seller overview](https://docs.zanora.dev/sellers/overview.md): What selling on Zanora involves, what you never have to build, and which integration fits your server — an MCP tool, an HTTP endpoint, or a package buyers run themselves.
- [Seller quickstart](https://docs.zanora.dev/sellers/quickstart.md): Sell an MCP tool on the hosted platform. Sign up, ask for verification, publish and serve with one call, make a test purchase, and see the sale land.

## Sellers — Set up

- [Create a provider account](https://docs.zanora.dev/sellers/signup.md): Sign up as a seller, confirm your email, and receive your provider id, settlement wallet and API key.
- [Getting verified](https://docs.zanora.dev/sellers/verification.md): Your capabilities stay out of discovery until a Zanora operator verifies you. How to ask, what the states mean, and what to do after a denial.

## Sellers — Sell

- [Sell an MCP tool](https://docs.zanora.dev/sellers/mcp.md): @zanora/middleware-mcp: declare a price, get a wrapper for the handler. Publishing, reconciling on restart, pricing a whole server, showing prices in tools/list, and low-level servers.
- [Sell an HTTP endpoint](https://docs.zanora.dev/sellers/rest.md): Publish a REST capability, then add @zanora/middleware-express to the route. Unpaid calls get a 402 with a signed price, and your handler only runs once the call is paid for.
- [Sell without hosting](https://docs.zanora.dev/sellers/packages.md): A stdio MCP server can be sold as a pinned npm package that buyers run locally. There's no port and no uptime to maintain, and payment works exactly as for a hosted server.
- [Pricing and editing listings](https://docs.zanora.dev/sellers/listings.md): Change a live capability's price, wording or schema without changing its id. Also covers what can't change, how to withdraw a capability, and how discovery ranks you.
- [Manage listings from an MCP client](https://docs.zanora.dev/sellers/no-code.md): Run @zanora/mcp in seller mode to publish, edit, request verification, and follow sales and earnings from Claude or any MCP client. It can see money but can't move it.

## Sellers — Get paid

- [Earnings and payouts](https://docs.zanora.dev/sellers/payouts.md): How each sale settles to your wallet, where to see sales, and how to register a payout destination and move money to your bank or a USDC address.
- [Seller troubleshooting](https://docs.zanora.dev/sellers/troubleshooting.md): The problems sellers run into most, what causes each one, and the fix.

## API reference — Using the API

- [API overview](https://docs.zanora.dev/api/overview.md): Base URL, authentication, amount format, errors, rate limits and pagination for every Zanora API route.

## API reference — Endpoints

- [Signup and accounts](https://docs.zanora.dev/api/signup-and-accounts.md): Self-serve signup for buyers and sellers, and the email/password console login. These are the only routes you can call without an API key.
- [Keys and identity](https://docs.zanora.dev/api/keys.md): Check who a key belongs to, and mint, list, rotate and revoke narrower keys.
- [Discovery](https://docs.zanora.dev/api/discovery.md): Search the marketplace for capabilities, ranked by relevance, price, latency, reputation and verification.
- [Capabilities](https://docs.zanora.dev/api/capabilities.md): Publish, list, fetch, edit and deprecate capabilities. Sellers write; anyone with a key can read what discovery would show.
- [Providers](https://docs.zanora.dev/api/providers.md): Seller profiles, verification requests, ratings and payout destinations.
- [Wallets](https://docs.zanora.dev/api/wallets.md): Create and list wallets, read balances and ledgers, fund them, and freeze or unfreeze them.
- [Policies and approvals](https://docs.zanora.dev/api/policies-and-approvals.md): Register, list and switch spending rules on or off, and resolve purchases that a rule held for a person.
- [Receipts](https://docs.zanora.dev/api/receipts.md): List and fetch signed receipts. Buyers see their purchases and sellers see their sales.
- [Payouts and rails](https://docs.zanora.dev/api/payouts.md): Request seller payouts, see which funding and payout rails this deployment offers, and follow money moving in or out.
- [Platform keys and health](https://docs.zanora.dev/api/platform.md): The public keys that sign price challenges and receipts, and the health check. None of these need an API key.

## API reference — Protocol

- [x402 protocol](https://docs.zanora.dev/api/x402.md): The payment handshake step by step, over HTTP and over MCP. For anyone writing a buyer client or seller middleware in a language without a Zanora package.

## API reference — Packages

- [MCP server reference](https://docs.zanora.dev/api/mcp-server.md): Every environment variable, tool and resource in @zanora/mcp, for both the buyer and seller profiles.
- [SDK and middleware reference](https://docs.zanora.dev/api/sdk.md): The public surface of @zanora/sdk, @zanora/middleware-mcp and @zanora/middleware-express, in one place.

## Optional

- [Everything in one file](https://docs.zanora.dev/llms-full.txt): all of the pages above, concatenated