Reference

Schemas, endpoints, and headers — the part of the docs you'll keep open in another tab. Reference pages stay close to the wire: types, fields, verbs, status codes, examples. For the why behind any of it, follow the links back into Concepts.

API reference

Live OpenAPI explorer for api.airbrx.ai. Authenticate with a PAT and try it.

Rule schema

JSON shape for cache rules and invalidation rules — fields, operators, cache key elements.

Response headers

X-Airbrx-* headers the Gateway adds to every response.

Analytics API

Yearly, daily, and per-user summary endpoints. Build your own dashboards.

Markers API

Create, list, and delete invalidation markers. Pair with rules to bust cache from outside the SQL stream.

What reference pages don't cover

Reference pages are intentionally narrow: shape and verbs, not motivation. For the conceptual model behind any of these, jump back into:

Rules as the differentiator — why cache and invalidation rules are peers.
How the Gateway works — the request lifecycle these headers describe.
Security posture — how the four-axis token scope (referenced from the API page) works in practice.