Developer API
Your first call
Anything with an HTTP client works — curl, your backend, a workflow tool, another agent.
Authenticate with a workspace key
Create a key in the dashboard and send it as an X-Api-Key header. Keys carry read or write scope, and a key can be locked to a single product — so an integration only ever touches what you gave it.
https://api.supercognit.com/v1curl https://api.supercognit.com/v1/products \
-H "X-Api-Key: $SUPERCOGNIT_API_KEY"What the API covers
What you can do in the dashboard, your code can do too — same workspace, same resources.
- Products
/v1/productsCreate, update, publish and unpublish chat agents and MCP servers — prompt, summary, slug and price included. - Tools
/v1/toolsManage the workspace tool library: LLM, HTTP and static tools, their inputs, and which products use them. - Knowledge bases
/v1/knowledge-basesList the knowledge behind your answers and see which products each base is attached to. - Conversations
/v1/sessionsRead conversations and full transcripts — every message, model and token count, ready for your analytics or your CRM. - Webhooks
/v1/webhooksRegister endpoints, inspect deliveries and retries, and re-enable an endpoint without touching the dashboard. - Wallet
/v1/walletRead the usage-credit balance and every top-up, charge and refund behind it. - End users
/v1/verify-userVerify a chat session token server-side, so your own app can trust who it is talking to.
What teams build with it
- An agent per customerAgencies and SaaS teams create, configure and publish one agent per client straight from their own onboarding flow — no clicking through the dashboard.
- Conversations in your CRMStream every conversation and captured contact into HubSpot, Salesforce or your own database as it happens.
- Knowledge that stays currentRefresh a knowledge source when your docs change, so answers follow your product instead of trailing behind it.
- Usage you can bill onRead the wallet and the transcripts to see exactly what an account consumed, then charge for it inside your own product.
Events, pushed to you
Register an endpoint and SuperCognit POSTs JSON as conversations happen. Every request is signed with HMAC-SHA256 over the raw body, retried up to five times with exponential backoff, and kept in a delivery log with its response status.
- conversation.created — someone started a new conversation
- message.created — a message was sent, by a visitor or by the agent
- message.completed — the agent finished its answer
REST for your systems, MCP for AI clients
The API is how your code drives SuperCognit. MCP is how AI clients — Claude, Cursor, your own agents — use what you publish. Both run on the same workspace, so a tool you build once is reachable either way.
Questions developers ask
Still wondering? Ask our agent; it answers from these same pages.