Start small. Preview a definition before you run it. Check the actual result in Telbox. Revoke access when the test is finished. A saved definition or accepted request does not prove delivery to your phone.
REQUEST LAB
Explore a voice-note request.
Inspect the request and its permissions. Live voice-note sending is not available on this deployment.
Voice-note sending is unavailable on this deployment.
Response
Text-to-speech turns the sentence into audio in a built-in English voice. Telbox can access this audio to provide playback.
CREATE AN AUTOMATION
What should Telbox help with?
Start with an outcome. We'll draft the steps for you to review. Drafting does not create or run an agent.
Include when it should run, what it should read, and what you want back.
Scoped server-to-server keys for the REST API (/v1/*). The MCP surface uses OAuth-minted tokens, not direct keys. Shown once on create. Store them securely. Rotate or revoke any time.
Scopes: what this key is allowed to do
MCP · both directions
Agent tools & MCP.
Let your agents use tools from other apps, and let any MCP-compatible client talk to your agents. Each connection is scoped and revocable.
Review your agents’ MCP endpoints and existing external servers. Endpoint access depends on the agent’s visibility and the caller’s OAuth permissions. Creating a new external connection is not available here yet.
Access
Apps with access.
Third-party apps and MCP-compatible clients you've granted access to via OAuth. Revoke any time.
Events
Webhooks
Telbox sends a POST when an event happens. Verify its HMAC signature with the signing secret shown when you create the webhook.
Events
Recent deliveries
Every signed POST Telbox sends: event, HTTP status, response time, retries.
The console can’t show deliveries yet. Your server’s own logs show each POST Telbox sends. The HMAC signing secret is shown once at creation; verify it on each incoming POST.
API & MCP
Reference
Six tools. OAuth 2.1 with PKCE. Register a client with Dynamic Client Registration, complete the device flow, then call the MCP surface with a scoped bearer token. A new client is reviewed by Telbox before it can be used.
Create → run → inspect → talk to the world. Every call is a real endpoint the console itself uses.
# set these once: create a key on the API keys page with the agents:read and agents:write scopes
export TELBOX=https://api.telbox.ai
export KEY=tb_live_…
# 1 · install an agent from a template → returns its id
curl -X POST $TELBOX/v1/agents/from-template \
-H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
-d '{"template_id":"vip-watcher"}'
# 2 · or build one from a typed IR (what Studio ships)
curl -X POST $TELBOX/v1/agents \
-H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
-d '{"name":"Nudge","triggers":[{"kind":"schedule","cron":"0 9 * * 1"}],
"steps":[{"id":"s1","type":"tool","tool":"get_tasks"},
{"id":"s2","type":"tool","tool":"create_reminder",
"args":{"title":{"prompt":"follow up with non-repliers"}}}],
"guards":{"capabilities":{"reminders":{"level":"auto_act_limited"}}}}'
# 3 · test-run it (durable, side-effect aware) and read the trace
curl -X POST $TELBOX/v1/agents/$AGENT_ID/test-run \
-H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \
-d '{"prompt":"Give me a quick status of this thread."}'
curl $TELBOX/v1/agents/$AGENT_ID/runs -H "Authorization: Bearer $KEY"
# 4 · call the MCP surface (global server, or a published agent's own /mcp).# /mcp takes an OAuth access token (the flow above), not the console key in $KEY.
export MCP_TOKEN=…
curl -X POST $TELBOX/mcp \
-H "Authorization: Bearer $MCP_TOKEN" -H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{
"name":"send_message",
"arguments":{"thread_id":"THREAD_ID","content":"On it."}}}'
Every published agent is also its own OAuth-gated MCP server at POST /v1/agents/{id}/mcp. Point any MCP-compatible client straight at it. Full machine-readable schema at /openapi.json.
PLANS & USAGE
Know what you're paying for.
Your Telbox plan, an external AI subscription, and a production application's usage are separate things.
Free and Plus cover the features and allowances described in your Telbox plan. Plus is available through the iPhone app. Pro and Business remain planned offerings.
EXTERNAL AI
Your AI provider's plan
Connecting an AI app does not transfer its subscription or API credits to Telbox. That provider's own plan and charges still apply.
BUILDING FOR OTHERS
Developer usage
This console does not yet provide a confirmed developer rate card. Do not assume a personal subscription includes unrestricted application hosting or third-party AI usage.
ADVANCED EDITOR
Build a definition.
Drag triggers, tools, and logic onto the canvas and connect them into a working bot, no code. Every block is a real, verified capability; risky actions ask first.
Assemble triggers and tools into an agent definition. Preview effects and review authority before saving. Creating an agent does not run it.
Drag a trigger from the left onto the canvas to begin. Then drop tools and connect them by dragging from the bottom dot to the next block.
Select a block to configure it.
Build in any language
SDKs & snippets
HTTP examples for message proposals and saved agent definitions. Replace sample values and use the credential type shown with each example. The request lab explains the voice-note request and its current availability.