Developers
Bring the assistant to your app, your MCP client or your website. Every door costs the same as the chat app.
POST/api/v1/conversations
Start a conversation: { text, locale?, model?, tools? } — use tools to create images, video, music or speech.
curl -X POST "https://bilgisam.com/api/v1/conversations" \
-H "Authorization: Bearer sk_..." \
-H "Content-Type: application/json" \
-d '{"text":"…","locale":"en"}'Response body
The response will appear here.
Documentation
REST API
JSON in, JSON out. Answers are written in the background: send a message, then read the conversation until `pending` is false.
POST/api/v1/conversationsStart a conversation: { text, locale?, model?, tools? } — use tools to create images, video, music or speech.POST/api/v1/conversations/{id}Add a message: { text, locale?, model?, tools? }GET/api/v1/conversations/{id}Latest messages and the `pending` stateGET/api/v1/conversationsYour recent conversationsGET/api/v1/creditsYour remaining creditsGET/api/v1/toolsAvailable tools and their credit costs
curl -X POST https://bilgisam.com/api/v1/conversations \
-H "Authorization: Bearer sk_..." \
-H "Content-Type: application/json" \
-d '{"text": "Merhaba", "locale": "en"}'
# → {"id": "…"} — read the answer a few seconds later
curl https://bilgisam.com/api/v1/conversations/{id} -H "Authorization: Bearer sk_..."Optional fields: instructions (system instructions for this turn, up to 20,000 characters; send them with every request), private (true → 402 needs-private if your plan doesn’t allow private chats). API answers don’t use thinking (model reasoning): fast and fixed-cost.
Errors: 401 invalid key · 402 not enough credits or Pro required · 409 previous answer in progress or consent required · 429 rate limit.