CxAI Trading

Session-aware BFF

Same-origin Next.js routes attach authenticated user and account context before proxying private services.

Streaming interfaces

SSE and WebSocket paths carry market and operational updates without exposing private service addresses.

Persistent data contracts

PostgreSQL, DynamoDB-backed profiles, durable engine state, and caching support user and execution workflows.

Routed model services

Inference and agent requests resolve through configured channels rather than binding the browser to one provider.

Automation and delivery

Airflow, Spark, Jenkins, and service tooling coordinate research, pipelines, deployment, and operational checks.

Per-user context

Broker records are encrypted at rest and resolved server-side for the authenticated profile and requested lane.

Frontend contract

Read authenticated context safely.

This browser-side example reads the normalized dashboard through the BFF. It does not embed a token, private host, broker secret, or state-changing order request.

Authenticated browser request

const response = await fetch("/api/dashboard", {
  credentials: "include",
  headers: { Accept: "application/json" },
});

if (!response.ok) {
  throw new Error(`Dashboard unavailable (${response.status})`);
}

const dashboard = await response.json();
// Preserve dashboard freshness and availability metadata
// instead of converting unknown values to zero.

Stay same-origin

Call the web application’s /api routes from the browser; private hosts remain server-side details.

Preserve identity

Use the authenticated session and let the BFF resolve canonical profile and account scope.

Represent uncertainty

Keep loading, unavailable, stale, empty, and confirmed-zero states distinct in every consumer.

Treat mutations as workflows

Require explicit intent, surface partial failure, and reconcile the external result.

View the API map Architecture →