@agentcash/router 1.6.0 → 1.7.1

package/README.md

@@ -1,185 +1,130 @@
-# @agentcash/router
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://agentcash.dev/logo-dark-striped.svg">
+    <img alt="AgentCash" src="https://agentcash.dev/logo-light-striped.svg" width="360">
+  </picture>
+</p>
 
-Unified route builder for Next.js App Router APIs with x402 payments, MPP payments, SIWX authentication, and API key auth.
+<h1 align="center">@agentcash/router</h1>
 
-Eliminates ~80-150 lines of boilerplate per route. Routes become 3-6 lines.
+<p align="center">
+  <strong>The fastest way to ship an API on x402 and MPP.</strong><br/>
+  x402 and MPP payments, compatible discovery, and minimal boilerplate. With @agentcash/router, agents on <a href="https://agentcash.dev">AgentCash</a> and across the agentic commerce ecosystem are compatible and call your endpoints from day one.
+</p>
 
-## Install
+<p align="center">
+  <a href="https://www.npmjs.com/package/@agentcash/router"><img alt="npm" src="https://img.shields.io/npm/v/@agentcash/router.svg?color=111&label=npm"></a>
+  <a href="https://agentcash.dev/docs"><img alt="docs" src="https://img.shields.io/badge/docs-agentcash.dev-111"></a>
+  <a href="#install"><img alt="next.js" src="https://img.shields.io/badge/Next.js-App%20Router-111"></a>
+</p>
 
-```bash
-pnpm add @agentcash/router
-```
+---
 
-Peer dependencies:
+## Install
 
 ```bash
-pnpm add next zod @x402/core @x402/evm @x402/extensions @coinbase/x402 zod-openapi
-# Optional: for MPP support
-pnpm add mppx
+pnpm add @agentcash/router
+pnpm add next zod @x402/core @x402/evm @x402/extensions @coinbase/x402 zod-openapi # peer dependencies
+pnpm add mppx  # optional, for MPP support
 ```
 
-## Environment Setup
+## Environment
 
-The router uses the default facilitator from `@coinbase/x402` for x402 payments, which requires CDP API keys:
+The recommended entry point reads its config from `process.env`. A copy-paste `.env.example` lives at the repo root.
 
-```bash
-CDP_API_KEY_ID=your-key-id
-CDP_API_KEY_SECRET=your-key-secret
-```
+### x402
 
-**For Next.js apps with env validation** (T3 stack, `@t3-oss/env-nextjs`): Add these to your env schema — Next.js doesn't expose undeclared env vars to `process.env`.
+| Var | Required | Purpose |
+|-----|----------|---------|
+| `EVM_PAYEE_ADDRESS` | yes | EVM address that receives x402 and MPP payments (`0x…`, 20 bytes). Canonicalized to lowercase. The zero address is rejected. |
+| `CDP_API_KEY_ID`, `CDP_API_KEY_SECRET` | yes (production) | Coinbase Developer Platform credentials for the default EVM facilitator. T3 / `@t3-oss/env-nextjs` users must declare these in their env schema. |
 
-```typescript
-// src/env.js
-import { createEnv } from "@t3-oss/env-nextjs";
-import { z } from "zod";
-
-export const env = createEnv({
-  server: {
-    CDP_API_KEY_ID: z.string(),
-    CDP_API_KEY_SECRET: z.string(),
-  },
-  runtimeEnv: {
-    CDP_API_KEY_ID: process.env.CDP_API_KEY_ID,
-    CDP_API_KEY_SECRET: process.env.CDP_API_KEY_SECRET,
-  },
-});
-```
+### Solana
 
-Without these keys, x402 routes that use the default EVM facilitator will fail to initialize.
-`createRouter(config)` always validates the base URL and protocol list, throws protocol config
-errors in production, and keeps protocol-specific init errors as request-time JSON 500s in
-development. Call `validateRouterConfig(config)` before `createRouter(config)` when you want
-missing facilitator, MPP, or store configuration to throw immediately in every environment.
+| Var | Required | Purpose |
+|-----|----------|---------|
+| `SOLANA_PAYEE_ADDRESS` | no | When set, adds a Solana `exact` accept so the router takes Solana payments. **Dynamic pricing (`upto`) is Base-only** — Solana clients can only pay static-priced routes. |
+| `SOLANA_FACILITATOR_URL` | no | Override the Solana x402 facilitator. Defaults to `DEFAULT_SOLANA_FACILITATOR_URL`. |
 
