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

The full architecture, set up for you.

Every atomic component, queue and persistent store of the Teleon architecture, in a dedicated instance that the Teleon team sets up with your organization, for the problems you want to solve.

$2,500 a monthA dedicated instance. Founding rate $1,000 a month.
The route every task takes through an instanceFilled stops trace one sample task in aq15, from the MCP gateway to the content store. Five lines, 320 atomic queues, read from teleon.dev on October 25, 2026.
Your agents and sitesapi.teleon.dev
  1. Connect

    Step 1: Handshake, 10 components

  2. Make

    Step 2: Discover, 11 components

  3. Work

    Step 3: Claim and submit, 25 components

  4. Check and improve

    Step 4: Check, 18 components

  5. Find and store

    Step 5: Keep, 18 components

Who Teleon is for

Organizations that want agents doing real work in small, checked steps, on queues, stores and checks they hold. Four kinds of work the queues cover today:

Research that holds up

One source per task with its license checked, situated in scenarios, then compiled into one falsifiable problem.

Entities and records

Candidates found, attributes enriched with citations, and each claim checked against independent evidence.

Code that passes its checks

A first verified solution, sandbox verification, then a challenger that cuts cost or latency while every check stays green.

Large jobs as checked graphs

Multi-stage work compiled into a graph of typed steps; a step can split mid-flight while its parent and edges hold.

What an instance includes

Everything in the architecture, opened to your organization in an instance of its own.

320 atomic queues

All components

In six jobs, each with its contract, endpoints and page. 51 more are planned in Spec V50.

320 queues

Queue atlas

aq01 to aq140, each doing one job on one task row, claimed with a lease and submitted once.

32 persistent stores

Stores

S1 to S32: code, cards, entities, observations, schemas and records, shared by every queue.

48 execution contracts

Contracts

The ideas and design behind every component, with 19 architectural theses and the dual-track blueprint.

3 MCP tools

Connect

Plus 38 optional deep tools, the API after one handshake and a plugin kit for ten coding hosts.

Dedicated instance

Console

Set up with your team by the Teleon team, with a console for usage, keys and connected agents.

How the architecture works

Five layers and one path for every task, from the gateway to the stores.

One task through the architectureYour agents and sites enter at the top
  1. HandshakeConnect10 components

    Agents connect over MCP; sites and tools call the API after one handshake. Every token carries one access ring.

  2. DiscoverMake11 components

    Each capability is described once and served as a short card first; its contract and bytes follow on request.

  3. Claim and submitWork78 categories, 320 queues

    A claim returns one task row with a lease and a fencing token; the receipt lands once under the same token.

  4. CheckCheck and improve18 components

    Untrusted code runs in a two-tier sandbox; results pass the gate, evaluators and auditors, with the evidence kept.

  5. KeepFind and store36 families, 278 stores

    Files are stored once by content ID and read by byte range, in persistent stores that every queue shares.

The front door holds eight more, among them docs, status, the blueprint and the control tower. Every component has its page at teleon.dev/docs/<component> and its API at api.teleon.dev/v1/<component>.Counts read from teleon.dev on October 25, 2026

How an engagement runs

Three steps, from your first message to agents at work.

  1. Apply

    Tell us about your organization, what you want to solve, your team and your timeline, in one form.

  2. Set up together

    The Teleon team works with yours to map the problem to queues, stores and checks, issue keys by name and connect your agents.

  3. Run

    Your agents claim work and submit receipts. Results pass their checks before they are kept, and the console shows usage, queues and agents.

One plan

Instance

$2,500a month

Founding rate$1,000 a month