telnyx.com

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ✓Sitemap present & freshrequired4/4

  Sitemap at https://telnyx.com/sitemap.xml: 2061 entries, freshest <lastmod> 2026-08-17 (1 days ago)

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✓Brand search discoverabilityrequired4/4

  Both searches ("Telnyx" and "Telnyx communication support") cited telnyx.com: https://developers.telnyx.com/api-reference/mdr-usage-reports/generate-and-fetch-mdr-usage-report, https://support.telnyx.com/en/articles/1130611-understand-telnyx-sms-mdr-report-log, https://developers.telnyx.com/api-reference/organization-users/get-organization-users-groups-report, https://support.telnyx.com/en/articles/4363904-sip-registration, https://support.telnyx.com/en/collections/3968237-telnyx-sip-trunking-configurations

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• ✓MCP registry listingsrecommended4/4

  /.well-known/mcp/server-card.json serves JSON; searched "telnyx.com" and "Telnyx": listed in Glama, Smithery (2 of 3 reachable registries)

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✓robots.txt present & parseablerequired2/2

  /robots.txt parses: 3 User-agent group(s), 3 Sitemap line(s)

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ◐AI crawler policyrequired2/5

  robots.txt blocks 2 of 12 AI crawler user-agents from /: CCBot, Bytespider

  fix → robots.txt blocks CCBot, Bytespider. Add explicit `User-agent: <bot>` / `Allow: /` groups for AI agents you welcome.

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✓Content Signals directivesemerging2/2

  3 valid Content-Signal line(s) in robots.txt (e.g. `Content-Signal: ai-train=yes, search=yes, ai-input=yes`)

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✓Agent user-agent paritybetarequired4/4

  All three UAs get HTTP 200; bot bodies are ClaudeBot 100%, GPTBot 100% of the browser response (428172 bytes)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✓agents.mdrecommended3/3

  Found https://telnyx.com/agents.md: 1814 chars of markdown with 3 heading(s)

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "Telnyx provides end-to-end infrastructure for real-time AI agents, offering a comprehensive suite of communication and AI services built on its own private network and hardware.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ✓OpenGraph / social metadatarecommended2/2

  Homepage has og:title, og:description, and og:image (twitter:card="summary_large_image" present)

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✓llms.txtrecommended4/4

  /llms.txt is valid llmstxt.org shape: H1 "Telnyx", 76 markdown link(s)

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✓llms-full.txtbonusrecommended2/2

  /llms-full.txt serves 144799 chars of markdown

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✓JSON-LD structured datarequired4/4

  11 JSON-LD block(s) on homepage and pricing page (types: Organization, FAQPage, SoftwareApplication, Service, WebApplication, WebPage, Review, BreadcrumbList); Organization block is well-formed

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✓Markdown content negotiationrecommended3/3

  https://telnyx.com/ returns markdown for `Accept: text/markdown` (content-type text/markdown)

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• ✓Developer resource discoverabilityrecommended3/3

  Search "Telnyx API documentation" cited your own domain: https://developers.telnyx.com/development/api-fundamentals, https://developers.telnyx.com/llms.txt, https://telnyx.com/products/web-search-api, https://telnyx.com/release-notes/web-search-api

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• ✗OpenAPI spec discoverablerequired0/5

  No OpenAPI spec found: checked docs-page links and /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /docs/openapi.json, and api-subdomain locations

  fix → Publish your OpenAPI spec at /openapi.json and link it from docs — it's the single highest-leverage artifact for agent integration.

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✓Docs discoverablerequired4/4

  Docs found at https://developers.telnyx.com/docs/overview (via homepage link, 1466 chars of readable text)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ✓MCP server discoveryrequired5/5

  Valid MCP server card at https://telnyx.com/.well-known/mcp/server-card.json: name "io.github.team-telnyx/telnyx-mcp", endpoint https://github.com/team-telnyx/ai

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• ◐npm SDKrecommended1/2

  Official npm package "telnyx-api" (verified via README mentions the domain) but latest 1.0.3 is stale — published 2024-12-10, over 18 months ago

  fix → Publish a fresh release of "telnyx-api" — agents treat SDKs untouched for 18+ months as abandoned.

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• ✗PyPI SDKrecommended0/2

  No official PyPI SDK found: probed 4 candidate(s) (telnyx, telnyx-sdk, telnyxapi, telnyx-python) — found but not domain-verified: telnyx

  fix → Publish an official Python SDK (suggest "telnyx") with your domain in the project URLs so agents can verify it's official.

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No OpenAPI spec found — nothing to lint

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ◐Docs qualityrecommended2.1/3

  Docs at https://developers.telnyx.com/docs/overview scored clarity 4/5, completeness 3/5, runnable examples 4/5, agent-friendliness 3/5 (mean 3.5/5)

  fix → Docs scored 3/5 on completeness. The documentation provides a high-level overview and quickstart for the Inference API, but lacks comprehensive details on all available APIs, their full specifications, and how to integrate them beyond the basic Python example.

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• ✓Quickstart / getting startedrecommended2/2

  Quickstart found: https://developers.telnyx.com/docs/inference/getting-started (linked from https://developers.telnyx.com/docs/overview) returns 200 with a code block

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No tools listed by the MCP endpoint — nothing to lint

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://telnyx.com/ upgrades to https in 1 hop(s), 1 redirect(s) total, final HTTP 200; HSTS present

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ✓Response speed & weightrequired1/1

  Homepage TTFB 467ms, payload 418KB, Content-Encoding: gzip

  Measured homepage TTFB, payload size, and compression

  report issue