-### Recommended strict setup
+### MPP (auto-enabled when `MPP_SECRET_KEY` is set)
 
-```typescript
-import {
-  createRouter,
-  mppFromEnv,
-  validateRouterConfig,
-  x402AcceptsFromEnv,
-  type ProtocolType,
-} from '@agentcash/router';
-
-const payeeAddress = process.env.X402_WALLET_ADDRESS ?? process.env.X402_PAYEE_ADDRESS;
-const accepts = x402AcceptsFromEnv(process.env, { payeeAddress });
-const protocols: ProtocolType[] = process.env.MPP_SECRET_KEY ? ['x402', 'mpp'] : ['x402'];
-
-const config = {
-  payeeAddress: payeeAddress!,
-  baseUrl: process.env.NEXT_PUBLIC_BASE_URL!,
-  strictRoutes: true,
-  protocols,
-  x402: { accepts },
-  mpp: mppFromEnv(process.env, {
-    recipient: payeeAddress,
-  }),
-  discovery: {
-    title: 'My API',
-    version: '1.0.0',
-  },
-};
+| Var | Required | Purpose |
+|-----|----------|---------|
+| `MPP_SECRET_KEY` | when MPP is enabled | Server-side MPP secret. Presence toggles MPP on. |
+| `MPP_CURRENCY` | when MPP is enabled | Tempo currency address. Use `TEMPO_USDC_ADDRESS` for Tempo USDC. |
+| `TEMPO_RPC_URL` | when MPP is enabled | Authenticated Tempo JSON-RPC endpoint. Public `rpc.tempo.xyz` returns 401. |
+| `MPP_OPERATOR_KEY` | no | Signs server-side close/settle. When set, MPP session mode is enabled automatically (required for streaming + `.paid({ dynamic: true })` on MPP). Address must equal the payee. |
+| `MPP_FEE_PAYER_KEY` | no | Sponsors client gas for channel open/topUp. Must resolve to a different address than `MPP_OPERATOR_KEY` (Tempo rejects fee-delegated txs where `sender === feePayer`). |
 
-validateRouterConfig(config);
-export const router = createRouter(config);
-```
+### Other
 
-`x402AcceptsFromEnv()` always adds Base (`BASE_NETWORK`) and also adds Solana
-mainnet (`SOLANA_MAINNET_NETWORK`) when `SOLANA_PAYEE_ADDRESS` is set. Solana
-addresses are case-sensitive and are preserved as-is. It reads
-`X402_WALLET_ADDRESS` by default; older services that still use
-`X402_PAYEE_ADDRESS` can pass `{ payeeEnv: 'X402_PAYEE_ADDRESS' }`.
+| Var | Required | Purpose |
+|-----|----------|---------|
+| `BASE_URL` | yes | Origin URL (`https://api.example.com`). Load-bearing — used as the 402 realm, OpenAPI server URL, and MPP memo prefix. Must match the public domain. |
+| `KV_REST_API_URL`, `KV_REST_API_TOKEN` | no | Upstash / Vercel KV. Backs SIWX nonce, SIWX entitlement, and MPP replay. In-memory fallback is unsafe in serverless production. Providing a Kv Store is highly recommended. |
 
-`mppFromEnv()` returns `undefined` when no MPP env vars are present. If any MPP
-env var is present, the full trio is required: `MPP_SECRET_KEY`, `MPP_CURRENCY`,
-and `TEMPO_RPC_URL`. `MPP_CURRENCY` must be the Tempo currency address; for
-Tempo USDC use `TEMPO_USDC_CURRENCY`. Optional `MPP_FEE_PAYER_KEY` is included
-when present and validated as a 32-byte EVM private key. `mppFromEnv()` only
-builds config; call `validateRouterConfig(config)` before `createRouter(config)`
-to fail fast on misconfiguration.
+## Quick start
 
-### Persistent KV store
+### 1. Create the router
 
