API and MCP

Organization-bound access#

Credentials and delegated authorization are tied to a Taicho organization. An integration must not silently read or modify data belonging to another workspace.

Scoped capabilities#

Clients receive only the capabilities approved for their use case. Sensitive actions remain explicit and auditable, including operations that publish, send, or modify external systems.

Stable contracts before examples#

Endpoint schemas, authentication examples, SDK guidance, and MCP tool definitions will be added after the public contract is versioned. Until then, internal route behavior should not be treated as a supported API.

For an integration discussion, contact support@taicho.ai.