API Reference
This is a generated discovery surface built from the route definitions in each owning service's source code. It is not the API contract itself: the authoritative contract stays in each owning repository (and in API conventions, which this catalog complements rather than replaces).
Source-derived is not deployed. Every route below was found in service source code. That does not mean it is deployed, reachable from outside the platform, publicly supported, or that its declared authentication is enforced in any particular deployment.
Scope of this first slice
8 services: api-gateway, auth, billing, model-registry, rag, tes, toolserver, workflow-bundles. Other services are not covered yet, and their absence here says nothing about whether they expose APIs.
Across these services 251 routes were found in source. Only the 110 routes classified PUBLIC or AUTHENTICATED_PUBLIC by the maintainer-reviewed visibility manifest are itemised in the endpoint catalog. Every other route (administrative, operator, internal-service, infrastructure, or not yet reviewed) is counted but deliberately not listed.
| Service | Routes found in source | Routes itemised |
|---|---|---|
| api-gateway | 16 | 6 |
| auth | 143 | 48 |
| billing | 19 | 14 |
| model-registry | 24 | 21 |
| rag | 13 | 7 |
| tes | 18 | 7 |
| toolserver | 8 | 0 |
| workflow-bundles | 10 | 7 |
How to read it
- Authentication and conventions explains the auth-evidence and path fields, and why a missing auth dependency is reported as UNKNOWN, never "unauthenticated".
- Services gives a per-service summary with source revision and route counts.
- Endpoint catalog lists the published routes by service.
Machine-readable data
The full structured catalog is published as JSON at
/generated/api-catalog.json. Generated as of source revisions listed on the
Services page.