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
Make

Describe each capability once, precisely.

teleon.dev/docs/capabilities holds versioned spec cards for every capability: typed inputs and outputs, the checks that prove it worked, and the refusal codes it returns when a request falls outside its scope.

teleon.dev/docs/capabilitiesSpec v1httpsjson
One purpose, swappable methods
Purpose: expose our API to agentsteleon_purpose_task/v1
compiled to capability steps
openapi_to_mcp_serverv1.3, code-first
grpc_to_mcp_bridgev0.9
hand_written_toolstemplate

The purpose stays fixed. Any capability whose ports and checks fit can carry it out.

What it does

Typed inputs and outputs

Every port names its type, so tools connect only where they fit.

Intent apart from method

A purpose task says what you want; capability tasks are the swappable ways to do it.

Clear refusal codes

A request outside scope returns a named code and the nearest capability that fits.

The contract

A PurposeTask states the goal; one or more CapabilityTasks carry it out, each with its own version.

Speccapability_task_spec/v1
Intentteleon_purpose_task/v1
VersioningEach spec carries its own version and changelog
AccessRING-3 to read
Identifiers
  • teleon_purpose_task/v1
  • capability_task_spec/v1
Spec cardCopy
{ "capability": "openapi_to_mcp_server", "version": "1.3.0", "inputs": {"spec": "application/openapi+yaml"}, "outputs": {"server": "mcp_server_bundle", "tests": "test_report"}, "checks": ["tools_listed", "auth_passthrough", "contract_tests_pass"], "refusals": {"R_SPEC_INVALID": "the spec failed validation"} }

Endpoints

MethodPathAccessWhat it doesStatus
GET/capabilitiesRING-3Browse capability specsListed
GET/capabilities/{name}RING-3Read one spec with its versions
POST/capabilities/{name}/compileRING-2Compile a purpose task into capability steps

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/capabilities.

For agents

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

Agent prompt
Read https://teleon.dev/docs/capabilities and find the spec for turning an OpenAPI file into an MCP server. Read only.
Copy

Words on this page

Full glossary
Contract
A versioned agreement on the shape of a request and response, so either side can change behind it safely.
Capability card
A short description of what a component does, its typed inputs and outputs and its license, sized for an agent's context.
DAG
A directed acyclic graph: steps joined by one-way edges, so work flows forward in a known order.