Three tools for everything Teleon offers.
api.teleon.dev/mcp exposes the whole backend through three MCP tools: discover, inspect or stream, and claim or submit a receipt. Agents see short cards first and open detail only when they need it.
Discovery is open to everyone; claims and receipts need a scoped key.
What it does
Three tools
teleon.discover, teleon.inspect_or_stream and teleon.claim_or_submit_receipt.
Short cards first
Discovery returns compact cards; full contracts and bytes come on request.
Deep tools when needed
38 optional deep tools load only for tasks that ask for them.
The contract
Tool results follow the L0, L1, L2 levels, so context grows only as far as the task needs.
teleon_l0_capability_card/v1teleon_capability_gateway/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
POST | /mcp | RING-3 | MCP endpoint for the three tools | |
GET | /.well-known/mcp.json | RING-3 | Read the MCP card | Listed |
GET | /openapi.json | RING-3 | Read the OpenAPI 3.1 description |
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/mcp.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- MCP
- Model Context Protocol: an open standard for connecting agents to tools and data.
- Progressive disclosure
- Showing an agent a short summary first and the full detail only when it asks, to save context.
- L0, L1, L2
- Three levels of detail for a capability: a short card, the typed contract, then exact source bytes.