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
Work

Route each call to the right lane.

teleon.dev/docs/switchboard sends every harness request down one of three lanes: library answers, your own keys, or managed credits. Keys stay sealed in a vault and every site keeps its own cookies and tokens.

teleon.dev/docs/switchboardSwitchboardhttpsjsonmcp
One request, three lanes
Request from a sitesummarize_repo
Lane chosen by rule
Libraryanswer from cards
Your keyvault grant
Creditsmanaged pool
Result returnedwith the lane recorded

The switchboard tries the library first, then your key, then managed credits, as the rule allows.

What it does

Three lanes

Library answers first, your own keys second, managed credits third, by rule.

Sealed keys

Your API keys live behind vault references and reach the provider through short-lived grants.

Separate sites

Each site keeps its own cookies and token realm.

The contract

A routing decision names the lane, the grant and the site realm for each call.

LanesLibrary, bring your own key, managed credits
KeysSealed behind vault references
IsolationPer-site cookies and token realms
AccessRING-2
Identifiers
  • teleon_harness_switchboard_decision/v1
  • teleon_vault_sealed_credential/v1
Request and responseCopy
POST /v1/route { "surface": "files_site", "task": "summarize_repo", "prefer": "library" } # Response { "lane": "library", "answer_source": "teleon.dev/docs/cards", "grant": null }

Endpoints

MethodPathAccessWhat it doesStatus
POST/v1/routeRING-2Choose a lane for one request
GET/v1/workspaceRING-2Read the workspace, vault slots and grantsListed
POST/v1/vault/slotsRING-2Seal a key into a vault slot

Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/switchboard.

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt
Read https://teleon.dev/docs/switchboard.md and explain the three lanes. Read only: ask me before sealing any key.
Copy

Words on this page

Full glossary
Access ring
One of four access levels. RING-0 is internal operations, RING-1 operators, RING-2 keyed agents and sites, RING-3 public reads.
Contract
A versioned agreement on the shape of a request and response, so either side can change behind it safely.