primitive.dev

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

• ✓Sitemap present & freshrequired4/4

  Sitemap at https://www.primitive.dev/sitemap.xml: 83 entries, freshest <lastmod> 2026-08-17 (0 days ago)

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

  spec ↗report issue
• ◐Brand search discoverabilityrequired2/4

  Search "Primitive" cited primitive.dev (https://www.primitive.dev/, https://www.primitive.dev/docs, https://www.primitive.dev/signup), but search "Primitive agent tools" did not cite your domain

  fix → Your domain doesn't surface when agents search "Primitive agent tools". Strengthen brand pages, structured data, and third-party citations (docs portals, GitHub, directories).

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

  report issue
• ✓MCP registry listingsrecommended4/4

  /.well-known/mcp/server-card.json serves JSON; searched "primitive.dev" and "Primitive": listed in official MCP registry, Smithery (2 of 3 reachable registries)

  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 & parseablerequired2/2

  /robots.txt parses: 14 User-agent group(s), 1 Sitemap line(s)

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

  spec ↗report issue
• ◐AI crawler policyrequired2/5

  robots.txt blocks 2 of 12 AI crawler user-agents from /: CCBot, Bytespider

  fix → robots.txt blocks CCBot, Bytespider. Add explicit `User-agent: <bot>` / `Allow: /` groups for AI agents you welcome.

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

  report issue
• ✓Content Signals directivesemerging2/2

  14 valid Content-Signal line(s) in robots.txt (e.g. `Content-Signal: search=yes, ai-input=yes, ai-train=no`)

  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 (193160 bytes)

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

  report issue
• ✓agents.mdrecommended3/3

  Found https://primitive.dev/agents.md: 7381 chars of markdown with 10 heading(s)

  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: "Primitive provides email infrastructure specifically designed for AI agents, enabling them to send and receive emails, manage email addresses, and communicate with other agents or people via a simple API.")

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

  report issue
• ✓OpenGraph / social metadatarecommended2/2

  Homepage has og:title, og:description, and og:image (twitter:card="summary_large_image" present)

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

  spec ↗report issue
• ✓llms.txtrecommended4/4

  /llms.txt is valid llmstxt.org shape: H1 "primitive.dev", 72 markdown link(s)

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

  spec ↗report issue
• ✓llms-full.txtbonusrecommended2/2

  /llms-full.txt serves 20099 chars of markdown

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

  spec ↗report issue
• ✓JSON-LD structured datarequired4/4

  16 JSON-LD block(s) on homepage and pricing page (types: Organization, WebSite, SoftwareApplication, Service, FAQPage, WebPage, BreadcrumbList); Organization block is well-formed

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

  spec ↗report issue
• ✓Markdown content negotiationrecommended3/3

  https://primitive.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 "Primitive API documentation" cited your own domain: https://www.primitive.dev/docs/webhook-payload

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

  report issue
• ✓OpenAPI spec discoverablerequired5/5

  OpenAPI spec found at https://primitive.dev/openapi.json (version 3.1.0)

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

  spec ↗report issue
• ✓Docs discoverablerequired4/4

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

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

  report issue
• ✓MCP server discoveryrequired5/5

  Valid MCP server card at https://primitive.dev/.well-known/mcp/server-card.json: name "primitive", endpoint https://registry.modelcontextprotocol.io/v0/servers?search=dev.primitive%2Femail

  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 "primitive" (verified via homepage https://primitive.dev): latest 1.22.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) (primitive, primitive-sdk, primitiveapi, primitive-python) — found but not domain-verified: primitive

  fix → Publish an official Python SDK (suggest "primitive") 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 & qualityrecommended3/3

  Spec at https://primitive.dev/openapi.json: 7/7 quality criteria passed (94 paths, 127 operations)

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ✓Docs qualityrecommended2.4/3

  Docs at https://docs.primitive.dev/docs scored clarity 4/5, completeness 3/5, runnable examples 5/5, agent-friendliness 4/5 (mean 4.0/5)

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

  report issue
• ✓Quickstart / getting startedrecommended2/2

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

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

  report issue
• —MCP tool qualityrecommendedna

  No tools listed by the MCP endpoint — nothing to lint

  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://primitive.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 120ms, payload 189KB, Content-Encoding: gzip

  Measured homepage TTFB, payload size, and compression

  report issue
• ✓security.txtrecommended1/1

  Valid security.txt at https://primitive.dev/.well-known/security.txt: Contact mailto:contact@corp.primitive.dev, Expires 2027-05-01

  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 metadatarecommended3/3

  Valid RFC 8414 metadata at https://primitive.dev/.well-known/oauth-authorization-server: issuer https://www.primitive.dev, PKCE S256, dynamic client registration at https://www.primitive.dev/oauth/register

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

  spec ↗report issue
• ✓OAuth protected resource metadatarecommended2/2

  Valid RFC 9728 metadata at https://primitive.dev/.well-known/oauth-protected-resource: resource https://api.primitive.dev/v1, 1 authorization server(s) (https://www.primitive.dev)

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

  spec ↗report issue
• ✓Auth documentationrecommended2/2

  Auth documentation found at https://primitive.dev/auth.md (8241 chars, with code examples)

  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.primitive.dev/pricing (via path probe) with legible price signals ("$0/moIncludes $5/mo of usage c").

  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.primitive.dev/pricing at confidence 1.00: Developer USD 0/month; Power USD 13/month; Platinum USD 299/month.

  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. API probe GET https://api.primitive.dev/v1/account returned HTTP 401 without x402 payment requirements. 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 llms.txt, agents.md, docs page (https://docs.primitive.dev/docs), OpenAPI spec (https://primitive.dev/openapi.json); /.well-known/ap2 returned HTTP 200.

  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 Protocolemerging1/1

  Agentic Commerce Protocol evidence found: llms.txt mentions "checkout_sessions".

  Scanned docs and specs for agentic checkout endpoints

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

  No UCP/MPP hints found — scanned llms.txt, agents.md, docs page (https://docs.primitive.dev/docs), OpenAPI spec (https://primitive.dev/openapi.json).

  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 listrequired0/4

  MCP endpoint https://registry.modelcontextprotocol.io/v0/servers?search=dev.primitive%2Femail failed handshake: HTTP 404

  fix → MCP endpoint https://registry.modelcontextprotocol.io/v0/servers?search=dev.primitive%2Femail failed handshake: HTTP 404. Support streamable HTTP with protocol version negotiation; if auth-gated, return RFC 9728 metadata in WWW-Authenticate.

  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 endpointemerging1/1

  GET /ask?query=hello returned HTTP 200 with a JSON response

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

  spec ↗report issue
• ✓Semantic HTML structurerequired3/3

  5/6 semantic signals present on the homepage (missing: <nav> landmark)

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

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 27434 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
• ✓WebMCPemerging1/1

  WebMCP evidence on homepage: navigator.modelContext reference

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue