Introduction

Thinklio exposes three distinct API surfaces. These are not three versions of the same API — they represent fundamentally different integration patterns with different consumers, different interaction models, and different architectural implications.

The Three API Surfaces

Channel API — Conversational Access

A messaging interface. Your system sends messages to a Thinklio agent and receives responses, exactly as a user would via Telegram or web chat. Use this when you want to embed a Thinklio agent into your own product — a mobile app assistant, an in-app support widget, or an internal tool.

The Channel API treats your integration as a channel adapter. Messages become universal events inside Thinklio, and all governance (policies, budgets, audit) applies exactly as it does for any other channel.

Status: Beta — available now for early access partners.

Platform API — Orchestration and Management

Programmatic access to Thinklio's orchestration capabilities. Create agents, dispatch jobs, manage knowledge, query usage, and control the full lifecycle of agents and their work.

Use this when you are building on top of Thinklio rather than just talking through it — operations teams automating agent deployment, CI/CD pipelines managing agent configurations, or external workflow engines treating Thinklio agents as workers.

Status: Coming soon — planned for Phase 4.

Integration API — Bidirectional Capability Exchange

Register your external system as a tool available to Thinklio agents, and subscribe to Thinklio events. A CRM can register itself so agents can query customer records. A project management tool can register so agents can create tasks. Any external system can offer its capabilities to Thinklio agents through this surface.

Status: Coming soon — planned for future phases.

Design Principles

All three surfaces share the same authorisation model, the same governance framework, and the same cost attribution mechanism. An action blocked by org policy is blocked regardless of which API surface it comes through.

Every surface is versioned independently. Breaking changes require a new version with a deprecation period.