Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
Preparing the stored Is Agentic score
promptmetrics.dev
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 16 applicable checks
Strong
Weighted across 12 applicable checks
Strong
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
Make your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.
Return standard rate-limit headers on your API responses (the RFC RateLimit headers, plus Retry-After on a 429) so agents can self-throttle in real time, and document the conventions alongside your API.
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
Checks are grouped by relevance for Docs & content sites.
7634 chars, semantic headings (1 H1 + 8 H2s + 13 H3s), 24.1% content ratio
Site accessible to 6 AI agent user-agents
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 1 checked page
OpenAPI spec found at https://promptmetrics.dev/openapi.json (version: 3.1.0)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
All major AI crawlers can reach the site: ChatGPT-User, ClaudeBot, Google-Extended, ora-agent, DeepSeekBot.
API returns JSON error responses (200 at https://api.promptmetrics.dev)
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
Name search surfaced no pages on promptmetrics.dev, although developer resources exist on the site (API docs, OpenAPI spec, MCP server) - weak search indexing or transient search noise
How to pass
Make your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.
"PromptMetrics" search returned 8 results but domain did not appear - brand may be too generic or not indexed
How to pass
Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
Valid sitemap found at https://www.promptmetrics.dev/sitemap.xml with 155 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 blocks)
API/docs link found on homepage and resolves: /developers
When-to-use guidance found in llms.txt
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 3 measured pages fit an agent context budget (largest ~2K tokens)
Code fences balanced across 1 markdown document
Developer portal found at /developers
REST API documentation found at https://www.promptmetrics.dev/developers. Best-of-protocols score: 7/7.
MCP server connected via Streamable HTTP - promptmetrics v1.0.0 (protocol 2025-11-25)
REST rate-limit headers documented in OpenAPI spec, but not observed on a live response (API requires authentication).
How to pass
Return standard rate-limit headers on your API responses (the RFC RateLimit headers, plus Retry-After on a 429) so agents can self-throttle in real time, and document the conventions alongside your API.
OpenAPI defines a typed error schema in components.schemas and 4xx/5xx responses reference it
API versioning found (URL versioning (servers or paths)) but no deprecation or sunset policy detected - add Sunset/Deprecation headers or a deprecation policy page
How to pass
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
CLI tool mentioned in llms.txt
How to pass
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
100% of operations define typed response schemas, 100% use application/json
REST: agent-friendly schema (6 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 6/6 ops with IDs, 6/6 with typed schemas
Wikidata Q140461989 (PromptMetrics) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage
How to pass
Establish a Wikipedia article and a Wikidata entity for your brand, with the domain set as the official website (Wikidata property P856) and a corresponding external link on Wikipedia. Wikipedia is the largest single source of citations in ChatGPT and a primary input to Knowledge Graphs across Google, Bing, and LLM training data. Earn third-party press coverage first to satisfy notability, then draft the article with cited references rather than self-promotion.
NPM package found: @promptmetrics/sdk - "Official TypeScript/JavaScript SDK for PromptMetrics API - Manage and execute LLM prompts with version control, monitoring, and analytics"
MCP server referenced in llms.txt
Rich agent mode view at ?mode=agent with 4 agent signals and navigation links
Homepage markdown fallback works (https://promptmetrics.dev/index.md). No additional same-host content pages were discovered to sample.
79% of 155 sampled sitemap entries carry lastmod; newest is 1 day(s) old
Found the llms.txt at https://promptmetrics.dev/llms.txt.
The llms.txt is well-formatted with markdown links, but at 36,387 characters it exceeds the 30,000-character recommendation for a navigation index.
How to pass
Format your llms.txt as a navigation index: start with a markdown heading, include markdown links to deeper resources, and keep it under 30,000 characters. If you have more to say, move long-form content into /llms-full.txt or per-section files (e.g. /docs/llms.txt, /api/llms.txt) and link to them from the main index.
Strong entity linking via sameAs: github.com, linkedin.com
Some extended schema types found: ProfessionalService - add FAQPage, Service, or AggregateRating for full coverage
How to pass
Expand your JSON-LD beyond Organization/WebSite. Add FAQPage for common questions, Service or Product for offerings, AggregateRating or Review for social proof, and BreadcrumbList for navigation context.
All 5 probed llms.txt links resolve to real content
Frontmatter with title + description and canonical on /developers.md
Path-suffix markdown docs served with text/markdown content-type: /developers.md, /index.md
All 11 tools on other MCP have detailed descriptions (>= 20 chars)
9/11 tools on other MCP have parameter schemas, 9 with required fields
other MCP identifies as "promptmetrics" v1.0.0 with instructions
other MCP exposes 11 tools - substantial tool surface
All 11 tool names follow consistent convention, descriptive, and non-generic
other MCP returns structured JSON-RPC errors with code and message
other MCP uses modern Streamable HTTP transport
Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /.webmcp/bridge.js).
SDK package found only in npm
How to pass
Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json repository/homepage, PyPI Home-Page or project_urls, RubyGems homepage_uri) - this is how agents verify the package is your official SDK.
Batch/bulk operations referenced in llms.txt
How to pass
Offer a batch endpoint that accepts an array of operations in one request, documented in your spec, so an agent acting on many items can do it in bulk instead of looping one call at a time.
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
68 native controls, 0 non-native div-soup affordances (100% native).
68/68 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does promptmetrics.dev do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does promptmetrics.dev do and who is it for? Explain it back to me.
7 steps1 reasoning step
The agent successfully gathered a complete overview of PromptMetrics from five fetched pages, obtaining clear answers on what they do, their target audience, service tiers, and differentiation. The site was moderately navigable via direct links from the homepage, though it lacked published pricing details and case studies, which the agent identified as gaps but could not fill from available content.