Frequently asked questions

Open the app and go to Settings → API Keys, then create a key. It is shown only once, so copy it immediately and store it somewhere safe. The key starts with dq_live_ and inherits your knowledge-base access.

Not yet. There are no enforced request limits today, but rate limiting is on the roadmap. Build retries with backoff so your integration stays robust when it ships.

By default, queries are answered with deepseek-chat. You can override it per request by passing a "model" field in the /query body. The response echoes back the resolved model so you always know what produced the answer.

{
  "query": "What is our refund window?",
  "model": "deepseek-chat"
}

Every read and query is scoped to the knowledge bases your key can reach — the ones you own plus any shared with you read-only. You can never retrieve or query another tenant’s data; requests for KBs you cannot see return 403 or 404.

Not in v1. The /documents endpoint ingests raw text and markdown via the "content" field. To add PDFs, upload them in the app for now — PDF support over the API is planned for a future version.

Go to Settings → API Keys in the app and revoke the key. Revocation takes effect immediately — the key stops authenticating on the next request. If a key may have leaked, revoke it and mint a replacement right away.

Each citation ties the answer back to its source: a document_id, the document title, the exact snippet the answer drew from, and a similarity score between 0 and 1. Use them to show provenance or to let users open the underlying source.

{
  "document_id": "6e2f0a8c-9b41-4d7e-8a3f-c05e9b1d7264",
  "title": "refunds.md",
  "snippet": "Refunds are issued within 14 days of purchase.",
  "similarity": 0.91
}