Topolo Auth API
Curated reference overlay for the Topolo Auth service where platform semantics matter more than raw route listing.
Important route families
- authentication and session validation
- organization and service registry queries
- service API key scopes
- service API key bindable resources
- API key create, list, revoke, and validation flows
Why this page exists
Topolo Auth exposes platform semantics that are broader than a raw endpoint index. Use this page for behavioral guidance, then use generated reference where a formal spec exists for a downstream service.
Operational contract
- service scope metadata for API keys is served from Auth D1
- resource-binding catalogs for supported services are also served from Auth D1
- clients should not hardcode service scope lists or fetch bindable resources directly from application UIs