API Reference
Integrate with Clevername programmatically through the OpenAI-compatible governance gateway, the MCP Gateway, legacy Guard API utility endpoints (agent health, FP disputes, tuning), and webhooks. Authenticate with browser Supabase JWTs, MCP OAuth, the Hub Core API key, or per-agent gateway tokens (cn-live-*).
Key Concepts
API architecture
Clevername's API is built around the OpenAI-compatible governance gateway for AI traffic and the MCP Gateway for tool execution. Both are accessible through the Vercel proxy at /api/hub/, which forwards requests to the private Hub Core backend on GCP Cloud Run.
Authentication methods
- Supabase JWT — for browser-based and user-context requests
- MCP OAuth — for IDEs and MCP clients that support browser login
- Hub Core API Key — for server-to-server communication
- Gateway Tokens (cn-live-*) — scoped, time-limited tokens for programmatic access (legacy
cnk_*tokens are still accepted)
Base URL
All API requests go throughhttps://clevername.net/api/hub/. Never call the Cloud Run backend directly — it is private and requires GCP identity tokens.
API architecture diagram showing browser and server clients connecting through the Vercel proxy to Hub Core
Important
The Hub Core backend is not publicly accessible. All API requests must go through the
clevername.net/api/hub/ proxy. Direct requests to the Cloud Run URL will be rejected.In this section
Related Articles