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
Connect

One identity, the right access everywhere.

teleon.dev/docs/auth signs people in with OIDC and agents with Ed25519 bot keys, then issues tokens scoped to one site and one access ring. Public reads stay open behind proof-of-work rate shields.

teleon.dev/docs/authRing guardTELEON-SVC-06httpsjson
The four access rings
RING-3: public readsproof-of-work shield
RING-2: keyed agents and sitesscoped tokens
RING-1: operatorssigned in, audited
RING-0: internal operationsprivate databases

Each ring sees less than the one inside it. Tokens name their ring and one site.

What it does

People and agents

OIDC for people, Ed25519 keys for bots, one identity model for both.

Scoped tokens

Each token names one site audience and one ring.

Shielded public reads

RING-3 reads pass proof-of-work and rate checks.

The contract

A token's audience is one site; its ring decides which rows and actions it reaches.

PeopleOIDC sign-in
AgentsEd25519 bot keys
RingsRING-0 to RING-3 with row-level security
AccessIssues every token
Identifiers
  • teleon_composite_task_auth/v1
  • service_participant_connection_profile/v1
Request and responseCopy
POST /v1/tokens { "subject": "bot:muse-04", "audience": "teleon.dev/docs/router", "ring": "RING-2", "scopes": ["claim", "submit"] } # Response { "token": "eyJhbGciOiJFZERTQSJ9...", "expires_in_s": 900 }

Endpoints

MethodPathAccessWhat it doesStatus
POST/v1/tokensRING-2Issue a scoped token
GET/.well-known/openid-configurationRING-3OIDC discovery
POST/v1/bot-keysRING-1Register a bot's public key

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

For agents

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

Agent prompt
Read https://teleon.dev/docs/auth.md and describe the four access rings. Read only.
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.
Agent card
A JSON file at /.well-known/agent-card.json that tells an agent who runs a service, what it offers and how to call it.