Agent Readiness Score
gcore.com
41 — Developing. Agents can find parts of this site, but key capabilities are hard to reach.
HonestClaw measured how well gcore.com's site and APIs work for AI agents — across 9 dimensions and 45 automated checks.
Dimensions
Discoverability15.4/24
Content Accessibility14.9/24
Bot Access Control2/12
Protocol & Capability Discovery12.6/41
Authentication & Credentials9.8/19
Documentation Quality0.5/10
Structured Data I/O0/13
Observable State & Reliability5.5/15
Agent Safety & Trust8.1/11
Checks
Discoverability
Subdomain sweepsubdomain-sweepBoth an API-family and a docs-family subdomain are live (api.gcore.com, docs.gcore.com).Useful
robots.txtrobots-txtrobots.txt at https://gcore.com/robots.txt declares a sitemap. Declared sitemap https://gcore.com/sitemap.xml resolves as valid XML.Cross-verified
API catalogapi-catalogAPI Catalog found at https://gcore.com/.well-known/api-catalog (application/linkset+json).Detected
Canonical domaincanonical-domainRoot and www converge on gcore.com, with a matching canonical tag.Cross-verified
sitemap.xmlsitemap-xmlhttps://docs.gcore.com/sitemap.xml is a dated sitemap whose URLs include docs/pricing/api surfaces.Cross-verified
API existenceapi-existenceNo API endpoint found at common paths (only HTML pages or 404s).Not detected
API versioningapi-versioningThe API version lifecycle is documented at https://docs.gcore.com/api-reference/storage/storage/delete-s3-bucket-lifecycle, including deprecation/sunset. (source: docs)Cross-verified
Content Accessibility
Markdown twinmarkdown-twinA markdown twin is published at https://docs.gcore.com/home.md alongside the docs HTML surface (https://docs.gcore.com/).Parseable
Raw content extractabilityraw-content-extractabilitySome main content (0% ratio) is present in raw HTML, but navigation chrome or JS shells limit extractability.Parseable
Freshness signalsfreshness-signalsMultiple freshness signals present (Last-Modified header, ETag header, sitemap lastmod) with sitemap entries updated within 90 days.Cross-verified
Crawl-cost estimatecrawl-cost-estimateInformational — not scoredSitemap index declares 13 child sitemap(s) — crawl cost is not directly observable from the index alone.Parseable
llms.txtllms-txtA curated llms.txt index is published at https://gcore.com/llms.txt: 19 links across 2 sections.Cross-verified
llms-full.txtllms-full-txtA comprehensive llms-full.txt is published at https://gcore.com/llms-full.txt with 194,465 chars across 148 sections.Cross-verified
ai.txtai-txtNo ai.txt file found (HTML pages at .txt paths do not qualify).Not detected
Bot Access Control
AI bot rulesai-bot-rulesrobots.txt is readable but declares no AI-bot-specific rules.Not detected
Content signalscontent-signalsrobots.txt declares 3 recognized Content Signal(s) with a valid value: ai-train, search, ai-input.Cross-verified
RSL licensingrslrobots.txt is readable but declares no RSL License directive.Not detected
TDM reservationtdmrepNo TDMRep policy found at /.well-known/tdmrep.json.Not detected
Protocol & Capability Discovery
MCP descriptormcp-descriptorInformational — not scoredAn MCP server is described at https://docs.gcore.com/.well-known/mcp.json, but the description doesn't include a web address for the server.Parseable
MCP supportmcp-supportA first-party MCP support page exists at https://docs.gcore.com/developer-tools/mcp-server/connect-claude-code-to-gcore-mcp-server, but it does not identify a concrete HTTPS MCP endpoint or fully establish a company-operated service.Parseable
MCP Server Cardmcp-server-cardA fully described MCP Server Card is published at https://gcore.com/.well-known/mcp/server-card.json with identity, version, and protocol-versioned remote endpoints.Cross-verified
A2A Agent Carda2a-agent-cardAn A2A Agent Card is described at https://docs.gcore.com/.well-known/agent-card.json, but it is missing required fields (name, description, version, supportedInterfaces, or skills).Parseable
DNS-AIDdns-aidNo DNS-AID index found at _index._agents.gcore.com.Not detected
GraphQL surfacegraphql-surfaceNo GraphQL transport surface found at conventional paths (GET-only; no introspection issued).Not detected
.well-known indexwell-known-indexNo non-owned /.well-known/ descriptors found.Not detected
Auth discoveryauth-discoveryNo standardized authentication-discovery surface found. Blocked by robots.txt for a generic compliant agent (Disallow: /).Not detected
SDK availabilitysdk-availabilitySDK libraries page at https://docs.gcore.com/developer-tools/sdks/go: 2 GitHub repos, 1 registry link, 0 install commands (3 pointers).Cross-verified
Link headerslink-headersNo RFC 8288 Link headers found on any probed response.Not detected
OpenAPI specificationopenapi-specNo OpenAPI/Swagger specification found.Not detected
Rate limit documentationrate-limit-docsA rate-limit documentation page exists at https://docs.gcore.com/gclaw/limits, but it doesn't state a concrete limit alongside a rate-limit response header.Parseable
WebMCPwebmcpInformational — not scoredWebMCP browser probing is not yet available in this scanner release.Couldn't verify
Authentication & Credentials
Programmatic auth flowprogrammatic-auth-flowA programmatic auth flow is documented at https://docs.gcore.com/cloud/faas/authenticate-to-functions-with-api-keys, naming a non-interactive grant and a token endpoint. To reach the top level, it would need scopes and token expiry/refresh documented.Useful
Sandbox environmentsandbox-environmentNo sandbox or test environment documentation found at the standard docs locations an agent would check.Not detected
Auth documentationauth-documentationAuthentication is documented at https://docs.gcore.com/cloud/faas/authenticate-to-functions-with-api-keys with the specific detail an agent needs — the credential and how it is sent. To reach the top level, it would need to corroborate against another surface or document more than one complete method.Useful
Credential managementcredential-managementCredential management is documented at https://docs.gcore.com/api-reference/cloud/container-as-a-service/delete-api-key, covering how to rotate or revoke credentials. To reach the top level, it would need rotation, revocation, and scoping/expiry all documented.Useful
Documentation Quality
Changelog presencechangelog-presenceNo changelog or release notes found at the standard docs locations an agent would check.Not detected
API reference depthapi-reference-depthAPI reference content is mentioned at https://docs.gcore.com/api-reference/overview, but not on a dedicated reference page.Detected
Structured Data I/O
Structured data I/Ostructured-data-ioNo published structured-data contract found (no typed spec response schemas).Not detected
Machine-readable pricingmachine-readable-pricingNo machine-readable pricing endpoint found (HTML pricing pages do not qualify).Not detected
Data export APIdata-export-apiNo data export or bulk API documentation found at the standard docs locations an agent would check.Not detected
Observable State & Reliability
Status & health endpointsstatus-and-healthStatus page found at https://status.gcore.com/ (HTTP 200).Detected
Machine payments (x402/MPP)x402-or-mpp-supportInformational — not scoredNo 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. Blocked by robots.txt for a generic compliant agent (Disallow: /).Not detected
Webhook documentationwebhook-documentationA webhook documentation page exists at https://docs.gcore.com/streaming/extra-features/get-webhooks-from-the-streaming-platform, but it doesn't list specific event types with their payload shape.Parseable
Retry & idempotencyretry-and-idempotencyNo retry or idempotency documentation found at the standard docs locations an agent would check.Not detected
Error documentationerror-documentationErrors are documented at https://docs.gcore.com/cdn/troubleshooting/gcore-error-status-codes with specific codes or a documented response shape. To reach the top level, it would need recovery guidance and a machine-readable error format, or corroboration against the API spec.Useful
Agent Safety & Trust
security.txtsecurity-txtsecurity.txt at https://gcore.com/.well-known/security.txt publishes a Contact address.Useful
Org identity signalsorg-identityHomepage exposes legal name, address, support contact, and social profile links.Cross-verified
Metadata consistencymetadata-consistencyHomepage metadata (canonical, Open Graph, schema) is present and consistent.Cross-verified
Legal policy pageslegal-pagesNo terms, privacy, or data-use policy pages found at conventional paths.Not detected