HonestClaw · What is Agent Readiness? · How we score
Limited. Agents will struggle to discover or use this site without human help.
HonestClaw measured how well metaworks.ai's site and APIs work for AI agents — across 9 dimensions and 45 automated checks. Score: 19/100 (Limited).
Scanned · scanner v1.36.0 · 10 of 45 checks conclusive.
5 of 8 scored areas have measured gaps. Documentation & meaning is furthest along; Permissions & policy has the largest measured point gap.
4 additional observations provide context and do not affect the score.
Reachable entry points
Could not conclusively sweep conventional subdomains (unreachable or transient).
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
Could not conclusively check for a sitemap (unreachable, rate-limited, or behind auth).
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.
Could not conclusively check for an API Catalog (endpoint unreachable, rate-limited, or behind auth).
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 DNS-AID index found at _index._agents.metaworks.ai.
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 public evidence URL recorded for this check
Could not conclusively check for Link headers (endpoints unreachable, rate-limited, or behind auth).
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
Could not conclusively check /.well-known/ descriptors (unreachable, rate-limited, or behind auth).
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
The origin https://metaworks.ai/ is reachable, but root/www do not converge on one host.
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.
Content available to the tested client
The homepage is a JS-rendered shell with no meaningful content in the initial HTML — content is behind JavaScript.
These are recorded points before the total is normalized to 100.
Public pages; distinguish HTTP and browser clients
Critical content available in the response is a direct prerequisite for the tested client. An extraction ratio alone does not prove that the needed facts were captured.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Equivalent readable representations
Could not conclusively check for markdown twins (unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Only representations the site offers; all sites can satisfy readable-content outcome with HTML
Headers, routes and frontmatter support one readable representation. Plain HTML must be able to receive full content-access credit.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Retrieval cost
No crawl-cost signals found (no sitemap URL inventory or Crawl-delay directive).
Useful context, outside the readiness score. Adoption, payment support and retrieval cost are not readiness quality by themselves.
Measured retrieval path
Tokens, bytes and elapsed time explain retrieval cost and tradeoffs. They are context and do not affect the readiness score.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Clear and consistent publisher policy
robots.txt is readable but declares no AI-bot-specific rules.
These are recorded points before the total is normalized to 100.
ChatGPT-User, Claude-User and Perplexity-User access declarations
A small legibility contribution for explicit user-directed access rules, including wildcard defaults. Permission and denial earn equal legibility; training-only groups add no points.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
robots.txt is readable but declares no RSL License directive.
These are recorded points before the total is normalized to 100.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Could not conclusively check for an ai.txt file (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
robots.txt is readable but declares no Content-Signal line.
These are recorded points before the total is normalized to 100.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Could not conclusively check for a TDMRep policy (unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Publisher-declared policy; no obligation to permit training, indexing or licensing
Published licensing, indexing and training preferences remain inspectable without separate readiness points. User-directed policy legibility is measured once; observed public HTTP access is separate.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
robots.txt at https://metaworks.ai/robots.txt is a valid robots file (no Sitemap: declared).
These are recorded points before the total is normalized to 100.
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.
Usable documentation entry and references
Could not conclusively check for an llms.txt file (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for an llms-full.txt file (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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. This check has no external governing spec; its weight is product judgment.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Usable API reference and examples
Could not conclusively check for API reference documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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
Could not conclusively check for a machine-readable pricing endpoint (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Document freshness evidence
Freshness signals present: Last-Modified header, ETag header.
These are recorded points before the total is normalized to 100.
Resources whose currency can be assessed
A timestamp or ETag supports freshness provenance; it does not by itself prove factual accuracy or current behavior.
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
Could not conclusively check for a structured-data contract (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for data export or bulk API documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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
Could not conclusively check for an API endpoint (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for an OpenAPI/Swagger specification (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for SDK or client library documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively discover or check first-party MCP support documentation and likely endpoints.
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for GraphQL (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Emerging interface declarations
Could not conclusively check for an A2A Agent Card (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Could not conclusively check for an MCP Server Card (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
WebMCP browser probing is not yet available in this scanner release.
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
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
Could not conclusively check for an MCP descriptor (locations unreachable, rate-limited, or behind auth).
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
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 machine-payment signal observed (no HTTP 402, no payment-required response header, and no /.well-known/x402.json manifest). Payment support cannot be ruled out from an unauthenticated probe.
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
Could not conclusively check for an auth-discovery surface (unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
No public evidence URL recorded for this check
Could not conclusively check for programmatic authentication documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for authentication documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for credential management documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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
Could not conclusively check for sandbox or test environment documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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
Could not conclusively check for rate limit documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Change and compatibility information
Could not conclusively check for API versioning (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for a changelog or release notes (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Observable outcomes and recovery
Could not conclusively check for webhook or event documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for error documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for retry or idempotency documentation (endpoints unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Could not conclusively check for health or status endpoints (unreachable, rate-limited, or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
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.
Attributable identity and consistent claims
Could not conclusively check for security.txt (unreachable or behind auth).
Unverified points are excluded from the score denominator and reduce observed coverage.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Homepage exposes one org-identity signal (legal_name).
These are recorded points before the total is normalized to 100.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.
Could not conclusively check legal policy pages.
Unverified points are excluded from the score denominator and reduce observed coverage.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
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
Homepage metadata (canonical, Open Graph, schema) is present and consistent.
These are recorded points before the total is normalized to 100.
Public company/service identity; MCP identity only for MCP
These establish provenance, disclosure routes and consistency. They cannot certify prompt-injection resistance or safe transactions.
These sources inform the check. They do not validate our exact point weights.
Current guidance · 2026-10-15. Recorded scores are unchanged.