Live App →
Developers

For Developers

Build against the Sentinel platform. API reference, authentication, SDKs, and contribution guides.

For Developers

For Developers

Build against the Sentinel platform. API reference, authentication, SDKs, and contribution guides for engineers extending the stack.

Quickstart

First API call in under 10 minutes

→

Authentication

Bearer JWT flow, refresh tokens, server actions

→

API reference

Every Studio BFF route — auth, dashboard, Nexus, Zen, agents

→

SDKs & clients

Available client libraries and patterns for direct HTTP

→

Webhooks

Event subscriptions for pipeline completion and chat events

→

Rate limits

Per-tenant quotas and burst behavior

→

Errors

Status codes, envelope shape, and recovery patterns

→

Frontend architecture

Next.js 16 App Router, Zustand, React Query

→

Design system

Typography, tokens, themes, Tailwind variants

→

Screen catalog

All routes, CTAs, and data dependencies

→

In ten minutes

# 1. Get a token from the Studio BFF
curl -X POST https://studio-backend-dev.centricitywealth.tech/api/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email":"<your-email>","password":"<your-password>"}'

# 2. Use the access_token in subsequent calls
curl https://studio-backend-dev.centricitywealth.tech/api/v1/dashboard \
  -H "Authorization: Bearer <access_token>"

That’s the whole loop. Every other backend (Nexus, Zen, Agentic, KB) is fronted by the same Studio gateway — you never call the capability backends directly. See Quickstart for the full version.

What’s in the API

Surface Purpose
/api/v1/auth/* Login, register, refresh, logout
/api/v1/dashboard Aggregated platform metrics
/api/v1/nexus/* Document intelligence (32 explicit routes)
/api/v2/nexus/pipeline/* Pipeline lifecycle and progress polling
/api/v1/zen/* Chat sessions, messages, RAG uploads
/api/v1/agents/* Agent invocation and model catalog

Full schemas: API reference.

Architecture in one diagram

graph LR
  Client["Your client<br/>(browser, server, SDK)"] --> Studio["Studio BFF<br/>FastAPI · JWT · RBAC"]
  Studio --> Nexus[Nexus<br/>Document AI]
  Studio --> Zen[Zen<br/>RAG chat]
  Studio --> Agents[Agentic<br/>workflows]
  Studio --> KB[Knowledge base]
  Studio --> LLM[LLM orchestrator]
  Studio --> Integrations[Integrations]

Single entry point, central auth, normalised response envelope — the BFF pattern is described in detail in the Platform overview.

Where to go next