aistudio.google.com
Journey
58.3/ 100
C · Needs work
Waymark scored aistudio.google.com 58.3/100 (C) on 26 Aug 2026.
aistudio.google.com is blockers remain. Discovery is the strongest layer, and Usability is the open one. Next: openAPI document.
FindMixed
15.9/20
14 of 20 checks passed
DoorMixed
18.3/30
19 of 32 checks passed
ToolsWeak
18.3/40
6 of 15 checks passed
Pay
N/A
No cart or pay rail — out of the denominator.
Group by
1. Can an agent discover and trust you? 70/100
Whether an agent can find this origin from public files and treat it as the real one.
pass
HTTPS reachable
2/2
Evidence. Homepage responded 200 over HTTPS.
Probed homepage.
pass
robots.txt present
2/2
Evidence. Valid robots.txt with User-agent rules.
Probed robots.txt.
pass
XML sitemap
2/2
Evidence. Found sitemap.xml or sitemap index.
failed
Well-known AI catalog
0/1
Evidence. No ai-plugin.json or ai-catalog.json.
Recommended fix. Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.
pass
AGENTS.md
1/1
Evidence. Found /agents.md.
partial
robots.txt AI policy
Required
1/2
Evidence. robots.txt present but no named AI crawlers.
Probed robots.txt.
Recommended fix. Name GPTBot, ClaudeBot, Google-Extended, PerplexityBot and state allow or deny.
pass
Sitemap for agents
Recommended
2/2
Evidence. Sitemap document fetched.
Probed sitemap.
failed
HTTP Link header
bonus
0/1
Evidence. No rel=sitemap|describedby|api-catalog|alternate on homepage.
Probed homepage + sitemap.
Recommended fix. Send RFC 8288 Link headers for related machine resources.
failed
ai-plugin.json
bonus
0/1
Evidence. No /.well-known/ai-plugin.json.
Probed well-known paths.
Recommended fix. Optionally publish a plugin-style capability manifest.
pass
API catalog linkset
bonus
2/2
Evidence. api-catalog found.
scanner error
Wikipedia sitelink
bonus
0/4
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
scanner error
Wikidata official website
bonus
0/3
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
scanner error
Brand official-website match
Recommended
0/3
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
pass
Public MCP registry listing
bonus
1/1
Evidence. Registry hit at https://glama.ai/mcp/servers?query=aistudio.
Probed public URLs named in the evidence.
failed
Package homepage match
bonus
0/1
Evidence. No npm package homepage matching aistudio.google.com.
Probed homepage.
Recommended fix. Publish an official package whose homepage is this domain.
failed
Sitemap lastmod
bonus
0/1
Evidence. Sitemap without lastmod.
Recommended fix. Add lastmod dates to sitemap entries.
pass
related-website-set
bonus
1/1
Evidence. related-website-set found.
n/a
ads.txt
bonus
0/1
Evidence. No ads inventory (N/A).
2. Do you welcome agents? 94/100
Whether crawlers and signed bots are allowed through rather than blocked at the door.
pass
AI crawlers not blanket-blocked
2/2
Evidence. No blanket Disallow: / for common AI bots.
n/a
robots Crawl-delay
bonus
0/1
Evidence. No Crawl-delay (optional).
pass
Web Bot Auth keys
Recommended
2/2
Evidence. Signature directory found.
partial
CORS / API hint
0.5/1
Evidence. No CORS header or obvious API path.
Recommended fix. If you expose an API, send Access-Control-Allow-Origin for intended clients.
pass
CSP or X-Frame-Options
1/1
Evidence. CSP or X-Frame-Options present.
pass
robots.txt agent-user policy
Required
2/2
Evidence. No Disallow: / for ChatGPT-User, Claude-User, or Perplexity-User (silence passes).
3. Does an agent understand who you are and what you do? 42/100
Whether the site explains the product in language a model can ingest.
pass
Title and description
2/2
Evidence. Title and meta description present.
failed
JSON-LD structured data
0/4
Evidence. No JSON-LD on the homepage.
Probed homepage.
Recommended fix. Add JSON-LD (Organization, WebSite, or SoftwareApplication).
pass
html lang attribute
1/1
Evidence. html[lang] is set.
failed
JSON-LD entities
Recommended
0/4
Evidence. No JSON-LD.
Recommended fix. Embed Organization, Product, Offer, SoftwareApplication, or FAQPage.
n/a
JSON-LD sameAs
bonus
0/2
Evidence. No JSON-LD.
pass
Open Graph basics
bonus
2/2
Evidence. Open Graph plus canonical.
pass
llms.txt
2/2
Evidence. Found /llms.txt with content.
pass
llms.txt index
Recommended
2/2
Evidence. llms.txt has content.
pass
llms.txt size and links
Recommended
2/2
Evidence. llms.txt 400000 chars, 2 URL(s).
pass
llms-full.txt
bonus
1/1
Evidence. llms-full.txt present.
pass
Section llms.txt
bonus
1/1
Evidence. Fetched /docs/llms.txt.
Probed public URLs named in the evidence.
n/a
NLWeb schemamap
bonus
0/1
Evidence. No schemamap (N/A unless you offer NL search).
failed
Trust pages
Recommended
0/2
Evidence. No about/privacy/contact link.
Recommended fix. Link about or privacy from the homepage.
n/a
Speakable markup
bonus
0/1
Evidence. No SpeakableSpecification (N/A unless voice content).
n/a
humans.txt
bonus
0/1
Evidence. No /humans.txt (optional).
failed
security.txt
Recommended
0/1
Evidence. No /.well-known/security.txt Contact.
Probed well-known paths.
Recommended fix. Publish /.well-known/security.txt with a Contact field.
failed
RSS or Atom feed
0/1
Evidence. No RSS/Atom link.
Recommended fix. Expose an RSS or Atom feed for machine subscribers.
n/a
RSS or Atom document
bonus
0/1
Evidence. No /feed or /rss.xml document.
failed
Agent instruction / when-to-use
Required
0/3
Evidence. Agent file exists without when-to-use guidance.
Recommended fix. Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.
n/a
Organization schema completeness
Recommended
0/2
Evidence. No Organization JSON-LD to score completeness.
n/a
Schema type breadth
Recommended
0/2
Evidence. No JSON-LD to score type breadth.
failed
Content without JavaScript
Required
0/3
Evidence. Raw HTML is thin for agents (H1=false, 16 chars).
Recommended fix. Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
4. Can an agent integrate with you? 64/100
Whether there is a documented machine door into the product.
pass
OpenAPI / Swagger link
2/2
Evidence. Homepage links mention OpenAPI or Swagger.
Probed homepage + OpenAPI.
pass
Login or docs link
3/3
Evidence. Login or developer docs link found.
pass
MCP well-known card
2/2
Evidence. MCP server card found under .well-known.
Probed well-known paths.
failed
MCP SSE / HTTP hint
0/1
Evidence. No MCP/SSE hint on the homepage.
Probed homepage.
Recommended fix. Document an MCP HTTP or SSE endpoint.
n/a
openapi.json fetchable
0/0
Evidence. OpenAPI linked but not fetchable at common or discovered paths.
Probed OpenAPI.
failed
Webhook or API docs
0/2
Evidence. No webhook/API docs mention.
Recommended fix. Document webhooks and REST/RPC APIs for agents.
pass
Agent skills index
2/2
Evidence. Skills index or mention found.
partial
OpenAPI document
Required
1/7
Evidence. OpenAPI probe.
Probed OpenAPI.
Recommended fix. Publish an OpenAPI document at a stable URL. Verify: curl -sI https://aistudio.google.com/openapi.json
pass
Public API surface
Recommended
7/7
Evidence. Docs or API paths look callable.
pass
Developer portal
Recommended
6/6
Evidence. Developer hub found.
partial
MCP server
Recommended
2/6
Evidence. MCP mentioned without a documented initialize.
Recommended fix. Publish an MCP card or document the MCP URL in llms.txt, then answer initialize.
pass
MCP server card
Recommended
2/2
Evidence. MCP card JSON found.
pass
Agent Skills files
bonus
2/2
Evidence. Skills file or index found.
failed
CLI tool
Recommended
0/3
Evidence. No CLI mention.
Recommended fix. Publish an official CLI.
n/a
GraphQL GET hint
bonus
0/2
Evidence. No GraphQL surface (N/A).
n/a
OpenAPI UI page
bonus
0/1
Evidence. No swagger-ui/redoc page.
n/a
OpenAPI (legacy slot)
0/0
Evidence. Linked but not fetched.
Probed public URLs named in the evidence.
5. Is your integration well-built? 40/100
Whether the integration surface is complete enough to call with confidence.
failed
MCP initialize
Required
0/3
Evidence. No MCP card to initialize
Recommended fix. Expose Streamable HTTP MCP and answer initialize.
pass
MCP server card
Recommended
2/2
Evidence. MCP card JSON found.
n/a
REST typed error model
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST versioning / deprecation policy
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST pagination pattern
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST async-job pattern
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST response schema coverage
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
Function calling compatibility
Recommended
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
REST batch / bulk endpoint
bonus
0/1
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
MCP tool listing
bonus
0/3
Evidence. No public tools/list.
n/a
MCP tool descriptions
bonus
0/3
Evidence. No public tools/list.
n/a
MCP parameter schemas
bonus
0/2
Evidence. No public tools/list.
n/a
MCP tool naming
bonus
0/2
Evidence. No public tools/list.
n/a
MCP tool annotations
bonus
0/2
Evidence. No public tools/list.
n/a
MCP resources exposed
Recommended
0/3
Evidence. No public MCP initialize.
6. Can an agent use you reliably in production? 33/100
Whether errors, idempotency, and limits are visible before a call fails.
partial
Rate limit signal
Recommended
1/2
Evidence. API surface without a rate-limit signal.
Recommended fix. Document or send rate-limit headers on APIs.
partial
Idempotency signal
Recommended
1/3
Evidence. API surface without idempotency notes.
Recommended fix. Document idempotency keys for mutating calls.
partial
Machine-readable errors
Recommended
1/4
Evidence. API surface without a JSON error shape.
Recommended fix. Return a JSON or problem+json error body.
n/a
Honest 404
Recommended
0/2
Evidence. Unknown path 200 is not a same-origin homepage shell (N/A).
Probed homepage.
n/a
Sandbox / test environment
bonus
0/2
Evidence. Docs do not mention sandbox/test keys (N/A).
n/a
Agent onboarding friction
Recommended
0/2
Evidence. No OpenAPI spec; onboarding stays N/A (no live signup probe).
Probed OpenAPI.
n/a
MCP error handling
bonus
0/2
Evidence. No public tools/call surface.
7. Can an agent authenticate to you? 60/100
Whether an agent can obtain access without a human in the loop.
failed
OAuth / OIDC well-known
0/2
Evidence. No oauth-authorization-server or openid-configuration.
Recommended fix. Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.
n/a
OAuth 2.0 surface
Required
0/5
Evidence. No delegated-access surface (N/A).
n/a
OAuth AS metadata
Required
0/3
Evidence. No AS metadata (N/A unless you run an AS).
n/a
PKCE S256
Required
0/2
Evidence. No OAuth metadata to evaluate PKCE.
pass
OAuth protected resource
Recommended
2/2
Evidence. oauth-protected-resource found.
n/a
Scoped permissions
Recommended
0/5
Evidence. No named OAuth scopes.
n/a
Scoped permissions
Recommended
0/2
Evidence. No OpenAPI document to analyze.
Probed OpenAPI.
n/a
auth.md
bonus
0/2
Evidence. No /auth.md (optional).
n/a
auth.md structure
bonus
0/2
Evidence. No /auth.md to grade.
pass
change-password well-known
bonus
1/1
Evidence. change-password HTTP 200.
n/a
MCP auth mechanism
bonus
0/2
Evidence. No discovered MCP endpoint to grade auth.
n/a
Agent auth WWW-Authenticate hint
bonus
0/1
Evidence. No documented API path to probe for WWW-Authenticate.
8. Can an agent transact with you? 100/100
Whether an agent can price, pay, or check out on a documented rail.
n/a
x402 payment
bonus
0/2
Evidence. No x402 (N/A unless you charge per call).
n/a
Agentic checkout (ACP)
bonus
0/3
Evidence. No ACP (N/A unless agent checkout).
n/a
ACP delegated payment
bonus
0/3
Evidence. No delegated payment (N/A).
n/a
Universal Commerce Protocol
bonus
0/3
Evidence. No /.well-known/ucp (N/A).
Probed well-known paths.
n/a
Machine Payments Protocol
bonus
0/2
Evidence. No MPP (N/A).
n/a
AP2 - Agent Payments Protocol
bonus
0/3
Evidence. No AP2 profile (N/A unless commerce rail).
pass
Pricing page
Recommended
3/3
Evidence. Fetched /pricing.
Probed public URLs named in the evidence.
n/a
pricing.md
bonus
0/2
Evidence. No /pricing.md (optional).
9. Can a user act through an agent? 83/100
Whether a person can finish a job through an agent-facing UI.
n/a
MCP Apps UI hint
bonus
0/1
Evidence. No MCP Apps hint (N/A unless you return UI).
pass
A2A agent card
Required
2/2
Evidence. Agent card JSON found.
partial
Web app manifest
bonus
0.5/1
Evidence. manifest link without a fetchable file.
Recommended fix. Host /manifest.webmanifest if the site is installable.
n/a
Listed on skills.sh
bonus
0/1
Evidence. No official skills.sh org for this brand; community listings are N/A.
10. Can an agent operate your website directly? 50/100
Whether an agent can read and operate the site itself when there is no API or MCP.
n/a
Markdown negotiation
bonus
0/1
Evidence. No markdown twin advertised (N/A).
n/a
/index.md fallback
bonus
0/1
Evidence. No /index.md twin (N/A).
n/a
WebMCP page tools
bonus
0/1
Evidence. No in-page WebMCP (N/A).
pass
NLWeb /ask
bonus
1/1
Evidence. NLWeb or /ask signal.
pass
Agent mode view
bonus
1/1
Evidence. mode=agent responded.
Probed public URLs named in the evidence.
pass
NodeInfo
bonus
1/1
Evidence. nodeinfo found.
pass
oEmbed discovery
bonus
1/1
Evidence. oEmbed discovery found.
n/a
Markdown alternate link
bonus
0/1
Evidence. No rel=alternate type=text/markdown.
n/a
Markdown frontmatter metadata
bonus
0/1
Evidence. No served markdown to check frontmatter.
n/a
Markdown content negotiation (acceptmarkdown.com)
bonus
0/1
Evidence. Homepage does not negotiate markdown.
Probed homepage.
failed
Agent-UA markdown docs
bonus
0/1
Evidence. Docs host did not serve markdown to GPTBot (HTTP 530, text/plain; charset=utf-8).
Recommended fix. Serve text/markdown to GPTBot (and similar agent UAs) on your docs host.
failed
Accessible document structure
bonus
0/3
Evidence. Homepage HTML lacks main/nav/H1 document structure.
Probed homepage.
Recommended fix. Give the homepage a main region, nav, H1, and a heading order that does not skip levels.
n/a
Code fence validity
bonus
0/1
Evidence. No markdown body to check fences.
partial
llms.txt links resolve
Recommended
1/2
Evidence. 1 real, 0 homepage-shell, 1 dead of 2 sampled links.
Probed homepage.
Recommended fix. Make every link your llms.txt declares resolve to real content, not a homepage shell 200.
About this snapshot & how to cite it
Public technical signals observed by Waymark. A score describes this snapshot; it does not guarantee that an agent will complete a task. Private and authenticated workflows are outside this scan.
Snapshot: . Cite the domain, score, scan time, and report URL. This URL serves the latest completed snapshot and can change after a rescan.
Share this snapshot
Also on the Board
- ora.ai90.9/100 · AScan them →
- superset.sh90.7/100 · AScan them →
- waymark.genedai.me87.2/100 · AScan them →
Email me if this score changes
Join the monitoring waitlist. Monitoring is not active yet. This saves your interest; it does not schedule scans or send change alerts.
Email this report
Send the current snapshot and a link. One email. Not a list.