HonestClaw · What is Agent Readiness? · How we score
Developing. Agents can find parts of this site, but key capabilities are hard to reach.
HonestClaw measured how well x.com's site and APIs work for AI agents — across 9 dimensions and 27 automated checks. Score: 43/100 (Developing).
Scanned · scanner v1.3.0 · 21 of 27 checks conclusive.
5 of 6 scored areas have measured gaps. Documentation & meaning is furthest along; Reliability & recovery has the largest measured point gap.
1 additional observation provides context and does not affect the score.
Reachable entry points
No RFC 9727 API Catalog found at /.well-known/api-catalog.
These are recorded points before the total is normalized to 100.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No live subdomains matched this check.
Unverified points are excluded from the score denominator and reduce observed coverage.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
No live subdomains matched this check.
Unverified points are excluded from the score denominator and reduce observed coverage.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
No live subdomains matched this check.
Unverified points are excluded from the score denominator and reduce observed coverage.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
No live subdomains matched this check.
Unverified points are excluded from the score denominator and reduce observed coverage.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
No live subdomains matched this check.
Unverified points are excluded from the score denominator and reduce observed coverage.
Public pages; interfaces when present
Clear entry points help agents find the intended site or interface. Multiple hostnames or directory formats may describe the same destination.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
Clear and consistent publisher policy
No live subdomains matched this check.
Unverified points are excluded from the score denominator and reduce observed coverage.
Published policy for the relevant use: indexing, training or user retrieval
Different policy syntaxes and business permissions are not independent readiness capabilities. Blocking training should not imply that an agent cannot use a public API.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No public evidence URL recorded for this check
Usable API reference and examples
API reference content is mentioned at https://docs.x.com/overview, but not on a dedicated reference page.
These are recorded points before the total is normalized to 100.
A documented API or tool interface
Reference depth and valid fenced examples contribute to the same documentation outcome. Parsing an example is weaker than executing it successfully.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Machine-readable facts
No machine-readable pricing endpoint found (HTML pricing pages do not qualify).
These are recorded points before the total is normalized to 100.
Facts relevant to the product; pricing only when there is a price to disclose
Structured facts can help agents interpret a page. Markup volume and the number of schema types alone do not establish accuracy, consistency or task success. This check has no external governing spec; its weight is product judgment.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable documentation entry and references
A curated llms.txt index is published at https://docs.x.com/llms.txt: 23 links across 4 sections.
These are recorded points before the total is normalized to 100.
Public documentation; llms files optional
An index, full text and modular files offer different routes to documentation. Useful content and working references matter more than the number of formats.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Complete and usable operation contracts
No data export or bulk API documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
The spec at https://docs.x.com/openapi.json declares typed response schemas as a rule (99% of operations) — no structured error envelope. (source: spec)
These are recorded points before the total is normalized to 100.
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable supported interface
A real API surface is declared at https://docs.x.com/openapi.json: the spec lists servers and paths. (source: spec)
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
SDK libraries page at https://developer.x.com/docs/sdks: 0 GitHub repos, 0 registry links, 0 install commands (0 pointers).
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Valid OpenAPI 3.0.0 spec at https://docs.x.com/openapi.json: 165 operations, 446 schemas, 100% response coverage, servers declared.
These are recorded points before the total is normalized to 100.
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
MCP discovery evidence
An MCP server is described at https://docs.x.com/.well-known/mcp.json, but the description doesn't include a web address for the server.
These are recorded points before the total is normalized to 100.
MCP surface
An MCP descriptor helps clients locate a service. This additional observation does not earn separate points for evidence already represented by the scored MCP check.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Payment capabilities
No HTTP 402 response or machine payment protocol headers detected.
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Payment-enabled business model
Payment support describes what the business offers. It must not make a research publication or free public service appear less ready.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable least-privilege authentication
Programmatic authentication is mentioned at https://docs.x.com/overview, but not on a page dedicated to documenting it.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Credential management is mentioned at https://docs.x.com/overview, but not on a page dedicated to documenting it.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Authentication is fully documented at https://docs.x.com/overview, naming complete method(s) and how they are sent, corroborated across surfaces or covering multiple methods.
These are recorded points before the total is normalized to 100.
Protected operations; anonymous access is valid when intended
Discovery, documentation and credential lifecycle jointly support a usable authorization flow. A public read-only service need not require OAuth.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Safe integration environment
A test environment is mentioned at https://docs.x.com/overview, but not on a page dedicated to documenting it.
These are recorded points before the total is normalized to 100.
Operations whose side effects or onboarding require a safe test environment
A sandbox helps validate consequential integrations; it is not necessary for every public content site or read-only API.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Actionable limits
Rate limiting is mentioned at https://docs.x.com/overview, but not on a page dedicated to documenting it.
These are recorded points before the total is normalized to 100.
An interface with quotas or throttling
Published limits and response headers help clients pace requests and recover from throttling. They describe related aspects of the same service constraint.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Observable outcomes and recovery
Webhooks are mentioned at https://docs.x.com/overview, but not on a page dedicated to documenting them.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
No retry or idempotency documentation found at the standard docs locations an agent would check.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Health/status endpoint found at https://developer.x.com/api/health (HTTP 200).
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Errors are fully documented at https://docs.x.com/overview, enumerating codes with a machine-readable format and recovery guidance.
These are recorded points before the total is normalized to 100.
Detected interface; idempotency for repeatable writes, webhooks only for event-driven workflows
Observable state and actionable errors help recovery. A status page or error schema does not prove successful repair.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Change and compatibility information
The API version is declared in the spec (info.version) at https://docs.x.com/openapi.json. (source: spec)
These are recorded points before the total is normalized to 100.
Maintained interface or evolving product
Version identifiers and change records help clients manage compatibility as an interface evolves.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
A changelog is published at https://docs.x.com/overview with multiple recent dated entries, indicating it is actively maintained.
These are recorded points before the total is normalized to 100.
Maintained interface or evolving product
Version identifiers and change records help clients manage compatibility as an interface evolves.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.