Every schema ships a REST API with filtering, search, sorting, pagination and relation expansion.
List endpoints accept page, limit, search, sort, field filters with operators, exact filters, response shaping (fields/omit) and relation expansion. The operator set is a deliberate allowlist — no $regex, no raw operators smuggled through keys — so the flexibility never becomes a security hole in a multi-tenant platform.
Every schema has a Docs tab with its actual endpoints, parameters and example responses generated from its own fields — not generic placeholders. Hand it to a frontend developer and they're productive before the coffee cools.