Show agents just enough, then the bytes.

teleon.dev/docs/cards serves capability information in three steps: a compact card, the typed contract, then exact source bytes by range. Agents spend context only on what they choose to open.

teleon.dev/docs/cardsL0 to L2 cardshttpsjsonmcp

Read the docs Copy the agent prompt

Three levels of detail

1L0 cardname, purpose, ports, licenseShort

2L1 contracttypes, checks, byte offsetsMedium

3L2 bytesexact source by rangeOn request

Most agents stop at the card. Those that need it open the contract, then read exact bytes.

What it does

L0: the card

Name, purpose, ports and license in a few lines.

L1: the contract

Typed inputs, outputs and checks with byte offsets into the source.

L2: the bytes

Exact source slices by HTTP range, one symbol at a time.

The contract

Each level links to the next; L2 reads come from the content store by range.

LevelsL0 card, L1 contract, L2 bytes

ReadsHTTP 206 byte ranges

Card sizeSized for an agent's context

AccessRING-3

Identifiers

teleon_l0_capability_card/v1

Execution contracts

Progressive L0-to-L2 disclosure, 1-RTT swarm cycle and AES-GCM vault Switchboard

L0 cardCopy

GET /v1/cards/openapi_to_mcp_server
{
  "name": "openapi_to_mcp_server",
  "purpose": "Expose an OpenAPI service as MCP tools",
  "ports": {"in": "openapi+yaml", "out": "mcp_server_bundle"},
  "license": "MIT",
  "next": "/v1/contracts/openapi_to_mcp_server"
}

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/cards/{name}`	RING-3	Read the L0 card
`GET`	`/v1/contracts/{name}`	RING-3	Read the L1 contract with offsets
`GET`	`/v1/bytes/{swhid}`	RING-3	Read L2 source bytes by range

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

How it connects

Reads from

Content storeteleon.dev/docs/cas Capability specsteleon.dev/docs/capabilities

Feeds into

MCP gatewayapi.teleon.dev/mcp Searchteleon.dev/docs/search Harness switchboardteleon.dev/docs/switchboard

Queuesaq09 aq94

StoresS2 Code Descriptions and L0, L1, L2 Cards

For agents

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

Agent prompt

Read https://teleon.dev/docs/cards.md and fetch the L0 card for openapi_to_mcp_server. Read only.

Copy

llms.txt Agent card MCP card

Words on this page

Full glossary

L0, L1, L2: Three levels of detail for a capability: a short card, the typed contract, then exact source bytes.
Progressive disclosure: Showing an agent a short summary first and the full detail only when it asks, to save context.
Range request: An HTTP request for a span of bytes, answered with status 206.