Application API
One public boundary for the private platform.
The Next.js backend-for-frontend is the browser-facing API. It carries authenticated identity, normalizes service responses, and keeps private topology out of client code.
Integration expectations
Keep account context intact.
Authenticate through the web application and include the session cookie
Call same-origin /api routes instead of private service addresses
Expect the server to resolve canonical user, profile, and broker scope
Handle unavailable, stale, empty, partial, and successful responses distinctly
Treat POST, PATCH, and DELETE operations as state-changing unless documented otherwise
This page is a route map, not a substitute for the live contract. Inspect the authenticated application response and current server implementation before building an external integration.
Representative routes
Authenticated BFF surface
GET
/api/dashboardNormalized account and desk overviewGET
/api/trading/sseAuthenticated trading event streamGET
/api/automation/telemetryAutomation and pipeline telemetryGET
/api/monitoring/targetsNormalized monitoring target stateGET
/api/models/lane-manifestAvailable lane and model configurationGET
/api/factory/registryInfrastructure and service registryGET
/api/user/brokersBroker configuration status for the active userPOST
/api/chat/[agent]Send an authenticated advisory-agent message