Developer overview
Find published Voice and Verification OpenAPI contracts, product integration guides and bounded human/AI documentation formats.
Documentation formats
Public documentation is intentionally readable without authentication. Use:
/llms.txtfor the section router, then/llms/<section>.txtfor the relevant guide list;/raw/<slug>.mdfor one Markdown page;/api/docs/catalog?limit=100&offset=0for bounded public metadata; followhasMorewith the next offset;/api/docs/page?slug=<slug>for one structured page;/api/docs/search?q=<query>for weighted full-text search;- Voice API OpenAPI and Verification API OpenAPI for published machine-readable contracts.
For setup, examples and scope, start with Voice, Verification, Commerce or CRM.
Product API authentication
Public documentation does not make a product API public. Each API contract defines its own Boni One user, service-account, scope, tenant, workspace, idempotency, and approval requirements. Never put a product credential in a browser URL or Knowledge file.
Versioning
Documentation records expose their version, content hash, and update time. OpenAPI filenames and contract versions remain stable and are changed deliberately. Integrations should use documented idempotency and error contracts rather than scraping the human UI.