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 coreweave.com's site and APIs work for AI agents — across 9 dimensions and 45 automated checks. Score: 26/100 (Limited).
Scanned · scanner v1.36.0 · 45 of 45 checks conclusive.
All 8 scored areas have measured gaps. Access & rendering is furthest along; Interfaces & data has the largest measured point gap.
4 additional observations provide context and do not affect the score.
Reachable entry points
No DNS-AID index found at _index._agents.coreweave.com.
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
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 non-owned /.well-known/ descriptors found.
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
No RFC 8288 Link headers found on any probed response.
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
An agent-relevant subdomain is live and serves its expected content kind (docs.coreweave.com).
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
https://coreweave.com/sitemap.xml is a valid sitemap (727 location(s)), but without lastmod or non-homepage URLs.
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.
The origin https://coreweave.com/ 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
Moderate-to-strong main content (62% of visible text) is extractable from raw HTML on the homepage.
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
A markdown twin is published at https://docs.coreweave.com/index.md alongside the docs HTML surface (https://docs.coreweave.com/).
These are recorded points before the total is normalized to 100.
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
A manageable sitemap (727 page URLs) helps agents estimate crawl cost.
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.
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.
No TDMRep policy found at /.well-known/tdmrep.json.
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.
No ai.txt file found (HTML pages at .txt paths do not qualify).
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.
robots.txt at https://coreweave.com/robots.txt declares a sitemap. Declared sitemap https://wf.coreweave.com/sitemap.xml resolves as valid XML.
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 API reference and examples
An API reference page exists at https://docs.coreweave.com/products/networking/hpc-interconnect/nccl-configuration-reference, but it doesn't show parameters with example requests and responses.
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.
Usable documentation entry and references
No llms-full.txt file found (HTML pages at .txt paths do not qualify).
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. This check has no external governing spec; its weight is product judgment.
Current guidance · 2026-10-15. Recorded scores are unchanged.
An llms.txt index is published at https://docs.coreweave.com/llms.txt with 824 links under 1 section(s). To reach the top level, it would need a fuller index (more links across multiple sections) or an llms-full.txt.
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.
Document freshness evidence
A single freshness signal is present (Last-Modified 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.
Machine-readable facts
A response at https://coreweave.com/pricing.json looks JSON-like but did not parse as JSON.
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.
Complete and usable operation contracts
No published structured-data contract found (no typed spec response schemas).
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.
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.
Usable supported interface
No OpenAPI/Swagger specification found.
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.
No SDK or client library documentation found.
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.
A conventional API path at https://api.intellimize.co/ returned an auth challenge (HTTP 403). (source: live)
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.
A first-party MCP support page exists at https://docs.coreweave.com/observability/mission-control-mcp, but it does not identify a concrete HTTPS MCP endpoint or fully establish a company-operated service.
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.
No GraphQL transport surface found at conventional paths (GET-only; no introspection issued).
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.
Emerging interface declarations
No A2A Agent Card found at the standard well-known locations.
These are recorded points before the total is normalized to 100.
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.
A file exists at https://docs.coreweave.com/.well-known/mcp/server-card.json, but it doesn't contain the fields that describe an MCP Server Card.
These are recorded points before the total is normalized to 100.
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
An MCP server is described at https://docs.coreweave.com/.well-known/mcp.json, but the description doesn't include a web address for the server.
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
No standardized authentication-discovery surface found. Blocked by robots.txt for a generic compliant agent (Disallow: /).
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.
No public evidence URL recorded for this check
No credential management documentation found at the standard docs locations an agent would check.
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.
An authentication page exists at https://docs.coreweave.com/changelog/release-notes/unmanaged-auth, but it doesn't document a programmatic grant with a token endpoint.
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.
An authentication documentation page exists at https://docs.coreweave.com/changelog/release-notes/unmanaged-auth, but it doesn't name a specific method or show how a request is authenticated.
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 sandbox/testing page exists at https://docs.coreweave.com/products/sandboxes/client/guides/sandbox-configuration, but it doesn't show how to obtain test credentials or a test base URL.
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.
Observable outcomes and recovery
No error 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.
A webhook documentation page exists at https://docs.coreweave.com/platform/coreweave-alerts/webhooks, but it doesn't list specific event types with their payload shape.
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.
Status page found at https://status.coreweave.com/ (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.
Actionable limits
A rate-limit documentation page exists at https://docs.coreweave.com/support/cks/tags/quotas-rate-limits, but it doesn't state a concrete limit alongside a rate-limit response header.
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.
Change and compatibility information
The API version lifecycle is documented at https://docs.coreweave.com/platform/terraform/resources/object_storage_bucket_lifecycle_configuration, including deprecation/sunset. (source: docs)
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.coreweave.com/changelog 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.
Attributable identity and consistent claims
No security.txt found at /.well-known/security.txt or /security.txt.
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.
No terms, privacy, or data-use policy pages found at conventional paths.
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.
No public evidence URL recorded for this check
Homepage exposes three org-identity signal types (legal_name, address, social).
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.
One metadata consistency warning: canonical_mismatch.
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.