Developer guides
Start here: get an API key, make your first SDK call, then wire it into your own server.
Get your API key
Create an organization and an app in the Console, and get the client_id and client_secret you'll use to call the SDK.
Choose your integration path
Four ways to call Quravin — plain webpage, React SPA, Node.js server, or raw API with no SDK. Pick the one that matches your stack.
Choose your auth mode
Two ways to authenticate the SDK — a decision tree for whether you need a static API key or a per-user session JWT.
Plain webpage direct integration
Drop a script tag on any page — no build step, no framework — and call the API from a static or server-rendered HTML page.
React SPA integration
Wire the Quravin SDK into a React component with a small custom hook — one client instance, real loading/error state, no re-instantiation on every render.
Node.js server integration
Two patterns for a Node.js backend: mint session tokens for a browser frontend, or call the API directly from server-only code.
Direct API integration
Call the API with plain HTTP — no SDK, any language. The exact anonymous and authenticated request/response shapes, with curl examples.
Tool reference
Every built-in tool's inputs, valid values, and output shape — the complete reference behind the quick-start guides.
Raw prompt mode
Send a custom system/user prompt straight to the model instead of a named pipeline — request shape and the constraints that don't apply to named pipelines.