Deep Conrad AI Developers

Production API access, key management, and implementation guides.

Real Developer Platform

Build on Conrad with live API keys, real docs, and a production-ready console.

The developer section now exposes a real authenticated API surface instead of a chat shortcut. Start with quickstart docs, issue keys from the console, and send requests to a stable chat completion endpoint.

Base endpoint

https://conrad-chatbot-230nuizxh-dan-projects-dc8caa0f.vercel.app/api/v1/chat/completions
First request
One endpoint, bearer auth, JSON payloads.
curl https://conrad-chatbot-230nuizxh-dan-projects-dc8caa0f.vercel.app/api/v1/chat/completions \
  -H "Authorization: Bearer YOUR_DEVELOPER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "conrad-balanced",
    "messages": [
      { "role": "user", "content": "Draft a rollout plan for a risky migration." }
    ]
  }'

Conrad Fast

Lower latency for short operational prompts.

conrad-fast

Conrad Balanced

Default model for production assistants and tooling.

conrad-balanced
Live API endpoint
Ship against a real `/api/v1/chat/completions` endpoint with bearer auth and JSON responses.
Key management
Issue, rotate, and revoke server-side API keys from an authenticated developer console.
Operational docs
Move from first curl request to production integration with quickstart and reference pages.
Plan-aware access
API access is tied to account billing plan so product usage and developer access stay aligned.
What changed
The old developer route was a gated prompt room. This section is now a real developer surface.

Public docs are now available without login.

Authenticated users can issue and revoke API keys from the console.

A live chat-completions endpoint is available for server-to-server requests.

Usage and model access are derived from account plan, not a disconnected marketing page.