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

Know which role decides at each company.

teleon.dev/docs/contacts keeps a verified graph of business decision makers: the roles that buy, approve and sign at each company. Every role links to the public record that names it.

v32.0teleon.dev/docs/contactsContacts feedhttpsjson
Roles at one company group
RoleCompanyNamed inRead
Chief procurement officerMeridian Holdingsannual reportOct 23
Chief financial officerMeridian HoldingsForm 4Oct 24
Head of purchasingMeridian Logisticsstate filingOct 20

Each role is listed with the public record that names it and the date Teleon read that record.

What it does

Roles on the hierarchy

Each role sits under its company in the S101 hierarchy, so a buyer at a subsidiary rolls up to its parent.

Verified from public records

A role joins the graph when a public record names it, such as an annual report or a business filing.

Changes as they publish

New officers and changed titles reach the change stream as their records publish.

The contract

A role record names the company, the title and the public record behind it, with that record's license and read time.

StoreS102, added in v32.0
HoldsVerified decision-maker graph
SourcingPublic business records, cited per role
RecordsEach record carries its source, license and read time
Identifiers
  • contacts.role
  • contacts.role_source
Request and responseCopy
GET /v1/contacts/roles?company=ent_4410&function=procurement&limit=2 Host: api.teleon.dev # Response { "roles": [ {"id": "role_3302", "company": "Meridian Holdings Ltd", "title": "Chief procurement officer", "function": "procurement", "contact": "procurement@example.com", "verified_by": "annual report 2025", "license": "terms:registry", "read_at": "2026-10-23T11:05:40Z"}, {"id": "role_3318", "company": "Meridian Logistics LLC", "title": "Head of purchasing", "function": "procurement", "verified_by": "state business filing", "license": "terms:state", "read_at": "2026-10-20T08:47:13Z"} ], "next_cursor": "c_19a2" }

Endpoints

MethodPathAccessWhat it doesStatus
GET/v1/contacts/rolesRING-3List roles by company and function
GET/v1/contacts/roles/{id}RING-3Read one role with the public record that names it
GET/v1/contacts/changes?since={cursor}RING-3Stream new and changed roles since a cursor
POST/v1/contacts/watchesRING-2Watch a company for role changes

Listed paths appear in the service’s published files today. This surface comes from the Teleon Omnibus Codex v1.0 to v50.0, Oct 25, 2026. In the one-host plan every path here is served under api.teleon.dev/v1/contacts.

For agents

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

Agent prompt
Read https://teleon.dev/docs/contacts.md and list the procurement roles at one company with the record that names each. Read only.
Copy

Words on this page

Full glossary
Entity resolution
Deciding which records from different sources describe the same company. Splink scores each candidate pair with a probabilistic match model.
Record license
The terms that came with a record from its source, stored on the record itself so every reader sees them.
Read time
When Teleon fetched a record from its source. It sits beside the source's own dates, so readers can judge how fresh each record is.
Change cursor
A position in a feed's change stream. A reader sends the last cursor it saw and gets every change after it, in order.