Developer documentation

Tychron Docs

Supercharge your customer experiences with powerful communication APIs and deliver better conversations. Our documentation lays out everything you need to get started and customize your platform.

Atlas API Reference Talk to an Expert

APIs

Pick an API

SMS APISend and receive text messages for quick and simple direct communication.Get Started →MMS APIDeliver media rich content directly for a better customer experience.Get Started →CNAM APICut down on scam callers and know who's really on the other end of the line.Get Started →LRN APIGather key information on your phone traffic for better control.Get Started →MCL APIManage your messaging traffic more effectively and with precision.Get Started →Atlas API & Provisioning ReferenceThe complete reference — number ordering, TCR registration, webhooks, opt-out lists and account APIs, in 35 chapters.Open the reference →

AI assistants & coding agents

Use these docs with an AI assistant

Everything here is also published in forms an assistant can ingest directly — Claude, ChatGPT, Codex, Cursor, or your own agent. Paste a URL below into the conversation, or fetch it from a tool. Every chapter page also has a View as Markdown link for handing over just the part you are working on. These files are generated from the same sources as the pages on every build.

llms-full.txt

The complete Atlas API & Provisioning Reference as one Markdown file — every chapter, endpoint, schema and example. One fetch.

llms.txt

The index: what the docs cover and where each chapter and spec lives. Start here when the assistant should decide what to read.

OpenAPI specs

The live Atlas API & Provisioning spec plus SMS, MMS, CNAM, LRN and MCL as OpenAPI 3, for typed clients and request validation.

A starting prompt

Read https://docs.tychron.com/llms-full.txt and the OpenAPI spec at
https://docs.tychron.com/openapi/mms.openapi.yaml.
Then write a Node.js client that sends an MMS with
request_delivery_report: true, plus one webhook receiver for the
Switch endpoint that dispatches on "kind": mms_forward_req (inbound
message) vs mms_delivery_report_req (delivery report). Note the
contract: the send request has no callback URL — Tychron delivers both
payload kinds to the HTTP endpoint configured on the MMS-enabled Switch.
Use the exact field names and error codes from those documents.