§ · changelog

What changed.

Every change to the service that a customer could notice, newest first. Subscribe at /changelog.atom. Last entry: 2026-09-12.

2026-09-12The fee schedule and the terms as pages of their own

  • /pricing renders the fee schedule as a page, and /terms carries the full terms of service; every receipt now links to /terms, and the site map lists both.

2026-09-11Corrected before paying, and refusals explained

  • An unpaid request now gets its 402 together with a preflight: the exact problems the paid retry would be refused for (address shape, body schema, spec problems, tier rules, idempotency key shape), and a hint that says do not pay yet. A buyer is corrected before signing a payment; catalog probers still see their 402.
  • The status page lists why every paid request was refused (status and error code) for the last 7 days.
  • A reused Idempotency-Key explains that a repeat purchase needs a fresh key.

2026-09-07The 402 funnel on the status page

  • A request without a payment now reaches the 402 storefront whatever its body; requests that carry a payment are still validated before settlement, so nothing is ever charged for a request that cannot run.
  • The OpenAPI document now lists each verdict tier as its own operation and carries what catalog probers read: x-payment-info with the price in USD, a required request body with an example a prober can send, response schemas, security markers on free and secret protected routes, and guidance for agents in info.x-guidance. A favicon is served at /favicon.ico.
  • A bare GET on a paid POST route now answers the same 402 storefront as the POST, instead of 404: catalogs probe paid URLs with GET, and humans click them. A paid GET is refused with 405 and never charged.
  • Every request to a paid route is now counted by the stage it reached (402 issued, refused before payment, paid attempt, settled) and shown on /status for the last 7 days, together with the user agents that knock on paid routes. Daily aggregates only; no addresses, no bodies.

2026-09-03Findable by crawlers, answer engines, and agents

  • A changelog at /changelog with an Atom feed at /changelog.atom, so every release is new content a crawler can read.
  • The status page now shows a public ledger: verdicts settled and webhooks delivered in the last 30 days, uptime, and visits by AI crawler family.
  • robots.txt invites AI search and answer engines explicitly and points at a real sitemap; an IndexNow key file lets Bing, Yandex, Naver, and Seznam be told about changes directly.
  • /.well-known/x402.json mirrors the payment manifest under the name catalogs probe, and /.well-known/agent-tools.json describes the service for agent tool directories.
  • A visible questions section on the landing page, and structured data naming every product and price, the witness tier included.

2026-09-03Live on mainnet, listed in the Bazaar

  • Payments settle on Base and Solana through the Coinbase CDP facilitator with PayAI as fallback.
  • The four verdict tiers are listed in the CDP x402 Bazaar after their first settled payments; every paid route advertises its bare path so the reputation read can be listed too.
  • Designed pages for the human-facing links: /manual, /status, and the probe policy at /bot.
  • Browser based x402 clients can pay: the API allows the PAYMENT-SIGNATURE header and exposes the 402 and receipt headers.

2026-09-03Witness tier and a hardened money path

  • POST /v1/verdicts/witness ($0.25): one live URL probe, answered synchronously as a signed verdict that embeds a signed observation of what was seen, aimed at agent false success.
  • Every network check carries an observations array: final URL, redirect hops, HTTP status, resolved address, TLS certificate details, capped headers, raw body sha256.
  • Idempotent replays are served in front of the paywall; unsettled purchases are voided; sworn pass 2 retries three times and then issues FAILED.
  • Every regex and JSON Schema evaluates in a worker thread with a CPU timeout.
  • Reputation reports add an amount weighted fulfillment rate and payer concentration signals; ERC-1271 smart wallet signatures are accepted.

2026-08-28Deployed

  • Container, persistent volume for the database and signing key, always-on scheduler.