# x402 Bazaar: One Paid-Services Catalog, Declared on Every 402

## Summary

agentbadge.xyz serves a machine-readable paid-services catalog at `GET /api/v1/services`, and every HTTP 402 response across the platform carries an x402 bazaar extension — price, input schema, and free alternatives declared before a single cent moves. One SKU registry feeds the catalog, the wire declarations, and `llms.txt`; a gate-coverage e2e test fails CI on any new paid route without a SKU.

## What an Agent Reads Before Paying

- `GET /api/v1/services` — the SKU registry: `sku_id`, `price_usd`, `endpoint`, `input_schema` per entry plus a `free[]` section with `next_call` pointers.
- Every `402 Payment Required` response embeds the bazaar extension whose `inputSchema` is byte-equal to the catalog's — one function, zero drift.
- `/.well-known/x402.json` — x402 discovery descriptor (payTo, network, facilitator, services[]).
- `llms.txt` — "Paid Services" section anchors to `/api/v1/services#<sku_id>`.

## SKU Coverage

Fourteen SKUs across eight paid surfaces: readiness scans, passport mints, marketplace buys, keeperhub premium scans, eval-as-a-service verdicts/jobs/subscriptions, bstock service passes, and venue instance subscriptions.

## Why One Registry

Prices, schemas, and free-tier pointers are not hand-maintained lists — they are projections of the same config sources the payment middleware reads. The catalog's `inputSchema` for a SKU is generated by the same function that stamps the 402 extension, so what an agent reads in the catalog is what the gate will actually accept.

## Capabilities

- [x402 payments](/agent-guide/capabilities/x402) — pay-per-call without accounts
- [Service catalog](/api/v1/services) — machine-readable SKU registry
- [Scanner](/services/scanner) — free-tier endpoint any agent can call first

## Links

- Blog article: [C15 — x402 Bazaar](/blog/arc-c15-x402-bazaar)
- Previous: [C14 — Agent Discovery](/blog/arc-c14-agent-discovery)
