1.5 KiB
1.5 KiB
id, title, type, status, timeframe, primary_repo, linked_repos, summary, why_it_matters, risk_if_lost, recommended_action
| id | title | type | status | timeframe | primary_repo | linked_repos | summary | why_it_matters | risk_if_lost | recommended_action | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| blackroad-os-api | BlackRoad OS API | repo | active | 2023- | blackroad-os-api |
|
Unified API surface exposing OS capabilities to web, console, and packs. | Provides consistent, authenticated entry points for every client surface and integration. | Clients would fragment across legacy endpoints and lose a trusted contract for platform access. | keep-live |
BlackRoad OS API – Archive Cover Sheet
Narrative
The API repo defines service contracts, request flows, and orchestration that present BlackRoad capabilities to all clients. It aligns SDKs, policies, and telemetry around a single gateway front door.
History
Born from multiple microservice experiments, the API consolidated endpoints into a single spec, then layered on gateway policies and observability to stabilize external access.
Current Role
It powers the public and partner-facing interfaces for the console, web, and packs, routing through the gateway and operator-managed deployments.
Dependencies
- Deployed through
blackroad-os-operatorand fronted byblackroad-os-api-gateway. - Consumes shared contracts from
blackroad-os-core. - Exposes data used by
blackroad-os-weband Prism Console.
Migration / Future
Continue converging legacy endpoints, adopt schema-first workflows with the archive catalog, and automate policy sync with the gateway repo.