-The router uses a single KV cache for three things: SIWX nonce replay
-protection, SIWX entitlement records, and MPP tx-hash replay protection. Each
-consumer gets its own key prefix (`siwx:nonce:`, `siwx:ent:`, `mpp:`) so one
-Redis/Upstash instance serves all three.
+There are two ways to initialize. Pick one.
 
-`createRouter` reads `KV_REST_API_URL` + `KV_REST_API_TOKEN` from `process.env`
-automatically (Vercel KV and Upstash both set these). If both are present, it
-builds an Upstash-compatible REST client and wires it into every store. If
-either is missing, all three stores fall back to in-memory — fine for local
-dev, unsafe in serverless production.
-
-To use REST credentials under a different env name, pass them as
-`{ url, token }`:
+**Option A — `createRouterFromEnv` (recommended).** Reads `process.env`, validates every value up front, and throws a single `RouterConfigError` with every problem at once. Auto-enables MPP when `MPP_SECRET_KEY` is set, auto-adds a Solana accept when `SOLANA_PAYEE_ADDRESS` is set, auto-enables MPP session mode when `MPP_OPERATOR_KEY` is set.
 
 ```typescript
-import { createRouter } from '@agentcash/router';
+// lib/router.ts
+import { createRouterFromEnv } from '@agentcash/router';
 
-createRouter({
-  kvStore: {
-    url: process.env.UPSTASH_REDIS_REST_URL!,
-    token: process.env.UPSTASH_REDIS_REST_TOKEN!,
-  },
-  // ...
+export const router = createRouterFromEnv({
+  title: 'My API',
+  description: 'Pay-per-call search.',
+  guidance: 'POST /search with { q: string }. Returns top 10 results.',
 });
 ```
 
-For a different backend entirely (Cloudflare KV, ioredis, etc.), implement the
-`KvStore` interface and pass your instance as `kvStore`.
-
-## Quick Start
-
-### 1. Create the router (once per service)
+**Option B — build a `RouterConfig` and pass it to `createRouter`.** Use this when you need custom networks, multiple payees, non-standard assets, or any setting `createRouterFromEnv` doesn't expose. `createRouter` runs the same validation against the `RouterConfig` shape.
 
 ```typescript
-// lib/routes.ts
-import { createRouter } from '@agentcash/router';
+// lib/router.ts
+import { createRouter, BASE_MAINNET_NETWORK } from '@agentcash/router';
 
 export const router = createRouter({
-  payeeAddress: process.env.X402_WALLET_ADDRESS!,
-  baseUrl: process.env.NEXT_PUBLIC_BASE_URL!,
-  strictRoutes: true, // recommended
+  baseUrl: 'https://api.example.com',
+  payeeAddress: '0x…',
+  network: BASE_MAINNET_NETWORK,
+  protocols: ['x402'],
+  x402: { accepts: [/* … */] },
   discovery: {
     title: 'My API',
     version: '1.0.0',
-    description: 'Pay-per-call API',
+    description: 'Pay-per-call search.',
+    guidance: 'POST /search with { q: string }. Returns top 10 results.',
   },
 });
 ```
 
 ### 2. Define routes
 
-**Paid route (x402)**
-
 ```typescript
 // app/api/search/route.ts
-import { router } from '@/lib/routes';
-import { searchSchema, searchResponseSchema } from '@/lib/schemas';
+import { router } from '@/lib/router';
+import { searchSchema } from '@/lib/schemas';
 
 export const POST = router.route({ path: 'search' })
   .paid('0.01')
   .body(searchSchema)
-  .output(searchResponseSchema)
-  .description('Search the web')
   .handler(async ({ body }) => search(body));
 ```
 
-**SIWX-authenticated route**
-
 ```typescript
+// app/api/inbox/status/route.ts
 export const GET = router.route({ path: 'inbox/status' })
   .siwx()
-  .query(statusQuerySchema)
-  .handler(async ({ query, wallet }) => getStatus(query, wallet));
+  .handler(async ({ wallet }) => getStatus(wallet));
 ```
 
-**Unprotected route**
-
 ```typescript
+// app/api/health/route.ts
 export const GET = router.route({ path: 'health' })
   .unprotected()
   .handler(async () => ({ status: 'ok' }));
@@ -187,479 +132,117 @@ export const GET = router.route({ path: 'health' })
 
 ### 3. Auto-discovery
 
-Discovery metadata (`title`, `version`, `description`, `guidance`) is configured once in `createRouter({ discovery })`. The discovery handlers are zero-arg:
-
 ```typescript
