rubric v0.9.1 · scanned
render.com
Verdict
L4 · Usable by agents
Web standards 95.2 · Agent conventions 80.3
Usable by agents: Yes: documented API (OpenAPI)
Held at L4: L5 Agent-native needs status-page (not measured) to pass or be partial. Read the level rules
Readable: HTTP 200 at https://render.com/, 1,406 words in the HTML. 4 to fix, 2 optional choices, 2 agent conventions not used, 1 agent convention to correct, and 26 out of scope.
How this was measured
Measured once, from 1 vantage point, at https://render.com. The scanner reads the homepage and at most 130 URLs, runs no JavaScript, and calls no API or MCP tool it finds.
Not a ranking prediction, not AI visibility, not a certification.
We sell no consulting. No ads, no sponsored listings, and we never contact the sites that are scanned. Scanning is free today.
Defects 4
Web-standards checks that fail or are partial, and optional files served with an error. Each lists what fixing it is worth.
-
Partial worth 2.6 points Adopted Title and description — Title "Render | The cloud for builders" (31 characters) and a description of 140 characters. The first H1 "Your fastest path to production for Y o u r f a s t e s t p a t h t o…" shares 0 of 2 words with the title, brand names aside. Microsoft's guide to AI search answers (October 2025) asks for an H1 that matches the title or closely reflects it.
Observation
title (31 characters): Render | The cloud for builders · description (140 characters): Deploy and scale any app or agent from your first user to your billionth. Build faster on intuitive cloud infrastructure for the modern web. · first H1: Your fastest path to production for Y o u r f a s t e s t p a t h t o p r o d u c t i o n f o r any workload any workload a n y w o r k l o…
The title and the description say what a page is about. Google uses them for the title link and the snippet.
Sources: Google: title links (Google Search Central), Google: snippets (Google Search Central), Bing Webmaster Guidelines, §13: titles, descriptions and headings (Microsoft Bing), Microsoft: optimizing content for AI search answers (Microsoft Advertising, 2025-10)
- Read today by
- Google, Bing, and link previews.
- Google Search
- Direct
Note
Give the first H1 and the title the same subject. Either can change, and brand names do not count.
Verify with
HOMEPAGE=https://render.com/ curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | perl -0777 -CS -ne 'if (m{<title[^>]*>(.*?)</title>}si) { my $t=$1; $t=~s/\s+/ /g; $t=~s/^ | $//g; print "title (", length($t), "): $t\n" } else { print "title: none\n" } if (m{<meta\b[^>]*\bname=["\x27]?description["\x27]?[^>]*>}i) { my ($c)=$& =~ /\bcontent=["\x27]([^"\x27]*)/i; $c //= ""; print "description (", length($c), "): $c\n" } else { print "description: none\n" }' -
Partial worth 0.4 points Adopted Structured contact information — Homepage markup declares 1 organization-type node with 0 contact details, while the page itself carries 0 plain-text contact signals. Organization "Render": no contact detail.
A ContactPoint in the Organization markup makes the contact route machine-readable.
Sources: Google: Organization structured data (Google Search Central)
- Read today by
- Google lists contactPoint as a recommended Organization property.
- Google Search
- Indirect
Fix
{ "contactPoint": { "@type": "ContactPoint", "contactType": "<choose: what this contact is for, such as customer service>", "email": "<choose: email address>" } }Verify with
HOMEPAGE=https://render.com/ curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | tr -d '\n' | grep -oE '"contactPoint":|"(contactType|email|telephone)":"[^"]*"' | sort -u -
Partial worth 0.4 points Adopted Responsive markup — viewport content "width=device-width, initial-scale=1, maximum-scale=1" sets maximum-scale=1, which stops a reader from zooming. WCAG 1.4.4 asks that text can be enlarged to 200%.
Observation
viewport meta: width=device-width, initial-scale=1, maximum-scale=1
Google indexes the smartphone rendering of a page. A viewport that blocks zoom fails WCAG 1.4.4.
Sources: Google: mobile-first indexing (Google Search Central), WCAG 2.2, 1.4.4 (W3C)
- Read today by
- Browsers; Google's smartphone crawler renders the page with it. No Google feature reads the tag itself.
- Google Search
- Indirect
Fix
<meta name="viewport" content="width=device-width, initial-scale=1">Note
Never set
user-scalable=noor amaximum-scalebelow 2: they keep a reader from enlarging text to 200%.Verify with
HOMEPAGE=https://render.com/ curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | perl -0777 -ne 'print m{<meta\b[^>]*\bname=["\x27]?viewport["\x27]?[^>]*>}i ? "viewport: $&\n" : "viewport: none\n"' -
optional file, served with an error 0 points Experimental Sandbox or test environment documented — A sandbox is referenced at /docs, but it names no non-production base URL, so an agent cannot integrate safely.
A documented sandbox lets a client test calls without touching production data.
Sources: OpenAPI 3.1 (servers) (OpenAPI Initiative)
- Read today by
- API integrators.
- Google Search
- None
Note
Merge the two servers entries into the OpenAPI document you already publish rather than replacing it: OpenAPI standardises servers but says nothing about test keys, sandbox tenants, or data resets, so those can only be stated as info.description prose. A sandbox on its own host is reported as declared, not observed, because this scan requests no other host; one on the scanned host has to answer a request without credentials. The declaring source also has to say what the sandbox excludes - no live data, test data only, resets nightly - because that statement is part of what the check reads.
Verify with
ORIGIN=https://render.com { curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: application/json, application/linkset+json;q=0.9, */*;q=0.5' "$ORIGIN/openapi.json" | jq -r '.servers[]?.url' 2>/dev/null | grep -iE 'sandbox|staging|test'; curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$ORIGIN/docs/sandbox" | grep -oiE 'https://[a-z0-9.-]*(sandbox|staging)[a-z0-9./_-]*'; } | sort -u | while read -r u; do printf '%s -> ' "$u"; curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' -o /dev/null -w '%{http_code} %{content_type}\n' "$u"; done
Optional choices 3
Show 3 Hide 3 in Optional choices
Decisions only you can make. None earns points or holds a level.
-
Not used 0 points Adopted Snippet and AI grounding directives — Not used: the homepage has no noarchive, nocache, nosnippet or max-snippet:0 directive, and no data-nosnippet attribute, so Bing applies none of the limits they set on snippets and Copilot answers.
Observation
<meta name="robots" content="index, follow"> · data-nosnippet: 0 elements
noarchive, nocache, nosnippet and data-nosnippet limit how Bing shows a page and how Copilot uses it. Each is the site owner's choice.
Sources: Bing Webmaster Guidelines, §10: NOARCHIVE, NOCACHE and NOSNIPPET (Microsoft Bing), Bing: robots meta tags and attributes that Bing supports (Microsoft Bing), Google: robots meta tag specifications (Google Search Central)
- Read today by
- Bing reads all five, and Copilot follows noarchive and nocache. Google reads nosnippet, max-snippet and data-nosnippet.
- Google Search
- Direct
Note
Each directive is your choice. noarchive keeps the page out of Copilot answers, nocache lets Copilot use only the URL, the title and the snippet, and nosnippet or data-nosnippet may limit the quality of what Copilot cites.
Verify with
HOMEPAGE=https://render.com/ curl -sSL -o /dev/null -D - -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | tr -d '\r' | grep -i '^x-robots-tag:' curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | perl -0777 -ne 'my $h = /^(.*?)<\/head>/si ? $1 : substr($_, 0, 8192); while ($h =~ m{<meta\b[^>]*>}gi) { my $t = $&; next unless $t =~ /\bname=["\x27]?(robots|bingbot|googlebot)["\x27]?[\s>\/]/i; my $n = lc $1; my ($c) = $t =~ /\bcontent=["\x27]([^"\x27]*)/i; print "meta $n: ", ($c // ""), "\n" } my $body = $_; $body =~ s{<!--.*?-->}{}gs; $body =~ s{<(script|style|template|title|textarea|noscript)\b[^>]*>.*?</\1\s*>}{}gsi; my $n = 0; while ($body =~ m{<[a-z][a-z0-9-]*\b((?:[^>"\x27]|"[^"]*"|\x27[^\x27]*\x27)*)>}gi) { (my $t = $1) =~ s{"[^"]*"|\x27[^\x27]*\x27}{}g; $n++ if $t =~ /(?:^|\s)data-nosnippet(?=[\s=\/]|$)/i } print "data-nosnippet: $n\n"' -
Not used 0 points Adopted Breadcrumb markup on an inner page — The inner page /docs/web-services has no BreadcrumbList in its JSON-LD, Microdata, or RDFa.
Observation
https://render.com/docs/web-services · HTTP 200 · text/html · BreadcrumbList: 0
BreadcrumbList states where an inner page sits in the site. A homepage has no trail.
Sources: Google: breadcrumb (Google Search Central), Google blog (Google Search Central, 2025-01)
- Read today by
- Google shows breadcrumbs in desktop results.
- Google Search
- Direct
Fix
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Render", "item": "https://render.com/" }, { "@type": "ListItem", "position": 2, "name": "<choose: name of this section>", "item": "https://render.com/docs" }, { "@type": "ListItem", "position": 3, "name": "Web Services – Render Docs", "item": "https://render.com/docs/web-services" } ] } </script>Note
Replace each <choose: …> with the name or the URL the site uses for that section, and drop a level that has no page. Show the same trail as links on the page.
Verify with
PAGE=https://render.com/docs/web-services curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' -o /tmp/aws-page.html "$PAGE"; perl -0777 -ne 'while (m{<script[^>]*application/ld\+json[^>]*>(.*?)</script>}gsi) { print "$1\n" }' /tmp/aws-page.html | jq -r '.. | objects | select((.["@type"]? | if type == "array" then .[] else . end) == "BreadcrumbList") | .itemListElement[] | [(.position | tostring), (.name // .item.name? // "NO NAME"), ((.item["@id"]? // .item) // "NO URL" | tostring)] | @tsv'; grep -c 'schema.org/BreadcrumbList' /tmp/aws-page.html -
Present 0 points Adopted security.txt (RFC 9116) — security.txt at /.well-known/security.txt declares 1 Contact and an Expires 2027-10-03T00:00:00.000Z in the future. Not scored: its Policy URL is on hackerone.com, which this scan does not request.
Observation
Contact: mailto:security@render.com Expires: 2027-10-03T00:00:00.000Z Preferred-Languages: en Canonical: https://render.com/.well-known/security.txt Policy: https://hackerone.com/render
security.txt tells a researcher where to report a vulnerability (RFC 9116). It has no effect on search.
Sources: RFC 9116 (IETF, 2022-04)
- Read today by
- Security researchers and disclosure tools.
- Google Search
- None
Agent conventions 10
Show 10 Hide 10 in Agent conventions
The scored ones make up 30% of the score, and the unscored ones earn no points. None has an effect on Google Search today. Each scored row not in use lists what using it is worth.
-
Not used worth 3.7 points Adopted Structured errors for JSON requests — Not used: /aws-probe-65b4253a8c74, asked for JSON, answered HTTP 404 with an HTML page, not a JSON error.
Observation
HTTP 404 · text/html · first 16 KB read
An agent that asks for JSON and gets an HTML error page has to read a page meant for people. RFC 9457 defines a JSON error format.
Sources: RFC 9457: Problem Details for HTTP APIs (IETF, 2023-07), RFC 9110, 12.5.1: Accept (IETF)
- Read today by
- API clients and agents that send Accept: application/json. No search engine reads it.
- Google Search
- None
Fix
{ "type": "about:blank", "title": "Not Found", "status": 404, "detail": "Nothing is published at this address." }Note
Send this with Content-Type: application/problem+json and the status 404 when a request for a missing path asks for JSON. Browsers can keep the HTML page (RFC 9457).
Verify with
ORIGIN=https://render.com MISSING="/aws-probe-$(head -c 6 /dev/urandom | od -An -tx1 | tr -d ' \n')" curl -sS -D - -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: application/json, application/problem+json;q=0.9, */*;q=0.1' "$ORIGIN$MISSING" | head -20 -
Partial worth 2.3 points Experimental WebMCP browser tool declaration — The homepage declares 2 WebMCP tools: 2 registerTool calls, 0 with a name, a description, and an inputSchema. An incomplete tool lacks a member that Chrome's documentation asks for.
WebMCP lets a page register tools for an in-browser agent. It is a W3C Community Group draft.
Sources: WebMCP draft (W3C Web Machine Learning Community Group), Chrome: WebMCP (Chrome for Developers), Chrome: WebMCP imperative API (Chrome for Developers), Chrome: WebMCP declarative API (Chrome for Developers)
- Read today by
- Chrome, behind an origin trial. Lighthouse audits it.
- Google Search
- None
Fix
// WebMCP (W3C Community Group draft): register a tool an in-browser agent can call. if ('modelContext' in document) { document.modelContext.registerTool({ name: 'search_site', description: 'Search this site and return the matching pages.', inputSchema: { type: 'object', properties: { query: { type: 'string', description: 'The words to search for' } }, required: ['query'], }, annotations: { readOnlyHint: true }, async execute({ query }) { // Call the site's own search here and return its results as text. return 'Results for ' + query; }, }).catch((error) => console.warn('WebMCP registration failed', error)); }Note
Give every tool a name, a description, and an input schema, as Chrome's documentation asks: registerTool() takes them as members, and a form takes toolname and tooldescription. A tool runs with the visitor's session, so expose only what that visitor could do, and ask for confirmation before any change of state.
Verify with
HOMEPAGE=https://render.com/ curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | grep -oE 'registerTool\(|<form[^>]*toolname[^>]*>' | sort | uniq -c -
Present Adopted AI crawler policy in robots.txt — 14 of 18 AI crawler tokens have their own robots.txt group: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User and Claude-SearchBot partly disallowed, and 8 more. The other 4 follow the * group (4 of the file's 8 rules).
Observation
GPTBot: own group, 4 rules, partly disallowed · OAI-SearchBot: own group, 4 rules, partly disallowed · ChatGPT-User: own group, 4 rules, partly disallowed · ClaudeBot: own group, 4 rules, partly disallowed · Claude-User: own group, 4 rules, partly disallowed · Claude-SearchBot: own group, 4 rules, partly disallowed · PerplexityBot: own group, 4 rules, partly disallowed · Google-Extended: own group, 4 rules, partly disallowed · Applebot-Extended: own group, 4 rules, partly di…
A crawler follows the robots.txt group that names it, otherwise the * group. A named group states the site's rules for that crawler.
Sources: RFC 9309, 2.2.1 (IETF), Google common crawlers (Google Search Central), OpenAI bots (OpenAI)
- Read today by
- AI crawlers that document robots.txt tokens.
- Google Search
- None
-
Present Draft Content-Signal preferences — robots.txt states Content-Signal search=yes, ai-input=yes, ai-train=yes in the User-agent: * group. 1 more line states values for other groups.
Observation
robots.txt: ai-train=yes, search=yes, ai-input=yes | ai-train=yes, search=yes, ai-input=yes
Content-Signal states search, ai-input and ai-train preferences in robots.txt. No crawler documents honouring it.
Sources: Cloudflare: Content Signals Policy (Cloudflare, 2025-09), IETF AIPREF (IETF)
- Read today by
- Cloudflare's scanner scores it. The IETF AIPREF drafts are the standards track.
- Google Search
- None
-
Present Adopted Discovery via Link response headers — The homepage Link header names the API catalog at /.well-known/api-catalog (rel=api-catalog) and the OpenAPI document at /openapi.json (rel=service-desc). It does not name /llms.txt and a markdown variant of the homepage.
Observation
link: </.well-known/api-catalog>; rel="api-catalog"; type="application/linkset+json"; profile="https://www.rfc-editor.org/info/rfc9727", </openapi.json>; rel="service-desc"; type="application/json", <https://api-docs.render.com/openapi/render-public-api-1.json>; rel="service-desc"; type="application/json", </docs/api>; rel="service-doc"; type="text/html", <https://api-docs.ren…
A Link header (RFC 8288) points a client at a resource before it parses the HTML.
Sources: RFC 8288 (IETF), IANA link relations (IANA)
- Read today by
- Clients that follow RFC 8288 and RFC 9727 links.
- Google Search
- None
-
Present Draft llms-full.txt expanded context — /llms-full.txt carries 151628 words of page text in 1330 KB. /llms.txt links it.
Observation
HTTP 200 · text/markdown · 1330 KB · Generated on: 2026-11-18 Obtain latest version from: https://render.com/llms-full.txt REST API llms reference: https://…
A convention that puts a site's text in one file. The llms.txt proposal does not define it.
Sources: llmstxt.org (llmstxt.org), Mintlify (Mintlify)
- Read today by
- Some documentation tools.
- Google Search
- None
-
Present Draft /llms.txt published and well-structured — /llms.txt opens with H1 "Render", with 4 H2 link sections and 411 links, 52.3 KB. The scan requested 6 links it names, and each answered 2xx. Not requested: 405 same-origin links (the scan samples up to 6). The proposal also suggests a blockquote summary under the H1.
Observation
HTTP 200 · text/markdown · 52.3 KB · headings: Render | Start here | Agent interfaces | Setup guides | Documentation | Core Platform | Start | Migrate from… | Compute…
A 2024 proposal for a markdown index of a site. Google Search does not use it.
Sources: llmstxt.org (llmstxt.org), Google: AI optimization guide (Google Search Central), Lighthouse llms.txt (Chrome for Developers)
- Read today by
- Some documentation tools and coding agents. Lighthouse audits it.
- Google Search
- None
-
Present Experimental Markdown content negotiation — The homepage serves text/markdown to `Accept: text/markdown, text/html;q=0.5`, with Vary: Accept, rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding (HTTP 200).
Observation
HTTP 200 · text/markdown · Vary: Accept, rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding · markdown body: yes
Some coding agents ask for text/markdown. Google Search does not use markdown.
Sources: RFC 7763 (IETF), Cloudflare: Markdown for Agents (Cloudflare), Google: AI optimization guide (Google Search Central)
- Read today by
- Claude Code, OpenCode and Cursor send Accept: text/markdown by default (Cloudflare, 2026-04).
- Google Search
- None
-
Not used 0 points Draft MPP discovery (x-payment-info or a 402 Payment challenge) — Not declared: /openapi.json describes 15 operations, and none declares x-payment-info.
Observation
/openapi.json: HTTP 200, 5 KB; 15 operations read
An operation with x-payment-info tells an agent that the call is paid, and states the intent, the payment method, and the amount. A 402 answer with a WWW-Authenticate Payment challenge is MPP's own way to ask for payment. MPP is a draft, and charging agents is a business decision.
Sources: MPP (mpp.dev), MPP: multi-method discovery (mpp.dev), draft-ryan-httpauth-payment (IETF (individual draft, expired)), isitagentready.com: MPP skill (isitagentready.com)
- Read today by
- Agents that pay with MPP; isitagentready.com.
- Google Search
- None
Note
Add x-payment-info to each operation you charge for, inside the OpenAPI description you already serve. Whether to charge agents, how much, and by which method are your decisions. A 402 answer that asks for payment with MPP carries a WWW-Authenticate: Payment challenge that states a method and an intent, among its other parameters. MPP is a draft, so the field names may change.
Verify with
ORIGIN=https://render.com # The scan reads the OpenAPI description it already holds. /openapi.json is the usual path; use the path your description is served at. curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: application/json, application/linkset+json;q=0.9, */*;q=0.5' "$ORIGIN/openapi.json" | jq -c '[.paths | to_entries[] | .key as $p | .value | to_entries[] | select(.value | type == "object" and has("x-payment-info")) | {operation: ((.key | ascii_upcase) + " " + $p), "x-payment-info": .value["x-payment-info"]}]' -
Present 0 points Draft Agent Skills declaration — Agent skills index at /.well-known/agent-skills/index.json lists 22 skills, each with name, type, description, url, and a sha256 digest under $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json. 22 artifacts (https://raw.githubusercontent.com/render-oss/skills/b985a6399ad64b2d7093cb5ee7bb29487ae05fee/skills/render-background-w…, …) are on another host, which this scan does not request (declared, not observed).
An agent skills index lists skill packages for agent runtimes. It is a draft on GitHub.
Sources: Agent Skills Discovery RFC (Cloudflare)
- Read today by
- Agent runtimes that read the draft.
- Google Search
- None
Not measured 1
Show 1 Hide 1 in Not measured
The scanner could not observe these. They left the score and lowered confidence.
-
Not measured Adopted Service status and changelog feed — Not measured: the status page at https://status.render.com is on another host, which this scan does not request.
A status page and a changelog feed say whether the service is up and what changed.
Sources: RFC 8631 (status relation, section 6.4) (IETF), RFC 4287 (IETF)
- Read today by
- Integrators and monitoring tools.
- Google Search
- None
Verify with
ORIGIN=https://render.com curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$ORIGIN/" | grep -oiE '<link[^>]+(atom|rss)[^>]*>|href="[^"]*(status|changelog)[^"]*"' | sort -u for p in /status /changelog; do printf '%s -> ' "$p"; curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' -o /dev/null -w '%{http_code} %{content_type}\n' "$ORIGIN$p"; done
Out of scope for this site 26
Show 26 Hide 26 in Out of scope for this site
The scan did not ask this site for these checks. Each says why. If one should apply, the error is ours, not yours.
Sites with an API or agent surface
The scan found an HTTP API. A check that reads another kind of surface is not asked.
-
Out of scope 0 points Draft A2A agent card — Not scored: this check applies to a site that runs an A2A agent, and the scan found none.
An A2A agent card describes an agent the site runs. An A2A server publishes it.
Sources: A2A specification (A2A Project)
- Read today by
- A2A clients.
- Google Search
- None
-
Out of scope 0 points Draft Cryptographically signed agent card — Not scored: this check applies to a site that runs an A2A agent, and the scan found none.
An A2A card may be signed with JWS. Signing is optional in the specification.
Sources: A2A specification 1.0.0, 8.4 Agent Card Signing (A2A Project), a2a.proto 1.0.0 (A2A Project), a2a-python 1.3.0 (a2a.utils.signing) (A2A Project, 2026-10), RFC 7515 (IETF), RFC 8785 (IETF)
- Read today by
- A2A clients that verify cards.
- Google Search
- None
-
Out of scope 0 points Experimental ARD resource discovery manifest — Not scored: robots.txt has no Agentmap line, the homepage links no ARD manifest or AI catalog, and the 4 manifest paths served none (/.well-known/ard.json 404 text/html; /.well-known/agent-resources.json 404 text/html; /.well-known/ai-catalog.json 404 text/html; /ard.json 404 text/html).
An ARD manifest lists a site's agent resources. Lighthouse does not count a missing one against a site.
Sources: Agentic Resource Discovery (ARD) v0.91, a proposal (ARD project, 2026-08), AI Catalog specification (AI Catalog Working Group), Lighthouse v13.6.0: the ARD gatherer (Google Chrome, 2026-10), Lighthouse v13.6.0: the ard-schema audit (Google Chrome, 2026-10)
- Read today by
- Lighthouse (ard-schema audit).
- Google Search
- None
-
Out of scope 0 points Draft /auth.md agent authentication guide — Not scored: this check applies to a site that uses OAuth, and the scan found none.
auth.md is one vendor's convention (WorkOS) for telling an agent how to authenticate.
Sources: WorkOS auth.md (WorkOS)
- Read today by
- Agents built on WorkOS.
- Google Search
- None
-
Out of scope 0 points Experimental DNS-AID discovery record — Not scored: this check applies to a site that runs an MCP server or runs an A2A agent, and the scan found none.
DNS-AID publishes agents in DNS. It is an individual Internet-Draft with no IETF standing.
Sources: draft-mozleywilliams-dnsop-dnsaid (IETF)
- Read today by
- Cloudflare's scanner.
- Google Search
- None
-
Out of scope 0 points Draft MCP server card — Not scored: this check applies to a site that runs an MCP server, and the scan found none.
An MCP server card describes a remote MCP server. It is an optional extension (SEP-2127), not core MCP.
Sources: SEP-2127 (Model Context Protocol, 2026-10), discovery.md (Model Context Protocol)
- Read today by
- MCP clients that implement SEP-2127; Cloudflare's scanner.
- Google Search
- None
-
Out of scope Adopted MCP server answers and lists its tools — Not scored: the scan found no MCP endpoint. No server card, ARD manifest, AI catalog or homepage link names one, and /mcp answered HTTP 200, which does not signal an MCP server.
An agent given the address of an MCP server can call its tools. The scan opens one session to see that the server answers and what it offers.
Sources: MCP 2025-11-25: lifecycle (Model Context Protocol, 2025-11), MCP 2025-11-25: transports (Model Context Protocol, 2025-11), MCP 2025-11-25: tools (Model Context Protocol, 2025-11), MCP 2026-07-28: server/discover (Model Context Protocol, 2026-07), MCP 2026-07-28: versioning (Model Context Protocol, 2026-07), MCP 2026-07-28: Streamable HTTP (Model Context Protocol, 2026-07), Agentic AI Foundation: MCP joins the Linux Foundation (Linux Foundation, 2025-12)
- Read today by
- MCP clients: agent apps, coding agents, and chat products that connect to MCP servers.
- Google Search
- None
-
Out of scope Adopted OAuth discovery documents — Not scored: this check applies to a site that uses OAuth, and the scan found none.
-
Out of scope 0 points Experimental Rate limits and quotas documented — Not scored: this check applies to API platform sites; this site was measured as SaaS.
Declared limits let a client pace its calls. RateLimit headers are an IETF draft.
Sources: draft-ietf-httpapi-ratelimit-headers (IETF)
- Read today by
- API clients.
- Google Search
- None
-
Out of scope 0 points Draft Web Bot Auth key directory — Not scored: this check applies to a site that runs an A2A agent or serves /.well-known/http-message-signatures-directory, and the scan found neither.
The operator of a signing agent publishes its keys here. A site that only serves content needs none.
Sources: draft-ietf-webbotauth-httpsig-protocol (IETF, 2026-10), Cloudflare: Web Bot Auth (Cloudflare)
- Read today by
- Sites and CDNs that verify signed agents.
- Google Search
- None
Sites with a commercial signal
The homepage shows no commercial signal, so commerce checks are not asked of this site.
-
Out of scope 0 points Draft ACP discovery (/.well-known/acp.json) — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
An ACP discovery document at /.well-known/acp.json tells an agent where a business's checkout API is and which services it offers. The RFC behind it is a proposal.
Sources: ACP discovery RFC (status: Proposal) (Agentic Commerce Protocol), isitagentready.com: ACP skill (isitagentready.com)
- Read today by
- Agents that implement ACP checkout; isitagentready.com.
- Google Search
- None
-
Out of scope 0 points Draft Agent purchase policy — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
Whether agents may buy, and with what approval, is a policy the site states.
Sources: ACP (Agentic Commerce Protocol)
- Read today by
- Agent checkouts.
- Google Search
- None
-
Out of scope Adopted Inventory and price freshness — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
availability says whether an item is in stock. A past priceValidUntil can hide a product snippet.
Sources: Google: product snippet (Google Search Central)
- Read today by
- Google product snippets.
- Google Search
- Direct
-
Out of scope 0 points Draft Agent payment protocol (UCP profile or x402) — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
-
Out of scope Adopted Product/catalog schema — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
Product and Offer markup on product pages feeds merchant listings.
Sources: Google: merchant listing (Google Search Central), Google: product (Google Search Central)
- Read today by
- Google merchant listings and shopping agents.
- Google Search
- Direct
-
Out of scope Adopted Return policy machine-readable — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
A MerchantReturnPolicy states return terms in markup, also under the Organization.
Sources: Google: return policy (Google Search Central)
- Read today by
- Google merchant listings.
- Google Search
- Direct
-
Out of scope Adopted Seller identity declared — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
On a marketplace, the seller named on an offer is who the buyer contracts with.
Sources: Google: merchant listing (Google Search Central)
- Read today by
- Google merchant listings.
- Google Search
- Direct
-
Out of scope Adopted Shipping cost and delivery declared — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
shippingDetails lets a client compute the delivered price.
Sources: Google: merchant listing (Google Search Central)
- Read today by
- Google merchant listings.
- Google Search
- Direct
-
Out of scope 0 points Draft UCP manifest (/.well-known/ucp) — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.
A UCP profile at /.well-known/ucp declares commerce capabilities. UCP is a draft.
Sources: UCP (Universal Commerce Protocol), Shopify profiles (Shopify)
- Read today by
- UCP agents; Shopify stores serve it.
- Google Search
- None
Every site
-
Out of scope 0 points Experimental AI usage policy page — Not scored: robots.txt and Content-Signal state no AI restriction, so there is none for a policy page to explain.
A page that explains in prose the AI restrictions the site states. No standard defines it.
Sources: RFC 9309 (IETF)
- Read today by
- People reading the site's terms.
- Google Search
- None
-
Out of scope 0 points Draft Machine-readable booking action — Not scored: this check applies to services sites; this site was measured as SaaS.
A ReserveAction declares a booking target in markup. No search engine documents a feature that reads it.
Sources: schema.org/ReserveAction (Schema.org)
- Read today by
- None documented.
- Google Search
- None
-
Out of scope 0 points Adopted Documents in machine-readable formats — Not scored: this check applies to institution sites; this site was measured as SaaS.
Tagged PDF or an HTML version can be read by screen readers and by machines.
Sources: GOV.UK: HTML not PDF (Government Digital Service), ISO 14289 (PDF/UA) (ISO)
- Read today by
- Screen readers; GOV.UK publishes HTML first.
- Google Search
- None
-
Out of scope 0 points Adopted FAQ markup for visible questions — Not scored: no heading on the homepage names a FAQ section, and the homepage carries no FAQPage markup.
Observation
visible questions under a FAQ heading: 0
FAQPage marks up questions that are visible on the page. Google stopped showing FAQ rich results on 7 May 2026.
Sources: Google Search updates (Google Search Central), Google: structured data policies (Google Search Central)
- Read today by
- Bing names FAQ markup as an example of labelled content.
- Google Search
- None
-
Out of scope 0 points Draft Reuse and licensing terms declared — Not scored: this check applies to publisher or institution sites; this site was measured as SaaS.
TDMRep reserves text and data mining rights in a machine-readable form, as EU DSM Article 4(3) allows.
Sources: TDMRep CG report (W3C), Directive (EU) 2019/790 (European Union)
- Read today by
- Text and data mining tools that implement TDMRep.
- Google Search
- None
-
Out of scope 0 points Adopted Content provenance declared — Not scored: this check applies to publisher or institution sites; this site was measured as SaaS.
Article markup with an author and dates lets a client attribute and date a source.
Sources: Google: Article structured data (Google Search Central)
- Read today by
- Google article features.
- Google Search
- Direct
-
Out of scope Adopted Service/product scope machine-readable — Not scored: the homepage markup declares no Service-type node.
Service markup states what is offered, by whom and where. An incomplete node leaves a client to guess.
Sources: schema.org/Service (Schema.org)
- Read today by
- Clients that read schema.org Service. Google has no Service rich result.
- Google Search
- None
Passed 16
Show 16 Hide 16 in Passed
Scored checks that pass, the heaviest first.
-
Passed Adopted OpenAPI definition — OpenAPI 3.1.0 at /openapi.json (api-catalog service-desc (/.well-known/api-catalog)) declares info.title "Render AI Discovery API", info.version 1.0.0, and 15 paths. Not scored: the scan requested 13 of its 13 GET operations on this origin, and 12 answered with 2xx: /api/agent/docs-search answered HTTP 400; /api/status answered HTTP 200; /llms.txt answered HTTP 200; and 10 more. Not scored: 2 templated paths were not requested.
Observation
tried: /openapi.json 200
An OpenAPI document describes an HTTP API so a client can call it without guessing.
Sources: OpenAPI 3.1 (OpenAPI Initiative), RFC 8631 (IETF)
- Read today by
- API clients and code generators.
- Google Search
- None
-
Passed Adopted JSON-LD structured data — 3 JSON-LD blocks parse, and the page entity, Organization "Render", is stated under a schema.org @context.
Observation
JSON-LD: 3 blocks, 3 parsed · schema.org @context: yes · Microdata: 0 items · RDFa: 0 items · top-level types: Organization, WebSite, SoftwareApplication
Structured data names the entity a page describes. Google reads JSON-LD, Microdata and RDFa alike.
Sources: Google: intro to structured data (Google Search Central), schema.org (Schema.org), Bing Webmaster Guidelines, §14: structured data (Microsoft Bing)
- Read today by
- Google rich results; any schema.org reader.
- Google Search
- Direct
-
Passed Adopted Content that needs no JavaScript — 8573 characters of text are in the HTML before any script runs.
Observation
static text: 8573 characters · inside <noscript>: 0 characters · markup: 766386 characters
Several AI crawlers do not run JavaScript. Text that appears only after scripts run is invisible to them.
Sources: Vercel: the rise of the AI crawler (Vercel), Google: JavaScript SEO basics (Google Search Central), Bing Webmaster Guidelines, §8: rendering (Microsoft Bing)
- Read today by
- GPTBot and ClaudeBot fetch HTML without rendering; Googlebot renders.
- Google Search
- Indirect
-
Passed Adopted Readable homepage — HTTP 200 text/html, 749 KB, 1406 words of visible text.
Observation
HTTP 200 · text/html · 749 KB
The homepage is the first URL every agent requests. An error or an empty page gives it nothing to read.
Sources: RFC 9110 (IETF), Google: 301 redirects (Google Search Central), Bing Webmaster Guidelines, §7: 301 and 302 redirects (Microsoft Bing)
- Read today by
- Every crawler and agent.
- Google Search
- Direct
-
Passed Adopted Semantic heading structure — 1 H1, 6 H2s, and 22 H3s in an outline of 29 headings, with no skipped level.
Observation
outline: H1 H2 H3 H3 H3 H2 H2 H3 H3 H3 H3 H3 H2 H3 H3 H3 H3 H3 H3 H3 H3 H2 H3 H3 H3 H3 H3 H3 H2
Headings outline the page for screen readers and for any client that splits text by section.
Sources: W3C WAI headings tutorial (W3C), Google SEO starter guide (Google Search Central), Bing Webmaster Guidelines, §13: titles, descriptions and headings (Microsoft Bing)
- Read today by
- Screen readers; clients that chunk HTML by heading.
- Google Search
- Indirect
-
Passed Adopted Homepage indexable: no noindex directive — No noindex: the homepage states <meta name="robots" content="index, follow">, which does not ask to leave the page out.
Observation
<meta name="robots" content="index, follow">
A noindex in a meta tag or in a response header keeps the page out of search results. Bing keeps it out of Copilot too.
Sources: Bing Webmaster Guidelines, §10: NOINDEX and the other robots directives (Microsoft Bing), Bing: robots meta tags and attributes that Bing supports (Microsoft Bing), Google: block indexing with noindex (Google Search Central), Google: robots meta tag specifications (Google Search Central)
- Read today by
- Google and Bing. Bing applies the same directives to Copilot answers.
- Google Search
- Direct
-
Passed Adopted robots.txt crawl policy — /robots.txt has 2 groups and 8 rules across all groups, and 1 Sitemap line.
Observation
HTTP 200 · text/plain · 921 bytes · # Individual pages may still declare more restrictive per-page robots directives. User-Agent: * Content-Signal: ai-train=yes, search=yes, a…
Crawlers read robots.txt before they fetch a page (RFC 9309). Its Sitemap line tells them where the URL list is.
Sources: RFC 9309 (IETF, 2022-09), Google robots.txt (Google Search Central)
- Read today by
- Google, Bing, and the AI crawlers that document robots.txt support.
- Google Search
- Direct
-
Passed Adopted XML sitemap — Sitemap index https://render.com/sitemap-index.xml parses and lists 3 child sitemaps. This scan does not read the child sitemaps.
Observation
HTTP 200 · text/xml · 318 bytes · root <sitemapindex>
A sitemap lists the URLs a site wants crawled. Google says a small, well-linked site may not need one.
Sources: Google: build a sitemap (Google Search Central), sitemaps.org (sitemaps.org), Bing Webmaster Guidelines, §3: lastmod (Microsoft Bing)
- Read today by
- Google and Bing.
- Google Search
- Direct
-
Passed Adopted API catalog — Linkset at /.well-known/api-catalog carries 4 entries, and 2 of them pair an anchor with a service-desc link, the first pointing at https://api-docs.render.com/openapi/render-public-api-1.json. The scan requested the same-origin service-doc target /docs/api, which answered HTTP 200. 2 further targets leave this host and were not followed. Not scored: the service-desc target /openapi.json answered HTTP 200. Not scored: the service-doc target /docs answered HTTP 200. Not scored: the status target /api/status answered HTTP 200. Not scored: 1 further catalog target was not requested by this scan.
Observation
relations: service-desc, service-doc, status, describedby; observed target: /docs/api
An API catalog lists a publisher's APIs in one document at a fixed address (RFC 9727).
Sources: RFC 9727 (IETF, 2025-06)
- Read today by
- API clients that follow RFC 9727.
- Google Search
- None
-
Passed Adopted Documentation reachable — Documentation is reachable at /docs/api (Link header rel=service-doc) and returns HTTP 200 text/html with 838 readable words.
Observation
tried: /docs/api 200 | /docs 200 | /docs/web-services 200 | /docs/private-services 200 | /documentation 404 | /developers 404 | /gelistiriciler 404
Documentation linked as service-doc (RFC 8631), or from the homepage, is how a client learns the API.
Sources: RFC 8631 (IETF)
- Read today by
- Developers and agents integrating the API.
- Google Search
- None
-
Passed Adopted Canonical URL — Canonical https://render.com/ matches the page reached.
Observation
<link rel="canonical" href="https://render.com">
A canonical link names the one URL a page is known by. Google treats it and redirects as canonical signals.
Sources: Google: consolidate duplicate URLs (Google Search Central), RFC 6596 (IETF), Bing Webmaster Guidelines, §6: duplicate URLs and canonicals (Microsoft Bing)
- Read today by
- Google and Bing.
- Google Search
- Direct
-
Passed Adopted Structured pricing information — Homepage markup carries 1 complete price node; the first, Offer (unnamed), states 0 USD.
Observation
{"price":0,"priceCurrency":"USD","where":"homepage"}A price in markup is read without parsing prose. An Offer with a price and no currency is ambiguous.
Sources: schema.org/Offer (Schema.org), Google: product snippet (Google Search Central)
- Read today by
- Clients that read schema.org Offer. Google reads an Offer only inside a Product, which product-schema measures.
- Google Search
- None
-
Passed Adopted HTTP caching of the homepage — The homepage sends Cache-Control "s-maxage=1, stale-while-revalidate=31535999" and ETag, and a request with If-None-Match was answered HTTP 304 Not Modified.
Observation
Cache-Control: s-maxage=1, stale-while-revalidate=31535999 · ETag: W/"cu9v1ty6lygfci" · Last-Modified: (none) · conditional GET with If-None-Match: HTTP 304
Cache-Control says how long the homepage may be reused. A validator lets a crawler ask whether it changed, and a 304 answer skips the body.
Sources: RFC 9111: HTTP Caching (IETF, 2022-06), RFC 9110, 13: conditional requests (IETF), Google: HTTP caching for crawlers (Google Search Central, 2024-12), Bing Webmaster Guidelines, §3: ETag and lastmod (Microsoft Bing)
- Read today by
- Googlebot sends If-None-Match and If-Modified-Since. Every HTTP cache reads Cache-Control.
- Google Search
- Direct
-
Passed Adopted Language declaration and multilingual access — html lang="en" is a well-formed BCP 47 tag, with no hreflang alternates.
Observation
html lang="en" · alternates: none · content-language: (none)
The lang attribute names the language of the text. WCAG 3.1.1 requires it at level A. Google reads hreflang, not lang.
Sources: WCAG 2.2, 3.1.1 (W3C), Google: managing multi-regional sites (Google Search Central), Google: localized versions (Google Search Central)
- Read today by
- Screen readers and translation tools. Google ignores the lang attribute and reads hreflang.
- Google Search
- Indirect
-
Passed Adopted A real 404 for a missing page — /aws-probe-65b4253a8c74, a path that does not exist, answered HTTP 404.
Observation
HTTP 404 · text/html · first 16 KB read
A URL that does not exist answers 404 or 410 (RFC 9110). A 200 there makes every mistyped link look like a page.
Sources: RFC 9110, 15.5.5: 404 Not Found (IETF), Google: HTTP status codes and soft 404s (Google Search Central), Bing Webmaster Guidelines, §9: 404 for missing pages (Microsoft Bing)
- Read today by
- Google reports a missing page that answers 200 as a soft 404. Every HTTP client reads the status first.
- Google Search
- Direct
-
Passed Adopted Per-page content separation (no SPA fallback) — The homepage and /about have different titles ("Render | The cloud for builders" and "About | Render") and different main text (68% word overlap).
Observation
compared / with /about · titles "Render | The cloud for builders" / "About | Render" · skeleton 68% · main-text word overlap 68% · main text 3356 characters
A route that answers every URL with the same page makes every URL look alike to a crawler.
Sources: Google: HTTP errors and soft 404s (Google Search Central)
- Read today by
- Google flags such pages as soft 404s.
- Google Search
- Direct
Hand this report to your coding agent
The prompt lists 4 checks to fix. Each has the value the scan measured and a command that repeats the measurement. It adds the change to make where the scan could build one. After them it lists 2 agent conventions, at lower priority. The prompt is served at https://agenticwebscore.com/aws/render.com/prompt.md. The command below prints it, so you can paste the output into your agent.
curl -s https://agenticwebscore.com/aws/render.com/prompt.md - prompt.md The prompt Paste this into your own agent
- agent-brief.md Agent brief The prompt plus every finding
- bundle.md Bundle Status and brief in one document
- status.md Status Every check with its measurement
This scan cannot see which AI answers cite the site. Bing Webmaster Tools reports citations in Copilot and in Bing's AI summaries under AI Performance. Google Search Console includes AI Overviews and AI Mode in its Performance report totals, without a separate view (Google's guide to AI features). Both need a verified owner of the site.
Badge
Show this score on your own site. Press Get the badge, paste its snippet into your homepage, and press Check my badge. The directory then lists your site as a verified listing.
Embed your score badge
Paste a snippet into a README, a site footer, or your docs. The badge shows the score this page publishes, and it links here.
These snippets do not list your site in the directory. A verified listing is a separate step. Claim the badge
Ship a fix, then re-scan
Measured 16 hours ago. Nothing re-scans a site on its own. A scan runs once, when somebody asks for it — and that somebody need not be you. Anyone can request a scan of any public host, so this page may be the first you hear of it. After you ship a fix, press Re-scan now. A check that now passes adds its points to the score.
Why a re-scan can differ
The current rubric evaluates 3 of its 60 checks against a clock: security-txt, status-page, and inventory-freshness. They can change with no change to the site. A response slower than 12 s is reported as not measured, so the same bytes served slowly can move the score and the fingerprint.
Measured as: SaaS / software product
Can an agent understand what the product does, what it costs, and how to call it? Checks that only apply to other site profiles were not scored, so you are not asked to do work that does not apply to you.
- · SaaS / software product (score 7), matched: SoftwareApplication schema; A pricing page responds; A documentation path responds.
Signal scores
- SaaS 7
- API platform 5
- Publisher 2
- Services 2
Modules
- Every site: always in scope.
- Sites with an API or agent surface : in scope.
- · Link rel="api-catalog" </.well-known/api-catalog> on the homepage
- · /.well-known/api-catalog lists 4 linkset entries
- · /openapi.json is an OpenAPI 3.1 document
- Sites with a commercial signal : out of scope. The homepage shows no commercial signal.
Scan record
- Target
- https://render.com
- Measured at
- https://render.com/
- Scanned
- Requests
- 64
- Duration
- 4.7s
- Confidence
- 99% · high
- Rubric
- rubric v0.9.1
Fingerprint
34dcd9c5d967… verify this record
full hash
34dcd9c5d96715a2fc9a6cff95e06d07c3a8a0aceba9bcdaf6d365847bb8cb35
Page as an agent receives it
- Words
- 1406
- Est. tokens
- 1898
- Markup
- 748.5 KB
- Language
- en
“Render | The cloud for builders”
By dimension
Each score is the share of the in-scope web-standards points a dimension earned. A dash means the dimension has no web-standards check in scope. The agent conventions are scored apart, as their own part.
-
Discoverability
100- Pass
- 6
- Partial
- 0
- Fails
- 0
- Not counted
- 0
Unscored: 0 in use, 0 not used
-
Content
88.9- Pass
- 6
- Partial
- 3
- Fails
- 0
- Not counted
- 1
Unscored: 0 in use, 1 not used
-
Crawler access
100- Pass
- 1
- Partial
- 0
- Fails
- 0
- Not counted
- 0
Unscored: 1 in use, 1 not used
-
API and agent
100- Pass
- 3
- Partial
- 0
- Fails
- 0
- Not counted
- 3
Unscored: 1 in use, 1 not used, 1 with an error
-
Commerce
—- Pass
- 0
- Partial
- 0
- Fails
- 0
- Not counted
- 5
Unscored: 0 in use, 0 not used
Request transcript 64 requests
Every fetch this scan record logged, in order. A fetch that followed redirects shows how many redirect requests it made.
63 fetches, 1 redirect request.
-
/
200 text/html 748.5 KB 748ms
-
/robots.txt
200 text/plain 921 B 194ms
-
/sitemap.xml
404 text/html 16.0 KB 210ms
-
/llms.txt
200 text/markdown 52.3 KB 218ms
-
/.well-known/security.txt
200 text/plain 186 B 194ms
-
/security.txt
404 text/html 16.0 KB 217ms
-
/about
200 text/html 242.0 KB 229ms
-
/contact
200 text/html 187.4 KB 644ms
-
/pricing
200 text/html 750.4 KB 330ms
-
/docs
200 text/html 571.5 KB 336ms
-
/developers
404 text/html 16.0 KB 206ms
-
/.well-known/api-catalog
200 application/linkset+json 1.1 KB 167ms
-
/openapi.json
200 application/json 5.5 KB 165ms
-
/.well-known/openapi.json
404 text/html 16.0 KB 208ms
-
/.well-known/mcp/server-card.json
200 application/json 961 B 233ms
-
/.well-known/ai-catalog.json
404 text/html 16.0 KB 218ms
-
/.well-known/agent-card.json
404 text/html 16.0 KB 216ms
-
/.well-known/oauth-protected-resource
404 text/html 16.0 KB 218ms
-
/.well-known/oauth-authorization-server
404 text/html 16.0 KB 223ms
-
/.well-known/openid-configuration
404 text/html 16.0 KB 208ms
-
/.well-known/ard.json
404 text/html 16.0 KB 203ms
-
/.well-known/agent.json
404 text/html 16.0 KB 437ms
-
/.well-known/http-message-signatures-directory
404 text/html 16.0 KB 356ms
-
/mcp
200 +1 redirect text/html 16.0 KB 603ms
-
/llms-full.txt
200 text/markdown 1330.1 KB 598ms
-
/openapi.yaml
404 text/html 16.0 KB 213ms
-
/api/openapi.json
404 text/html 16.0 KB 212ms
-
/swagger.json
404 text/html 16.0 KB 284ms
-
/.well-known/agent-skills/index.json
200 application/json 14.5 KB 205ms
-
/.well-known/agent-skills.json
404 text/html 16.0 KB 304ms
-
/.well-known/skills.json
404 text/html 16.0 KB 298ms
-
/.well-known/agent-resources.json
404 text/html 16.0 KB 297ms
-
/ard.json
404 text/html 16.0 KB 396ms
-
/documentation
404 text/html 16.0 KB 215ms
-
/gelistiriciler
404 text/html 16.0 KB 208ms
-
/status
404 text/html 16.0 KB 202ms
-
/changelog
200 text/html 749.5 KB 420ms
-
/releases
404 text/html 16.0 KB 311ms
-
/whats-new
404 text/html 16.0 KB 201ms
-
/docs/sandbox
404 text/html 16.0 KB 354ms
-
/sandbox
404 text/html 16.0 KB 481ms
-
/developers/sandbox
404 text/html 16.0 KB 330ms
-
/sitemap-index.xml
200 text/xml 318 B 233ms
-
/docs/web-services
200 text/html 500.0 KB 270ms
-
/docs/sandboxes/all
200 text/markdown 196.1 KB 234ms
-
/docs/workflows/all
200 text/markdown 230.8 KB 246ms
-
/docs/your-first-deploy.md
200 text/markdown 22.5 KB 217ms
-
/docs/free.md
200 text/markdown 12.0 KB 196ms
-
/docs/platform-features-by-plan.md
200 text/markdown 5.4 KB 202ms
-
/docs/llm-support.md
200 text/markdown 10.5 KB 178ms
-
/api/agent/docs-search
400 application/json 53 B 176ms
-
/api/status
200 application/json 51 B 288ms
-
/blog.md
200 text/markdown 2.6 KB 192ms
-
/articles.md
200 text/markdown 6.8 KB 203ms
-
/.well-known/mcp.json
200 application/json 502 B 190ms
-
/.well-known/webmcp.json
200 application/json 1014 B 196ms
-
/.well-known/agents.json
200 application/json 491 B 199ms
-
/docs/api
200 text/html 331.5 KB 269ms
-
/docs/private-services
200 text/html 326.5 KB 259ms
-
/
200 text/markdown 5.2 KB 210ms
-
/
304 — 0 B 195ms
-
/aws-probe-65b4253a8c74
404 text/html 16.0 KB 209ms
-
/aws-probe-65b4253a8c74
404 text/html 16.0 KB 218ms