• ✗security.txtrecommended0/1

  https://telnyx.com/.well-known/security.txt returned HTTP 404

  fix → Publish RFC 9116 /.well-known/security.txt with a Contact and a future Expires.

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• ✓OAuth authorization server metadatarecommended3/3

  Valid RFC 8414 metadata at https://telnyx.com/.well-known/oauth-authorization-server: issuer https://api.telnyx.com, PKCE S256, dynamic client registration at https://portal.telnyx.com/oauth/register

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• ✓OAuth protected resource metadatarecommended2/2

  Valid RFC 9728 metadata at https://telnyx.com/.well-known/oauth-protected-resource: resource https://telnyx.com, 2 authorization server(s) (https://telnyx.com, https://api.telnyx.com)

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• ✓Auth documentationrecommended2/2

  Auth documentation found at https://telnyx.com/auth.md (8136 chars, with code examples)

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ✓Pricing discoverablerequired5/5

  Pricing page found at https://telnyx.com/pricing/voice-ai-agents (via homepage link) with legible price signals ("$0.05 per minute. No fine prin").

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• ✓Machine-readable pricingrecommended5/5

  LLM extracted 4 numerically-priced plan(s) from https://telnyx.com/pricing/voice-ai-agents at confidence 1.00: AI Voice Agent Pricing USD 0.05/minute; PAY AS YOU GO USD 0/month; COMMITTED USD 500/month; ENTERPRISE USD 5000/month.

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✓x402 payment supportbonusrecommended2/2

  /.well-known/x402 returned HTTP 200 with a JSON payload (1321 bytes).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned llms.txt, agents.md, docs page (https://developers.telnyx.com/docs/overview); /.well-known/ap2 returned HTTP 404.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned llms.txt, agents.md, docs page (https://developers.telnyx.com/docs/overview); /.well-known/acp returned HTTP 404.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned llms.txt, agents.md, docs page (https://developers.telnyx.com/docs/overview).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• ✗MCP handshake & tools listrequired0/4

  MCP endpoint https://github.com/team-telnyx/ai failed handshake: Not a JSON-RPC endpoint

  fix → MCP endpoint https://github.com/team-telnyx/ai failed handshake: Not a JSON-RPC endpoint. Support streamable HTTP with protocol version negotiation; if auth-gated, return RFC 9728 metadata in WWW-Authenticate.

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✓NLWeb endpointemerging1/1

  GET /ask?query=hello returned HTTP 200 with a JSON response

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ✓Semantic HTML structurerequired3/3

  5/6 semantic signals present on the homepage (missing: text-to-markup ratio ≥ 0.10)

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 15559 chars of visible text without JavaScript

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✓Accessibility basicsrequired2/2

  Homepage accessibility: 4/5 checks passed — failing: labeled inputs (3/6 unlabeled)

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✓WebMCPemerging1/1

  WebMCP evidence on homepage: navigator.modelContext reference

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue