Skip to main content
Last generated: 2026-09-21. Use this page to choose the right Otto access path and to see which capabilities are published on each rail. The tables are generated from the storefront catalogs and the ACP schema exports, so counts and rail membership stay tied to code instead of hand-maintained docs.

What this page proves

  • Published membership. A cell in the matrix means the capability is declared in that rail’s catalog or schema export at generation time. It is a statement about the catalog, not a live health probe.
  • Readiness is checked live, not here. Before relying on a route or job, read the live surface: x402 discovery at /.well-known/x402 and the router health at /health; ACP offerings and prices through acp browse --json (see acp-cli); Otto X through its own discovery on the Otto X page. A capability can be published and still be Not available at a given moment; the live surface answers that.
  • Prices are served live. Where this page or an agent page shows a price, it is regenerated from the same catalogs; the amount you actually pay is the one the paywall or ACP discovery serves at purchase time.
The DApp column is a guided app workflow mapping, not an endpoint catalog.

Quick Answer

Published Counts

Counts of published capabilities per rail at generation time (membership, not readiness).

x402 Categories

Matrix

Provenance

  • These tables are generated from Otto’s storefront code, so endpoint counts stay tied to code instead of hand-maintained docs. They describe this source revision; use live discovery to confirm the current catalog.
  • Catalog membership is not a successful paid job or a funded execution test.