Start with public reference data
Kanbai exposes read-only public template and standard-operating-procedure data. Use the existing OpenAPI description and discovery files to inspect supported operations and response shapes.
For a first request, GET /api/v1/templates returns the public template catalog. Use a returned template identity when asking for a particular record; do not invent a project or template ID.
fetch('https://kanbai.app/api/v1/templates')
.then(response => response.json())
.then(catalog => console.log(catalog));Keep private operations authorized
The public catalog surface is distinct from the authorized project/task API and MCP operations. Use an approved existing account or agent credential and the operation's own contract for private work.
Do not place credentials in browser examples, copied URLs, client-side code or documentation. Request only the access your integration needs.
After a write, read back the intended item through its supported interface and compare the result. A request being accepted is not proof that the intended project content is correct.
Learn before automating
Read the same template and tool explanations your users see, test a small example and define its acceptance criteria before running repeated work.
Related development status
| Feature | Vision | Current state | Gap | Planned timing |
|---|---|---|---|---|
| Application and agent interfaces | People and authorized agents work from consistent project information. | Public catalog discovery and read-only data are distinct from authorized private operations. | Public catalog reads and authorized project operations are separate; automatic cross-application workflows are not provided here. | Not yet scheduled |