agenticweb.wiki

scaleway.com agentic web readiness

B Manifest validity: 50% (1/2 valid, 25 errors, 5 warnings) · Surface score 30 (coverage 20 + breadth 0 + conformance 10). 2 standards observed across 2 of 9 steps; 2 manifests present (+ robots.txt, security.txt), 25 errors, 5 warnings. Checked 2026-10-25 23:42:44 UTC via www.scaleway.com. This grades the agent-facing files published at scaleway.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/scaleway.com.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverRFC 972702 Identifynothing observed03 Permitnothing observed04 Readnothing observed05 ActAgent Skills06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
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)
/mcp/server-card
absent HTTP 404
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
valid
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog
errors
  • linkset[0].service-meta entry has no href
  • linkset[1].service-meta entry has no href
  • linkset[2].service-meta entry has no href
  • linkset[3].service-meta entry has no href
  • linkset[4].service-meta entry has no href
  • linkset[5].service-meta entry has no href
  • linkset[6].service-meta entry has no href
  • linkset[7].service-meta entry has no href
  • linkset[8].service-meta entry has no href
  • linkset[9].service-meta entry has no href
  • linkset[10].service-meta entry has no href
  • linkset[11].service-meta entry has no href
  • linkset[12].service-meta entry has no href
  • linkset[13].service-meta entry has no href
  • linkset[14].service-meta entry has no href
  • linkset[15].service-meta entry has no href
  • linkset[16].service-meta entry has no href
  • linkset[17].service-meta entry has no href
  • linkset[18].service-meta entry has no href
  • linkset[19].service-meta entry has no href
  • linkset[20].service-meta entry has no href
  • linkset[21].service-meta entry has no href
  • linkset[22].service-meta entry has no href
  • linkset[23].service-meta entry has no href
  • linkset[24].service-meta entry has no href
View valid /.well-known/api-catalog template for scaleway.com
{
  "linkset": [
    {
      "anchor": "https://scaleway.com/",
      "service-desc": [
        {
          "href": "https://scaleway.com/openapi.json",
          "type": "application/openapi+json"
        }
      ],
      "service-doc": [
        {
          "href": "https://scaleway.com/docs/api",
          "type": "text/html"
        }
      ],
      "service-meta": [
        {
          "href": "https://scaleway.com/AGENTS.md",
          "type": "text/markdown"
        }
      ]
    }
  ]
}
AI Crawler User-Agent Tokens in robots.txt
/robots.txt
no AI tokens
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial)
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
  • no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116)
/.well-known/security.txt
valid
  • Canonical: missing
auth.md
/auth.md
absent HTTP 404
Open Knowledge Format
/okf/index.md
absent HTTP 404

What an agent can call

Standards observed

Cheapest next steps

  1. llms.txt: one Markdown index file; the most widely read agent-facing file
    Generate starter /llms.txt for scaleway.com
    # Scaleway
    
    > Scaleway 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://scaleway.com/docs/getting-started): the first page to read
    - [API reference](https://scaleway.com/openapi.json): OpenAPI description
    
    ## Optional
    - [Changelog](https://scaleway.com/changelog): what changed, newest first
    
  2. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "scaleway.com"}))
  3. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for scaleway.com
    # Scaleway for agents
    
    Scaleway and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://scaleway.com/llms.txt
    - API description: https://scaleway.com/openapi.json
    - Discovery catalog: https://scaleway.com/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://scaleway.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@scaleway.com
    

Agent pre-flight & practical readiness

Preferred mode: openapi (fallback agent_skills). Read the published API description and call those operations. Scraping HTML skips the interface the site already gave you.

Fetch: GET https://www.scaleway.com/en/developers/api/instance/v2alpha1/schema.yml GET the API description and call the documented operations.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 296495 (~290 KB of head/script markup before main text), JSON-LD Corporation, ImageObject, ContactPoint, WebSite, WebPage, BreadcrumbList, ListItem.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 22/30, capabilities 13/35, conformance 10/15, total 65/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