telnyx.com agentic web readiness
A+ Manifest validity: 89% (8/9 valid, 1 error, 9 warnings) · Surface score 95 (coverage 70 + breadth 15 + conformance 10). 14 standards observed across 7 of 9 steps; 9 manifests present, 1 error, 9 warnings. Checked 2026-10-23 16:12:24 UTC. This grades the agent-facing files published at telnyx.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | absent HTTP 404 | |
AI Catalog well-known file/.well-known/ai-catalog.json | valid |
|
MCP Server Cards (SEP-2127)/.well-known/mcp/server-card.json | valid |
|
Agent2Agent Protocol/.well-known/agent-card.json | valid |
|
llms.txt/llms.txt | valid | |
AGENTS.md/AGENTS.md | valid | |
Agent Skills/.well-known/agent-skills/index.json | errors |
|
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs/.well-known/api-catalog | valid | |
AI Crawler User-Agent Tokens in robots.txt/robots.txt | valid |
|
security.txt (RFC 9116)/.well-known/security.txt | absent HTTP 404 | |
auth.md/auth.md | valid | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- MCP endpoint
https://api.telnyx.com/v2/mcp(streamable-http) — from/.well-known/mcp.json - MCP endpoint
https://api.telnyx.com/v2/mcp(streamable-http), tools: list_api_endpoints, get_api_endpoint_schema, invoke_api_endpoint, open_number_intelligence, open_usage_cost_explorer, open_voice_monitor — from/.well-known/mcp/server-card.json - MCP endpoint
https://api.telnyx.com/v2/mcp(streamable-http) — from/ai/mcp-server-card.json - A2A agent Telnyx AI Infrastructure Agent at
https://telnyx.com, skills: Evaluate Infrastructure, Compare with Competitor, Get Benchmarks, Get Pricing, List Capabilities - API description
https://telnyx.com/.well-known/api-catalog(application/linkset+json) - API description
https://telnyx.com/openapi.json(application/json) - API description
https://telnyx.com/openapi.json(application/json) - API description
https://developers.telnyx.com/docs(text/html) - API description
https://github.com/coinbase/x402(text/html) - API description
https://telnyx.com/.well-known/x402(application/json) - API description
https://telnyx.com/discovery/resources(application/json) - llms.txt: Telnyx, 83 links, llms-full.txt present
- robots.txt AI policy: blocks Bytespider, Diffbot; unlisted crawlers partial
- OAuth protected resource
https://telnyx.com, authorization servers: https://telnyx.com, https://api.telnyx.com
Standards observed
- Agent2Agent Protocol https://telnyx.com/.well-known/agent-card.json
- Universal Commerce Protocol https://telnyx.com/.well-known/ucp
- llms.txt https://telnyx.com/llms.txt
- AGENTS.md https://telnyx.com/AGENTS.md
- Content Signals Policy https://telnyx.com/robots.txt
- Web Bot Auth HTTP Message Signatures https://telnyx.com/.well-known/http-message-signatures-directory
- AI Catalog well-known file https://telnyx.com/.well-known/ai-catalog.json
- api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://telnyx.com/.well-known/api-catalog
- auth.md https://telnyx.com/auth.md
- AI Crawler User-Agent Tokens in robots.txt https://telnyx.com/robots.txt
- OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://telnyx.com/.well-known/oauth-protected-resource
- Markdown for Agents https://telnyx.com/
- MCP Server Cards (SEP-2127)
- Model Context Protocol
Cheapest next steps
- Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
- security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
Agent pre-flight & practical readiness
Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://api.telnyx.com/v2/mcp first. Do not scrape the HTML when a tool can answer.
Fetch: POST https://api.telnyx.com/v2/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.
Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.
AI crawler posture: open_to_all · Assistant access: OpenAI partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.
Readiness subscores: reach 20/20, readability 30/30, capabilities 35/35, conformance 10/15, total 95/100, grade A+.
How the grade is made
+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.
JSON · Markdown · probe rules