-// app/.well-known/x402/route.ts
-import { router } from '@/lib/routes';
-import '@/lib/routes/barrel'; // ensures all routes are imported
-export const GET = router.wellKnown();
-
 // app/openapi.json/route.ts
-import { router } from '@/lib/routes';
-import '@/lib/routes/barrel';
+import { router } from '@/lib/router';
+import '@/lib/routes-barrel';  // imports every route module so the registry is populated
 export const GET = router.openapi();
-
-// app/llms.txt/route.ts
-import { router } from '@/lib/routes';
-export const GET = router.llmsTxt();
 ```
 
-OpenAPI output follows the discovery contract:
+The barrel forces every route module to load before the discovery handler walks the registry — Next.js otherwise lazy-loads route files on first hit, and unloaded routes don't appear in the spec.
 
-- Paid signaling via `responses.402` + `x-payment-info`
-- Auth signaling via `security` + `components.securitySchemes`
-- Optional top-level metadata via `x-discovery` (`ownershipProofs`)
+## Auth modes
 
-## API
-
-### `createRouter(config)`
-
-Creates a `ServiceRouter` instance.
-
-| Option | Type | Default | Description |
-|--------|------|---------|-------------|
-| `payeeAddress` | `string` | — | Wallet address to receive payments |
-| `baseUrl` | `string` | **required** | Service origin used for discovery/OpenAPI/realm |
-| `discovery` | `DiscoveryConfig` | **required** | Title, version, description, guidance for OpenAPI/well-known/llms.txt |
-| `network` | `string` | `'eip155:8453'` | Blockchain network |
-| `plugin` | `RouterPlugin` | `undefined` | Observability plugin |
-| `prices` | `Record<string, string>` | `undefined` | Central pricing map (auto-applied) |
-| `kvStore` | `KvStore \| { url, token }` | auto from `KV_REST_API_URL` + `KV_REST_API_TOKEN`, else memory | Single KV cache for SIWX nonce, SIWX entitlement, and MPP tx-hash replay |
-| `mpp` | `{ secretKey, currency, recipient?, rpcUrl?, feePayerKey?, session? }` | `undefined` | MPP config |
-| `protocols` | `('x402' \| 'mpp')[]` | `['x402']` | Default protocols for paid routes |
-| `strictRoutes` | `boolean` | `false` | Enforce `route({ path })` and prevent key/path divergence |
-
-### Config validation helpers
+| Method | Purpose |
+|--------|---------|
+| `.paid(price)` | Payment required (x402, MPP, or both). |
+| `.siwx()` | Wallet identity, no payment. Returns 402 with a SIWX challenge. |
+| `.apiKey(resolver)` | `X-API-Key` or `Authorization: Bearer <key>`. Composes with `.paid()`. |
+| `.unprotected()` | No auth. |
 
 ```typescript
