amika.dev

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ✗Sitemap present & freshrequired0/4

  No valid sitemap found: robots.txt listed 0 Sitemap URL(s), and GET /sitemap.xml returned HTTP 404

  fix → Publish /sitemap.xml, reference it from robots.txt, and include <lastmod> dates so agents can tell what's current. Freshest lastmod seen: none.

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✓Brand search discoverabilityrequired4/4

  Both searches ("Amika" and "Amika developer tools") cited amika.dev: https://www.amika.dev/, https://docs.amika.dev/llms.txt, https://docs.amika.dev/reference/api-reference, https://www.amika.dev/pricing, https://app.amika.dev/signup

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• —MCP registry listingsrecommendedna

  No MCP server detected for this product

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✗robots.txt present & parseablerequired0/2

  GET /robots.txt returned HTTP 404

  fix → Serve a valid /robots.txt; without one, agent crawlers guess your policy.

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✓AI crawler policyrequired5/5

  No robots.txt (HTTP 404) — none of the 12 AI crawler user-agents are blocked. Note: without a robots.txt, crawlers guess your policy.

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✗Content Signals directivesemerging0/2

  No robots.txt (HTTP 404), so no Content-Signal lines are declared

  fix → Declare Content Signals in robots.txt (e.g. `Content-Signal: search=yes, ai-train=no`) to express AI usage preferences machine-readably.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✓Agent user-agent paritybetarequired4/4

  All three UAs get HTTP 200; bot bodies are ClaudeBot 100%, GPTBot 100% of the browser response (167300 bytes)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✗agents.mdrecommended0/3

  No agents.md: https://amika.dev/agents.md → HTTP 404, https://amika.dev/AGENTS.md → HTTP 404

  fix → Add /agents.md: what agents may do on your site, key URLs, auth, rate limits, and who to contact.

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "Amika provides a control plane for sandboxed cloud agents, enabling developers and teams to create, manage, and automate tasks using cloud devboxes and AI agents across various environments and tools.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ✗OpenGraph / social metadatarecommended0/2

  Homepage HTML contains none of og:title, og:description, og:image (twitter:card absent)

  fix → Add og:title, og:description, and og:image meta tags to your homepage; agents and link unfurlers use them as your canonical summary.

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✗llms.txtrecommended0/4

  GET /llms.txt returned HTTP 404

  fix → Add /llms.txt: an H1 with your name, a one-line blockquote summary, and H2 sections of curated links to docs, pricing, and API.

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✗llms-full.txtbonusrecommended0/2

  GET /llms-full.txt returned HTTP 404

  fix → Add /llms-full.txt with expanded inline docs content so agents can load everything in one fetch.

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✗JSON-LD structured datarequired0/4

  No application/ld+json blocks found on homepage and pricing page

  fix → Embed Organization + WebSite JSON-LD on your homepage (name, url, logo, sameAs) and Product/Offer JSON-LD on pricing.

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✓Markdown content negotiationrecommended3/3

  https://docs.amika.dev/ returns markdown for `Accept: text/markdown` (content-type text/markdown)

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• ✓Developer resource discoverabilityrecommended3/3

  Search "Amika API documentation" cited your own domain: https://docs.amika.dev/llms.txt, https://docs.amika.dev/reference/api-reference, https://docs.amika.dev/quickstart

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• ✗OpenAPI spec discoverablerequired0/5

  No OpenAPI spec found: checked docs-page links and /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /docs/openapi.json, and api-subdomain locations

  fix → Publish your OpenAPI spec at /openapi.json and link it from docs — it's the single highest-leverage artifact for agent integration.

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✓Docs discoverablerequired4/4

  Docs found at https://docs.amika.dev/ (via homepage link, 2886 chars of readable text)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ◐MCP server discoveryrequired2.5/5

  MCP evidence found only as a mention in docs page (https://docs.amika.dev/): "MCP server" — no well-known server card

  fix → Publish /.well-known/mcp/server-card.json describing your MCP endpoint so agents can autodiscover it. Evidence found: docs page (https://docs.amika.dev/).

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• ✓npm SDKrecommended2/2

  Official npm package "@amika/sdk" (verified via README mentions the domain): latest 0.10.0 published 2026-07-16

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• ✗PyPI SDKrecommended0/2

  No official PyPI SDK found: probed 4 candidate(s) (amika, amika-sdk, amikaapi, amika-python)

  fix → Publish an official Python SDK (suggest "amika") with your domain in the project URLs so agents can verify it's official.

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No OpenAPI spec found — nothing to lint

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ✗Docs qualityrecommended0/3

  Docs at https://docs.amika.dev/ scored clarity 3/5, completeness 2/5, runnable examples 1/5, agent-friendliness 2/5 (mean 2.0/5)

  fix → Docs scored 1/5 on runnable examples. The documentation is an introduction and table of contents, lacking the actual detailed instructions and API references needed for an agent to integrate.

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• ✓Quickstart / getting startedrecommended2/2

  Quickstart found: https://docs.amika.dev/quickstart (linked from https://docs.amika.dev/) returns 200 with a code block

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No MCP endpoint known — tool lint requires a tools/list

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://amika.dev/ upgrades to https in 1 hop(s), 2 redirect(s) total, final HTTP 200; HSTS present

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ✓Response speed & weightrequired1/1

  Homepage TTFB 97ms, payload 163KB, Content-Encoding: br

  Measured homepage TTFB, payload size, and compression

  report issue
• ✗security.txtrecommended0/1

  https://amika.dev/.well-known/security.txt returned HTTP 404

  fix → Publish RFC 9116 /.well-known/security.txt with a Contact and a future Expires.

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• ✗OAuth authorization server metadatarecommended0/3

  Neither /.well-known/oauth-authorization-server nor /.well-known/openid-configuration resolved (HTTP 404 / HTTP 404)

  fix → Serve RFC 8414 metadata at /.well-known/oauth-authorization-server with PKCE (S256) and a registration_endpoint so agents can self-onboard.

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• ✗OAuth protected resource metadatarecommended0/2

  No RFC 9728 metadata: https://amika.dev/.well-known/oauth-protected-resource → HTTP 404

  fix → Serve RFC 9728 metadata at /.well-known/oauth-protected-resource naming your authorization servers so agents can discover how to authenticate.

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• ◐Auth documentationrecommended1/2

  Auth page https://docs.amika.dev/guides/github-authentication exists but contains no code examples

  fix → Add a runnable example (key creation → header format → example call) to your auth docs — agents follow it literally.

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ✓Pricing discoverablerequired5/5

  Pricing page found at https://www.amika.dev/pricing (via homepage link) with legible price signals ("$0 / moTry Amika with your own").

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• ✓Machine-readable pricingrecommended5/5

  LLM extracted 3 numerically-priced plan(s) from https://www.amika.dev/pricing at confidence 1.00: Free $ 0/mo; Developer $ 30/mo; Team $ 100/mo; Enterprise (contact sales).

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✗x402 payment supportbonusrecommended0/2

  /.well-known/x402 returned HTTP 404. No x402 support detected (bonus check — absence costs nothing).

  fix → Support x402: serve payment requirements at /.well-known/x402, or answer unauthenticated API calls with HTTP 402 plus an x402 payment-requirements payload (x402Version, accepts[]).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned docs page (https://docs.amika.dev/); /.well-known/ap2 returned HTTP 404.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned docs page (https://docs.amika.dev/); /.well-known/acp returned HTTP 404.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned docs page (https://docs.amika.dev/).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• —MCP handshake & tools listrequiredna

  No MCP endpoint known — nothing to handshake with

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✗NLWeb endpointemerging0/1

  No NLWeb endpoint detected: /.well-known/nlweb.json returned HTTP 404 (text/html); GET /ask?query=hello returned HTTP 404 (text/html)

  fix → Consider exposing an NLWeb /ask endpoint (and /.well-known/nlweb.json) for conversational access to your content.

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ◐Semantic HTML structurerequired1.5/3

  4/6 semantic signals present on the homepage (missing: <header>/<footer>, text-to-markup ratio ≥ 0.10)

  fix → Add the missing structure: <header>/<footer>, text-to-markup ratio ≥ 0.10. Agents parse structure, not pixels.

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 9349 chars of visible text without JavaScript

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✓Accessibility basicsrequired2/2

  Homepage accessibility: 5/5 checks passed

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue