agenticweb.wiki

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.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/telnyx.com.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 972702 IdentifyWebBotAuth03 PermitContent Signals Policy, auth.md, AI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, AGENTS.md, Markdown for Agents05 Act06 CoordinateA2A07 PayUCP08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json
valid
  • no entry has representativeQueries; ARD registries use 2-5 example queries to index entries
MCP Server Cards (SEP-2127)
/.well-known/mcp/server-card.json
valid
  • Content-Type is application/json; charset=UTF-8; SEP-2127 says serve application/mcp-server-card+json
  • pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[]
  • $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key)
  • legacy /.well-known/mcp.json is still live and may shadow /.well-known/mcp/server-card.json in older scanners
Agent2Agent Protocol
/.well-known/agent-card.json
valid
  • supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape
llms.txt
/llms.txt
valid
AGENTS.md
/AGENTS.md
valid
Agent Skills
/.well-known/agent-skills/index.json
errors
  • body is not valid JSON
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
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
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

Standards observed

Cheapest next steps

  1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
  2. 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