-import {
-  BASE_NETWORK,
-  SOLANA_MAINNET_NETWORK,
-  TEMPO_USDC_CURRENCY,
-  getRouterConfigIssues,
-  mppFromEnv,
-  paidOptionsForProtocols,
-  validateRouterConfig,
-  x402AcceptsFromEnv,
-} from '@agentcash/router';
-```
-
-- `validateRouterConfig(config)` throws `RouterConfigError` with structured
-  issues. Use it when you want invalid env/config to fail at startup in every
-  environment; `createRouter(config)` still performs its own validation and
-  keeps deferred protocol init errors in development for request-time feedback.
-- `getRouterConfigIssues(config)` returns the same structured issues without
-  throwing.
-- `x402AcceptsFromEnv(env)` builds Base and optional Solana x402 accepts from
-  `X402_WALLET_ADDRESS` and `SOLANA_PAYEE_ADDRESS`.
-- `mppFromEnv(env)` builds MPP config only when MPP env is present, and rejects
-  partial MPP env.
-- `paidOptionsForProtocols(protocols)` copies a protocol array into a
-  route-level `PaidOptions` object.
-- Manual `.paid(price)` routes inherit `createRouter({ protocols })` unless
-  the route passes its own `options.protocols`.
-
-### Path-First Routing
-
-Use path-first route definitions to keep runtime, OpenAPI, and discovery aligned:
-
-```typescript
-router.route({ path: 'flightaware/airports/id/flights/arrivals', method: 'GET' })
-```
+router.route({ path: 'admin/users' })
+  .apiKey(async (key) => db.admin.findByKey(key))  // null => 401
+  .handler(async ({ account }) => db.user.findMany());
 
-If you need a custom internal key (legacy pricing map), you can pass:
-
-```typescript
-router.route({ path: 'public/path', key: 'legacy/key' })
+router.route({ path: 'gated' })
+  .apiKey(resolver).paid('0.01')  // key AND payment
+  .handler(fn);
 ```
 
-In `strictRoutes` mode, custom keys are rejected to prevent discovery drift.
-
-### Route Builder
-
-The fluent builder ensures compile-time safety:
+## Pricing
 
-- `.paid(price)` / `.paid(fn, { maxPrice })` / `.paid({ field, tiers })` - Payment auth
-- `.siwx()` - SIWX wallet auth
-- `.apiKey(resolver)` - API key auth (composable with `.paid()`)
-- `.unprotected()` - No auth
-- `.body(zodSchema, example?)` - Request body validation with optional discovery example
-- `.query(zodSchema, example?)` - Query parameter validation with optional discovery example
-- `.output(zodSchema, example?)` - Response schema with optional discovery example
-- `.inputExample(sample)` / `.outputExample(sample)` - Optional examples when a separate call reads better
-- `.description(text)` - Route description (for OpenAPI)
-- `.provider(name, config?)` - Provider monitoring (see [Provider Monitoring](#provider-monitoring))
-- `.settlement({ beforeSettle, afterSettle, onSettledHandlerError, onSettlementError })` - Payment lifecycle hooks
-- `.handler(fn)` - Terminal method, returns Next.js handler
-
-### Pricing Modes
-
-**Static** - Fixed price for all requests:
+**Static.**
 ```typescript
-router.route('search').paid('0.02')
+.paid('0.02')
 ```
 
-**Dynamic** - Calculate price based on request body:
+**Args-driven.**
 ```typescript
-router.route('gen')
-  .paid((body) => calculateCost(body.imageSize, body.quality))
-  .body(imageGenSchema)
-  .handler(async ({ body }) => generate(body));
+.paid((body) => calculateCost(body), { maxPrice: '5.00' })
+.body(genSchema)
 ```
 
-**Dynamic with safety net** - Cap at maxPrice if calculation exceeds, fallback to maxPrice on errors:
-```typescript
-router.route('compute')
-  .paid((body) => calculateExpensiveOperation(body), { maxPrice: '10.00' })
-  .body(computeSchema)
-  .handler(async ({ body }) => compute(body));
-```
+`maxPrice` caps the computed amount and acts as a fallback if the pricing function throws. Without `maxPrice`, the route trusts your function fully (no cap, no fallback) and returns 500 on errors.
 
-**Tiered** - Price based on a specific field value:
+**Tiered.**
 ```typescript
-router.route('upload').paid({
+.paid({
   field: 'tier',
   tiers: {
     '10mb': { price: '0.02', label: '10 MB' },
     '100mb': { price: '0.20', label: '100 MB' },
   },
-}).body(uploadSchema)
+})
+.body(uploadSchema)
 ```
 
-#### maxPrice Semantics (v0.3.1+)
-
-`maxPrice` is **optional** for dynamic pricing and acts as a safety net:
-
-1. **Capping**: If `calculateCost(body)` returns `"15.00"` but `maxPrice: "10.00"`, the client is charged `$10.00` (capped) and a warning alert fires.
-
-2. **Fallback**: If `calculateCost(body)` throws an error and `maxPrice` is set, the route falls back to `maxPrice` (degraded mode) and an alert fires. Without `maxPrice`, the route returns 500.
-
-3. **Trust mode**: No `maxPrice` means full trust in your pricing function (no cap, no fallback).
-
-**Best practices:**
-- ✅ Always set `maxPrice` for production routes (safety net)
-- ✅ Use `maxPrice` for routes with external dependencies (pricing APIs)
-- ✅ Monitor alerts for capping events (indicates pricing bug)
-- ⚠️ Skip `maxPrice` only for well-tested, unbounded pricing (e.g., per-GB storage)
-
-**Example with safety net:**
-```typescript
-router.route('ai-gen')
-  .paid(async (body) => {
-    // External pricing API (can fail)
-    const res = await fetch('https://pricing.example.com/calculate', {
-      method: 'POST',
-      body: JSON.stringify(body),
-    });
-    return res.json().price;
-  }, { maxPrice: '5.00' })  // Fallback if API is down
-  .body(genSchema)
-  .handler(async ({ body }) => generate(body));
-```
-
-### Dual Protocol (x402 + MPP)
-
+**Handler-driven (request-mode).** Bills exactly `tickCost` per request:
 ```typescript
