gcore.com agentic web readiness
A+ Manifest validity: 100% (2/2 valid, 1 security.txt error, 5 warnings) · Surface score 64 (coverage 40 + breadth 9 + conformance 15). 5 standards observed across 4 of 9 steps; 2 manifests present (+ robots.txt, security.txt), 1 security.txt error, 5 warnings. Checked 2026-10-25 03:13:13 UTC. This grades the agent-facing files published at gcore.com, not the organisation's products.
Coverage by step
Manifests
| Manifest | Result | Findings |
|---|---|---|
Agentic Resource Discovery/.well-known/ard.json | absent HTTP 404 | |
AI Catalog well-known file/.well-known/ai-catalog.json | absent HTTP 404 | |
MCP Server Cards (SEP-2127)/.well-known/mcp/server-card.json | valid |
|
Agent2Agent Protocol/.well-known/agent-card.json | absent HTTP 404 | |
llms.txt/llms.txt | absent HTTP 404 | |
AGENTS.md/AGENTS.md | absent HTTP 404 | |
Agent Skills/.well-known/agent-skills/index.json | absent HTTP 404 | |
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 | no AI tokens |
|
security.txt (RFC 9116)/.well-known/security.txt | errors |
View valid |
auth.md/auth.md | absent HTTP 404 | |
Open Knowledge Format/okf/index.md | absent HTTP 404 |
What an agent can call
- MCP endpoint
https://gcore.com/mcp(streamable-http) — from/.well-known/mcp/server-card.json - MCP endpoint
https://gcore.com/mcp(streamable-http) — from/.well-known/mcp-server-card - API description
https://api.gcore.com/cdn/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/cdn(text/html) - API description
https://api.gcore.com/cloud/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/cloud(text/html) - API description
https://api.gcore.com/dns/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/dns(text/html) - API description
https://api.gcore.com/fastedge/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/fastedge(text/html) - API description
https://api.gcore.com/iam/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/iam(text/html) - API description
https://api.gcore.com/security/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/security(text/html) - API description
https://api.gcore.com/storage/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/storage(text/html) - API description
https://api.gcore.com/streaming/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/streaming(text/html) - API description
https://api.gcore.com/waap/docs/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/waap(text/html) - API description
https://api.gcore.com/billing/docs/reseller/openapi.yaml(application/yaml) - API description
https://gcore.com/docs/api-reference/billing(text/html) - robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)
Standards observed
- Content Signals Policy https://gcore.com/robots.txt
- api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://gcore.com/.well-known/api-catalog
- Markdown for Agents https://gcore.com/
- MCP Server Cards (SEP-2127)
- Model Context Protocol
Cheapest next steps
- llms.txt: one Markdown index file; the most widely read agent-facing file
Generate starter
/llms.txtfor gcore.com# Gcore > Gcore and what it offers to agents Short notes an agent should know before using the site: what it is for, who runs it, how to cite it. ## Docs - [Getting started](https://gcore.com/docs/getting-started): the first page to read - [API reference](https://gcore.com/openapi.json): OpenAPI description ## Optional - [Changelog](https://gcore.com/changelog): what changed, newest first
- Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
- AGENTS.md: instructions for coding agents working on or with the site
Generate starter
/AGENTS.mdfor gcore.com# Gcore for agents Gcore and what it offers to agents ## Read the data, not the HTML - Index: https://gcore.com/llms.txt - API description: https://gcore.com/openapi.json - Discovery catalog: https://gcore.com/.well-known/ard.json ## Calling - MCP server (Streamable HTTP): https://gcore.com/mcp - Rate limits and authentication: describe them here ## Conventions - How to cite or attribute content - What not to do (no scraping of /account/, no automated sign-ups, etc.) Contact: security@gcore.com
Agent pre-flight & practical readiness
Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://gcore.com/mcp first. Do not scrape the HTML when a tool can answer.
Fetch: POST https://gcore.com/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 allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.
Readiness subscores: reach 20/20, readability 28/30, capabilities 22/35, conformance 15/15, total 85/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