Skip to main content
Your assistant sees these tools with full descriptions and argument lists; this page is the map. Tools marked † need your approval — see Safety. Which tools appear depends on the key: a Read-only key sees only the tools that look; a Build key sees everything except sending, calling and the WhatsApp tools that reach a person (marked ‡ below); a Full access key sees all of them. Ids are prefixed by what they are: ag_ agent, act_ action, conv_ conversation, cust_ contact, doc_ document, wh_ webhook; calls are out_ (placed) or sch_ (queued). Lists are newest first and take limit (up to 100) and cursor.

Agents

Connecting the agent to WhatsApp, a phone number or your website is still done in the console.

Knowledge

Knowledge is stored with us. For data that must stay in your database, use an action instead — see Keep your data in your database.

Actions — your own API

Contacts

Conversations

WhatsApp

Calls

Webhooks

Campaigns

Your assistant creates the draft, tells you how many people it reaches, and launches only after you approve. Scheduling a start time is done in the console.

Usage and analytics

The same numbers the console shows. All four work with a Read-only key. See Usage and analytics.

The rest of the console

Everything else the console does is a tool too, one per API operation, with the API reference’s own description — so your assistant reads the same rules you do. Which key sees which tool follows the API exactly: a tool appears only if your key may make that request. Done in the console, never by your assistant — anything that would put a secret in its conversation: connecting an account with a key or token (Cal.com, CRMs, helpdesks, carriers), a Telegram bot’s token, a tool server that needs a token, the keys for bring your own keys, and your SMS provider’s keys. Also a call’s recording (it is audio), cloning a voice (it needs a recording) and scheduling a campaign’s start time.

Customers — for developers

If you build your own product on ThinnestAI, your customers are workspaces under yours. Manage them from your own connection: Creating, changing, deleting and restoring a customer need a Full access key. To work inside one customer, add a second server entry with the header Thinnest-Workspace: org_… — every tool there acts in that customer. See Customers. Your customers’ API keys are created in the console, not by your assistant, so no key ever appears in its conversation.

Bring your own keys

Adding provider keys and switching bring-your-own-keys on or off are done in the console, under Settings → Your keys. See Bring your own keys.

Guides

read_guide gives your assistant two built-in how-tos: own-database and dashboards. Ask it to read the relevant one before building an integration.

Prompts

Ready-made commands your client lists — in Claude Code, type / to see them. Each is a worked plan with the points where you approve written in. A Read-only key is offered only weekly_report.