-router.route('search')
-  .paid('0.01', { protocols: ['x402', 'mpp'] })
-  .body(schema)
-  .handler(fn);
+.paid({ dynamic: true, tickCost: '0.01', unitType: 'request', maxPrice: '0.01' })
+.handler(async ({ body }) => { ... });
 ```
 
-### Handler Context
-
+**Streaming (MPP only).** One `charge()` call bills one tick:
 ```typescript
-interface HandlerContext<TBody, TQuery> {
-  body: TBody;              // Parsed + validated
-  query: TQuery;            // Parsed + validated
-  request: NextRequest;     // Raw request
-  wallet: string | null;    // Verified wallet address
-  payment: HandlerPaymentContext | null; // Payment metadata for this request
-  account: unknown;         // From .apiKey() resolver
-  alert: AlertFn;           // Fire observability alerts
-  setVerifiedWallet: (addr: string) => void;
-}
+.paid({ dynamic: true, tickCost: '0.0001', unitType: 'token', maxPrice: '0.05', protocols: ['mpp'] })
+.stream(async function* ({ body, charge }) {
+  for await (const token of streamLLM(body.prompt)) {
+    await charge();
+    yield token;
+  }
+});
 ```
 
-`payment` is `null` for unprotected, API-key-only, and SIWX-only requests. For
-paid requests it includes `protocol`, `status`, `payer`, `amount`, `network`,
-and best-effort recipient/transaction/receipt metadata when the protocol
-provides it. x402 handlers currently see `status: 'verified'` because settlement
-happens after a successful handler response.
-
-### Settlement Lifecycle
+## Pre-payment validation
 
-For paid routes, use `.settlement()` when final checks belong after handler work
-but before router-controlled settlement:
+For checks that need a DB lookup before quoting a price:
 
 ```typescript
