Machine-readable price list for every metered endpoint and MCP tool

Public, zero-auth price discovery — call this FIRST, before any paid call, to learn what every metered endpoint and MCP tool costs. Derived from the SAME pricing configuration the 402 INSUFFICIENT_CREDITS meter enforces, so there is deliberately no second price table anywhere in the system; a previously fetched price can still become stale after a pricing change, and the per-call metered response remains the authoritative charging signal. Returns each metered endpoint's canonical path, HTTP method, pricing category and cost in whole øre (100 øre = NOK 1), the matching MCP tool name where one exists, the credit-unit convention, whether enforcement is currently live (while dark, metered calls are not charged and responses carry X-Credit-Check: shadow), the exact machine-readable recovery contract a 402 carries (top_up_url / balance_ore / cost_ore plus the catalog-derived retryable / fix_hint / docs_url), the balance-visibility surfaces (X-Credits-* response headers on REST, metadata.credits on MCP, and the authenticated /account/credits/balance self-read), the low-balance warning rule, and the top-up bounds with the billing-dashboard top_up_url. Prices ONLY — never balances, customer data, or any authenticated state; the endpoint is keyless by design so an agent can price a workflow before holding a key. Served fresh on every request: Cache-Control no-store (the body embeds the runtime enforcement.live mode, which must never be served stale from a shared cache) with a strong SHA-256 ETag honouring If-None-Match (304) — revalidation is answered at origin over the current body, so a 304 can never confirm a stale enforcement mode. The per-call metered response (X-Credit-Check / X-Credits-* headers, or a 402 body) is the authoritative charging signal; enforcement.authority_note states this in-band.