Standard surfaces where standards already exist.
Use OpenAI-compatible inference, MCP for capabilities, OAuth for access, SCIM for provisioning, and webhooks for billing. Sofia-specific concepts appear only where needed.
One gateway for organization capabilities.
Clients discover and run skills, plugins, connected services, and remote tasks through one Sofia endpoint. OAuth scopes and org grants control access.
tools/list search_capabilities execute_capability search_capabilities query: "deploy production service" → railway.deploy → github.create_release → remote_worker.run
Predictable endpoints, explicit ownership.
The public surfaces are intentionally narrow. Identity, policy, pricing, and billing stay authoritative; adapters and workers sit behind stable contracts.
/v1/models, /v1/responses, and /v1/chat/completions use Sofia API keys and OpenAI-compatible request shapes.
/mcp supports API-key access and modern OAuth discovery, PKCE, rotating refresh tokens, and resource-bound scopes.
Managed workers use a lease protocol for durable jobs, heartbeats, renewal, completion, failure, and cancellation.
SCIM v2 users and groups map identity-provider state into memberships and teams.
Try it without a client library.
The API reference includes schemas and an interactive client for trying requests.
curl https://api.sofia.example/v1/responses \
-H "Authorization: Bearer $SOFIA_API_KEY" \
-H "Idempotency-Key: review-42" \
-H "Content-Type: application/json" \
-d '{"model":"sofia/deepseek-v4.1","input":"Review this diff"}'Read the guide, then check the wire format.
Authored guides for the harness, plus an interactive reference for the API.