-router.route('render')
-  .paid('0.10')
-  .body(schema, { prompt: 'city at dusk' })
-  .settlement({
-    beforeSettle: async ({ result }) => {
-      if (!isUsableResult(result)) {
-        throw Object.assign(new Error('Render failed validation'), { status: 502 });
-      }
-    },
-    afterSettle: async ({ payment, result }) => {
-      await ledger.record({ tx: payment.transaction, result });
-    },
-    onSettledHandlerError: async ({ payment, error }) => {
-      await compensationQueue.enqueue({ receipt: payment.receipt, error });
-    },
+router.route({ path: 'domain/register' })
+  .paid(calculatePrice, { maxPrice: '10.00' })
+  .body(RegisterSchema)
+  .validate(async (body) => {
+    if (await isDomainTaken(body.domain)) {
+      throw Object.assign(new Error('Domain taken'), { status: 409 });
+    }
   })
-  .handler(async ({ body }) => render(body));
+  .handler(async ({ body, wallet }) => registerDomain(body.domain, wallet));
 ```
 
-`beforeSettle` can still prevent the charge for x402 and MPP
-transaction-payload flows. `afterSettle` is for durable ledgers, analytics, and
-post-settlement bookkeeping. `onSettledHandlerError` covers already-settled
-MPP requests whose handler returns an error response, which is the right place
-to enqueue app-owned refund or compensation work. The router cannot generically
-refund protocol payments because it does not hold merchant signing keys.
-
-### RouterPlugin
+Pipeline order: `body parse -> validate -> 402 challenge -> payment -> handler`.
 
-Pluggable observability. All hooks are optional and fire-and-forget.
+## Plugin Hooks
 
 ```typescript
-import { createRouter, type RouterPlugin } from '@agentcash/router';
+import { createRouterFromEnv, type RouterPlugin } from '@agentcash/router';
 
 const myPlugin: RouterPlugin = {
-  onRequest(meta) { /* ... */ },
-  onPaymentVerified(ctx, payment) { /* ... */ },
-  onPaymentSettled(ctx, settlement) { /* ... */ },
-  onResponse(ctx, response) { /* ... */ },
-  onError(ctx, error) { /* ... */ },
-  onAlert(ctx, alert) { /* ... */ },
-  onProviderQuota(ctx, event) { /* ... */ },
+  onRequest(meta) {},
+  onPaymentVerified(ctx, payment) {},
+  onPaymentSettled(ctx, settlement) {},
+  onResponse(ctx, response) {},
+  onError(ctx, error) {},
+  onAlert(ctx, alert) {},
 };
 
-export const router = createRouter({
-  payeeAddress: process.env.X402_WALLET_ADDRESS!,
-  baseUrl: process.env.NEXT_PUBLIC_BASE_URL!,
+export const router = createRouterFromEnv({
+  title: 'My API',
+  description: '…',
+  guidance: '…',
   plugin: myPlugin,
-  discovery: {
-    title: 'My API',
-    version: '1.0.0',
-  },
-});
-```
-
-Built-in `consolePlugin()` logs lifecycle events:
-
-```typescript
-import { createRouter, consolePlugin } from '@agentcash/router';
-
-export const router = createRouter({
-  payeeAddress: process.env.X402_WALLET_ADDRESS!,
-  baseUrl: process.env.NEXT_PUBLIC_BASE_URL!,
-  plugin: consolePlugin(),
-  discovery: {
-    title: 'My API',
-    version: '1.0.0',
-  },
-});
-```
-
-### Central Pricing Map
-
-For services with many static-priced routes:
-
-```typescript
-const router = createRouter({
-  payeeAddress: process.env.X402_WALLET_ADDRESS!,
-  baseUrl: process.env.NEXT_PUBLIC_BASE_URL!,
-  discovery: {
-    title: 'My API',
-    version: '1.0.0',
-  },
-  prices: {
-    'search': '0.02',
-    'lookup': '0.05',
-  },
 });
-
-// Price auto-applied, no .paid() needed
-export const POST = router.route('search')
-  .body(schema)
-  .handler(fn);
 ```
 
-### Provider Monitoring
-
-Routes that wrap third-party APIs can declare monitoring behavior per-provider. This surfaces quota/balance information through the plugin system and registers cron-checkable monitors.
-
-#### Why
-
-Upstream providers report remaining quota in different ways:
-
-| Pattern | Example | How detected |
-|---------|---------|-------------|
-| Balance in response headers | `X-RateLimit-Remaining: 482` | `extractQuota` reads headers |
-| Balance in response body | `{ rateLimit: { remaining: 50 } }` | `extractQuota` reads result |
-| Separate health-check endpoint | Apollo `/credits` endpoint | `monitor` function (cron) |
-| Overages auto-charged at same rate | Exa, Firecrawl | `overage: 'same-rate'` |
-| Overages at increased rate | Some SaaS APIs | `overage: 'increased-rate'` |
-| No overages, immediate stoppage | Whitepages | `overage: 'hard-stop'` |
-
-The `.provider()` method handles all six patterns through a single interface.
-
-#### Basic usage
-
-```typescript
-export const POST = router.route('search')
-  .paid('0.01')
-  .provider('exa', {
-    extractQuota: (result, headers) => ({
-      remaining: (result as any).rateLimit?.remaining ?? null,
-      limit: (result as any).rateLimit?.limit ?? null,
-    }),
-    warn: 100,
-    critical: 10,
-  })
-  .body(searchSchema)
-  .handler(async ({ body }) => exaClient.search(body));
-```
-
-After every successful handler response, `extractQuota` runs with the raw handler result and the response headers. The router computes a level (`healthy`, `warn`, `critical`) based on thresholds and fires `onProviderQuota` on the plugin.
-
-#### ProviderConfig
-
-| Field | Type | Default | Description |
-|-------|------|---------|-------------|
-| `extractQuota` | `(result, headers) => QuotaInfo \| null` | — | Inline quota extraction after each request |
-| `monitor` | `() => Promise<QuotaInfo \| null>` | — | Standalone health check (for cron) |
-| `overage` | `'same-rate' \| 'increased-rate' \| 'hard-stop'` | `'same-rate'` | What happens when quota hits zero |
-| `warn` | `number` | — | Fire `warn` level when remaining <= this |
-| `critical` | `number` | — | Fire `critical` level when remaining <= this |
-
-#### QuotaInfo
-
-```typescript
-interface QuotaInfo {
-  remaining: number | null;  // Credits/calls remaining
-  limit: number | null;      // Total quota (null if unknown)
-  spend?: number;             // Credits consumed this request
-}
-```
-
-#### Threshold logic
-
-| Condition | Level |
-|-----------|-------|
-| `remaining === null` | `healthy` (no data to compare) |
-| `remaining <= critical` | `critical` |
-| `remaining <= warn` | `warn` |
-| Otherwise | `healthy` |
-
-#### Plugin hook
-
-```typescript
-interface ProviderQuotaEvent {
-  provider: string;       // Provider name from .provider()
-  route: string;          // Route key
-  remaining: number | null;
-  limit: number | null;
-  spend?: number;
-  level: 'healthy' | 'warn' | 'critical';
-  overage: 'same-rate' | 'increased-rate' | 'hard-stop';
-  message: string;        // Human-readable summary
-}
-```
-
-Handle in your plugin:
-
-```typescript
-const myPlugin: RouterPlugin = {
-  onProviderQuota(ctx, event) {
-    if (event.level === 'critical') {
-      discord.alert(`${event.provider}: ${event.remaining} remaining`);
-    }
-    clickhouse.insert('provider_quota', event);
-  },
-};
-```
-
-#### Cron monitors
-
-For providers that require a separate API call to check balance (not available inline in response), register a `monitor` function:
-
-```typescript
-export const POST = router.route('people/search')
-  .paid('0.05')
-  .provider('apollo', {
-    monitor: async () => {
-      const res = await fetch('https://api.apollo.io/v1/credits', {
-        headers: { 'X-Api-Key': process.env.APOLLO_KEY! },
-      });
-      const data = await res.json();
-      return { remaining: data.credits, limit: null };
-    },
-    overage: 'hard-stop',
-    warn: 500,
-    critical: 50,
-  })
-  .body(searchSchema)
-  .handler(fn);
-```
-
-Retrieve all registered monitors via `router.monitors()`:
-
-```typescript
-// cron.ts — run every 5 minutes
-import { router } from '@/lib/routes';
-import '@/lib/routes/barrel';
-
-for (const entry of router.monitors()) {
-  const quota = await entry.monitor();
-  if (!quota) continue;
-
-  const level = quota.remaining !== null && quota.remaining <= (entry.critical ?? 0)
-    ? 'critical'
-    : quota.remaining !== null && quota.remaining <= (entry.warn ?? 0)
-      ? 'warn'
-      : 'healthy';
-
-  if (level !== 'healthy') {
-    alert(`${entry.provider} (${entry.route}): ${quota.remaining} remaining [${level}]`);
-  }
-}
-```
-
-`monitors()` returns:
-
-```typescript
-interface MonitorEntry {
-  provider: string;
-  route: string;
-  monitor: () => Promise<QuotaInfo | null>;
-  overage: OveragePolicy;
-  warn?: number;
-  critical?: number;
-}
-```
-
-#### Provider name only
-
-If you just want to tag a route with its provider for logging/tracing, pass only the name:
-
-```typescript
-router.route('health')
-  .unprotected()
-  .provider('internal')
-  .handler(async () => ({ status: 'ok' }));
-```
-
-#### Safety guarantees
-
-- `extractQuota` runs fire-and-forget — exceptions are caught and swallowed
-- `extractQuota` only runs when `response.status < 400` (no quota extraction on errors)
-- The plugin hook is non-blocking — it never delays the response to the caller
-- Missing thresholds are fine — without `warn`/`critical`, level is always `healthy`
-
-## License
+All hooks are optional and fire-and-forget; they never delay the response. Use hooks to add additional telemetry or flexibility to your resource's lifecycle.
 
-MIT