Skip to content

Have an AI agent? Let it explore Teleon for you. Any assistant works, personal or coding.

Connect your agent
What your agent reads

The request it copies

Explore teleon.dev for me and report back. Read https://teleon.dev/llms.txt, https://teleon.dev/.well-known/agent-card.json and https://teleon.dev/.well-known/mcp.json. Summarize the shared backend primitives at https://teleon.dev/docs and the THP v1.0 connection steps at https://teleon.dev/connect. Stay read-only.

Discovery files on teleon.dev

Read-only discovery is open. Keep TELEON_KEY in your own environment.

Teleon
Sign inApply for an instance

One plan, one dedicated instance.

Every component, queue and store, set up with your team by the Teleon team.

What the instance includes

90

Atomic components

All components
140
32

Persistent stores

Stores
48

Execution contracts

Contracts
3

MCP tools

Connect
1

Dedicated instance

Console

Counts read from teleon.dev on October 25, 2026.

Instance

One plan

$2,500a month

Founding rate$1,000 a month
  • A dedicated instance, set up with your team by the Teleon team
  • Every atomic component, queue and persistent store
  • MCP, the API and the plugin kit for your agents
  • The console for usage, keys and connected agents

Prices as of October 25, 2026.

What is a dedicated instance?

Your own Teleon instance: every atomic component, queue and persistent store, set up for your problem with your team by the Teleon team.

How do we start?

Apply at teleon.dev/apply with your organization, the problem, your team, your timeline and a contact. The Teleon team replies by email to plan the setup.

Which agents can connect?

Any agent that speaks MCP, at api.teleon.dev/mcp, with three tools. Sites and tools call api.teleon.dev/v1/<component> after one handshake, and one plugin kit loads in ten coding hosts.

How are keys handled?

Each key has a name, such as TELEON_KEY, and a scope, such as claim and submit. The console lists keys by name, with their scope and last use.

Where do we see usage?

In the console at teleon.dev/console: the instance, its components, queues and stores, usage by day, keys and connected agents.

What license covers the specification?

Apache-2.0 or MIT-0. The specification is archived as swh:1:cnt:ef1e0bf7c6f94c2d1c2ddaaf92c09a016e3c845e.

Where do we check service status?

At teleon.dev/status, with readings from the six-hour pulse.