Skip to content
Sentinel AI Sentinel AI

Sentinel Platform

Sentinel Platform is the developer console at /app — the control surface for the sovereign API.

  • API keys — issue scoped, rate-capped virtual keys (sk-mesh-…).
  • Usage & billing — per-key usage, credit balance in PKR, local-rails top-ups, and a per-period statement with wholesale, retail, and margin per model.
  • Playground — try the model against your prompts in-browser.
  • Models & limits — the live catalog, per-key RPM caps, and usage tiers.
  • Docs — Quickstart and API reference.
The Sentinel Platform console The console at slash app has two halves. Developers use API keys, usage and billing, the sandbox, models and limits, and docs. Operators additionally run the routing engine, provider registry, pricing, guardrail defaults, governance and tenant administration, all live rather than by redeploy. FOR DEVELOPERS API keys sk-mesh-… Usage & billing PKR · statements Sandbox try your prompts Models & limits catalog · RPM caps Docs — quickstart and API reference FOR OPERATORS · /app/admin Routing engine policy · timeouts Providers add · key · enable Pricing rate · markup · FX Governance Watch · posture Tenants — markup, credits, quotas, keys Sentinel Mesh — changes take effect on the next request, not the next deploy
Two halves of one console: what a developer uses to build, and what an operator uses to run the gateway. Everything on the operator side takes effect on the next request rather than the next deploy.

Teams and workspaces

A Sentinel account is not a single seat. Every user gets a personal workspace, and can be invited into others — so an operator’s team, a client’s engineers and your own staff can share billing and keys without sharing a login.

RoleWhat it can do
OwnerThe workspace itself. Cannot be demoted or removed.
AdminMembers, keys, billing.
AnalystRead every monitoring surface — usage, logs, operations. Changes nothing.
MemberUse the gateway; see their own activity.
ViewerRead-only.

The workspace you are acting as decides whose credits a request spends, so switching moves usage, keys, billing and logs together. Membership is re-checked on every request: remove someone and their access ends on their next call, not at their next login.

Admin: the engine is dynamic

Operators run the gateway from /app/admin/engine — a live control surface, not a redeploy:

  • Routing — default policy, timeout profile, and whether external providers are in play.
  • Providers — add, key, enable, or disable upstream providers and their models; the router picks up changes on the next request.
  • Pricing — sovereign wholesale rate, default markup, and FX, all feeding the metered PKR price.
  • Defaults & guardrails — the global blocked-terms floor, new-tenant credits and quota, and top-up bounds.
  • Governance — Sentinel Watch audit feed and sovereignty posture.
  • Admin — for resellers: tenants, markup, credits, keys.

The Platform runs on the Sentinel Mesh gateway.

Open the Platform →