# Telnyx

> [llms.txt](https://www.mintlify.com/llms.txt)

[telnyx.com](https://telnyx.com)

- **Overall score:** 87/100 (Grade B)
- **Checks passed:** 24 / 35
- **Last computed:** 2026-11-16

## Components

### Content Discoverability

- **Score:** 75/100 · **Status:** partial
- **Summary:** 4 warnings across 7 AFDocs checks.
- **Rationale:** Agents need a clear entry point and crawl map before they can reliably discover the right pages.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **LLMS TXT Exists** — llms.txt found at https://telnyx.com/llms.txt
- ✅ **LLMS TXT Valid** — llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)
- ✅ **LLMS TXT Size** — llms.txt is 18,645 characters (under 50,000 threshold)
- ⚠️ **LLMS TXT Links Resolve** — All 15 same-origin sampled links resolve (70 total links) (3 external links also failed; may be bot-detection or rate-limiting) 3 of 30 links in your llms.txt return errors. Audit and fix or remove broken URLs to prevent agents from hitting dead ends.
- ⚠️ **LLMS TXT Links Markdown** — Same-origin links point to HTML, but 1 have .md variants available (20 external links excluded) Some links in your llms.txt point to HTML pages instead of markdown. Where possible, update links to use .md URLs so agents get clean markdown content directly.
- ⚠️ **LLMS TXT Directive Html** — llms.txt directive found in HTML of 1 of 14 sampled pages (13 missing) An llms.txt directive was found in the HTML of some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every documentation page.
- ⚠️ **LLMS TXT Directive MD** — llms.txt directive found in markdown of 3 of 6 sampled pages (3 missing); 8 had no markdown version An llms.txt directive was found in the markdown of some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every markdown page.

### Markdown Availability

- **Score:** 82/100 · **Status:** partial
- **Summary:** 1 warning across 2 AFDocs checks.
- **Rationale:** When markdown is available directly, agents spend less effort stripping presentation markup and guessing structure.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Markdown Url Support** — 6/6 sampled pages support .md URLs (100%)
- ⚠️ **Content Negotiation** — Content negotiation partially supported: 3 correct type, 0 wrong type, 3 HTML only Your server returns markdown content for Accept: text/markdown requests but with an incorrect Content-Type header. Set the response Content-Type to text/markdown for proper agent handling.

### Page Size and Truncation Risk

- **Score:** 89/100 · **Status:** fail
- **Summary:** 2 failed across 6 AFDocs checks.
- **Rationale:** Large pages, delayed primary content, and markdown that cannot be read in one fetch increase truncation risk and make retrieval less reliable.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Rendering Strategy** — All 14 sampled pages contain server-rendered content
- ✅ **Page Size Markdown** — All 6 pages under 50K chars (median 10K, max 19K)
- ❌ **Page Size Html** — 1 of 14 sampled pages convert to over 100K chars (max 307K HTML → 134K markdown (12% boilerplate)) 1 of 14 pages convert to over 100K characters of markdown. Break large pages into smaller units, reduce navigation boilerplate, or provide markdown versions that bypass the HTML conversion overhead.
- ✅ **Page Size Transfer** — All 14 sampled pages serve under 1MB (median 9KB served → 9KB content (~1:1))
- ❌ **Content Start Position** — 7 of 14 sampled pages have content starting past 50% (worst 100%) 7 of 14 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.
- ✅ **Single Fetch Completeness** — All 6 sampled markdown pages deliver complete content in one fetch (no pagination detected)

### Content Structure

- **Score:** 100/100 · **Status:** pass
- **Summary:** 5 AFDocs checks pass.
- **Rationale:** Predictable sections, valid code fences, serialized tabs, portable links, and pages not dominated by bulk data make the content easier for agents to parse correctly.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Tabbed Content Serialization** — No tabbed content detected across 14 sampled pages
- ✅ **Section Header Quality** — No tabbed content found; header quality check not applicable
- ✅ **Markdown Code Fence Validity** — All 0 code fences properly closed across 7 pages
- ✅ **Markdown Link Portability** — All 76 links across 6 sampled markdown pages are absolute; 8 sampled links resolve to the expected representation
- ✅ **Embedded Data Serialization** — Bulk data on 5 of 14 sampled pages, but no page is oversized because of it

### URL Stability and Redirects

- **Score:** 100/100 · **Status:** pass
- **Summary:** 2 AFDocs checks pass.
- **Rationale:** Stable URLs and sane redirect behavior prevent retrieval drift and broken tool references.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Http Status Codes** — All 14 sampled pages return proper error codes for bad URLs
- ✅ **Redirect Behavior** — No redirects detected across 14 sampled pages

### Observability and Content Health

- **Score:** 100/100 · **Status:** fail
- **Summary:** 1 failed across 3 AFDocs checks.
- **Rationale:** Coverage, parity, and cache behavior determine whether agents can trust the content they retrieve.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **LLMS TXT Coverage** — llms.txt covers 100% of 0 sitemap doc pages; 782 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)
- ❌ **Markdown Content Parity** — 1 of 6 pages have substantive content differences between markdown and HTML (avg 13% missing) 1 pages have substantive content differences between markdown and HTML (avg 13% missing). If unintentional, agents are getting outdated content; regenerate markdown from source or fix the build pipeline. If intentional (audience segmentation), add data-markdown-ignore to human-only HTML elements, or adjust thresholds with --parity-pass-threshold/--parity-warn-threshold.
- ✅ **Cache Header Hygiene** — All 15 endpoints have appropriate cache headers

### Authentication and Access

- **Score:** 100/100 · **Status:** partial
- **Summary:** 1 skipped across 3 AFDocs checks.
- **Rationale:** Agents need public access, or a clear alternative path when documentation is gated behind auth, without bot protection blocking automated fetches.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Auth Gate Detection** — All 14 sampled pages are publicly accessible
- ⏭️ **Auth Alternative Access** — All docs pages are publicly accessible; no alternative access paths needed
- ✅ **Bot Protection Interference** — No bot-protection interference observed across 222 requests

### Full Content Discoverability

- **Score:** 100/100 · **Status:** pass
- **Summary:** llms-full.txt passes all checks.
- **Rationale:** A full-document snapshot gives long-context agents a single canonical corpus to ingest without repeated crawling.
- **Reference:** [llms-full.txt guide](https://www.mintlify.com/docs/ai/llmstxt#llms-full-txt)

**Checks**

- ✅ **LLMS Full Exists** — Found llms-full.txt.
- ✅ **LLMS Full Size** — llms-full.txt size is within the expected range.
- ✅ **LLMS Full Valid** — llms-full.txt has a recognizable markdown structure.
- ✅ **LLMS Full Links Resolve** — llms-full.txt links resolve successfully.

### Agent Skills

- **Score:** 100/100 · **Status:** pass
- **Summary:** skill.md passes all checks.
- **Rationale:** Agent skills provide product-specific operating guidance that plain documentation pages do not encode on their own.
- **Reference:** [skill.md guide](https://www.mintlify.com/docs/ai/skillmd)

**Checks**

- ✅ **Skill MD** — Found an agent skill definition.

### MCP Server

- **Score:** 0/100 · **Status:** fail
- **Summary:** MCP has 1 failing check.
- **Rationale:** A discoverable MCP server lets agents use first-class tools instead of scraping pages and inferring behavior.
- **Reference:** [MCP guide](https://www.mintlify.com/docs/ai/model-context-protocol)

**Checks**

- ❌ **MCP Server Discoverable** — No MCP server was discovered at the expected endpoints.
- ⏭️ **MCP Tool Count** — Skipped because the MCP server was not discoverable.
