# Agent authentication — Rooster Agents

Three tiers. Most agents never leave tier 1.

## 1. Open (no credentials)
Discovery, business data and booking handoff are **open**. No account, no API key, no OAuth.

- `GET  https://roosteragents.ai/gateway/directory.json`
- `GET  https://roosteragents.ai/gateway/businesses/{id}.json`
- `POST https://roosteragents.ai/mcp`  (JSON-RPC 2.0: `initialize`, `tools/list`, `tools/call`)

Send a descriptive `User-Agent`. Per-IP rate limits apply; we do not store your IP in the clear.

## 2. Pay-per-call (x402, no account)
Paid analysis is metered with **x402** over USDC. Call the endpoint, receive `HTTP 402` with the
payment requirements, replay with the `X-PAYMENT` header. There is nothing to sign up for.

- Discovery document: `https://roosteragents.ai/.well-known/x402`
- Products + prices: `https://rooster-meter.roosteragents.workers.dev/v1/catalog`

Status: settlement currently runs on **Base Sepolia (testnet)** — challenges are real, the USDC is
not. A mainnet caller is refused with an explicit network-mismatch error rather than silently
failing. Mainnet listing will publish a new `payTo` on Base.

## 3. Partner / managed access
Higher volume, private endpoints, or a business that wants its own agent-callable surface built:
email `rudy@roosteragents.ai` or text `+1-717-562-6072`. We issue partner credentials by agreement — there is no
self-serve key, by design.

## What we do NOT support (so you stop looking)
- OAuth 2.0 authorization-code flow — `not_implemented`
- API-key self-signup — `not_implemented` (deliberate: done-for-you model)
- ACP / UCP checkout lifecycle — `discovery_only`, see `/.well-known/acp.json` and `/.well-known/ucp`

We would rather publish an honest "no" than a spec badge we cannot honour.
