Q Developer Hub
Choose a practical integration path for retrieval, grounded answers, durable agents and extensions.
Build against Q's public /v1 API for retrieval, grounded answers and agent execution. Start with Build with Q to connect your own backend without cloning this repository. For credential-free exploration, use the local sandbox. For a browser product, use the React backend-proxy starter.
The default API root is https://api.qdivision.ai/v1. A deployment's /capabilities and /openapi.public.json are authoritative for its operations, scopes, feature gates and schemas. This checkout includes locally qualified, unpublished SDK 1.1.0 archives; use the matching API and support matrix.
Choose a path
Start safely
Credentials come from your provisioned Q environment and belong on your backend. Grant only the scopes required by the deployment's advertised operations. A q_test_ prefix does not by itself isolate data or prove that provider calls are free. Use the local synthetic sandbox for credential-free protocol work; see authentication.
For answers, inspect the final sources, citations, evidence and quality. Draft tokens and an open connection are not a successful final result. For agents, retain the operation keys and returned receipt, request Temporal explicitly when required, and poll the original run. Consult operation metadata before retrying a mutation; a new key can create new work.
The examples index distinguishes the qualified entry examples from older, specialised demonstrations. The Q2.5 evidence records clean-environment and browser qualification. Local protocol tests do not certify live provider accuracy, deployment capacity or process-restart recovery.
- Durable run lifecycle — states, waits, recovery, cancellation, deadlines and operator rollout.
Managed agent consumers should read the event journal and replay contract, including revision replacement, cursor expiry and result-access errors.
-
Document ingestion quality and freshness — supported formats, current indexing state, safe errors and recovery.
-
MCP interoperability profile — supported revisions, tools, cancellation, client example and deployment requirements.
-
A2A interoperability profile — standard discovery, durable text tasks, streaming, cancellation and external agents.
Data use, retention and erasure: Data governance.
Operational release and recovery procedures: Deployment and data recovery.