useblume.dev
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
useblume.dev
Preparing the stored Is Agentic score
useblume.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 17 applicable checks
Ready with gaps
Weighted across 12 applicable checks
Strong
Weighted across 3 applicable checks
Strong
Weighted across 3 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
Checks are grouped by relevance for Docs & content sites.
14297 chars, semantic headings (1 H1 + 10 H2s + 5 H3s), 6.6% content ratio
Site accessible to 6 AI agent user-agents
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
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.
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
Valid sitemap found at https://useblume.dev/sitemap.xml with 294 entries
Rich JSON-LD identity: SoftwareApplication with name, description, url, and category/offers (1 block)
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema found but missing: contactPoint, address
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
Only About page verified - missing: Contact, Privacy
How to pass
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
All 7 measured pages fit an agent context budget (largest ~15K tokens)
ARD catalog valid at /.well-known/ard.json (spec 1.0) - 6/6 entries
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 6/6 entries
All 6 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ard.json)
Agent discovered 1 developer-resource type by name (API docs) across 4 pages
Agent config found: github.com/haydenbleasel/blume/blob/main/AGENTS.md
MCP manifest has name and description but no icon at /.well-known/mcp/server-card.json
How to pass
Give your MCP server-card (at /.well-known/mcp/server-card.json) a display name, an icon or logo, and a description - all three together are what reads as a complete, branded listing agents can present.
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 3 skill(s)
Index v0.2.0 conformant; verified SHA-256 of "blume" (2 other skills present)
MCP server discoverable at standard path https://useblume.dev/.well-known/mcp.json
Rich agent mode view at ?mode=agent with 8 agent signals and navigation links
RFC 8288 Link header advertises: describedby, service-desc, api-catalog, alternate(markdown)
Partial markdown fallback support. Homepage (https://useblume.dev/index.md) returns markdown, but 1 of 3 sampled content pages do not: https://useblume.dev/docs/advanced/api-reference.md. To earn full credit, serve a .md twin for each content page (e.g. /docs/auth -> /docs/auth.md) with text/markdown content-type or a heading-led non-HTML body.
How to pass
Let agents fetch markdown by appending .md to page URLs. Required for any credit: serve a markdown homepage at /index.md. For full credit (2/2): also serve a .md twin for each content page (e.g. /docs/auth -> /docs/auth.md). Content-Type should be text/markdown and the body should start with a top-level heading (not HTML).
97% of 294 sampled sitemap entries carry lastmod; newest is 0 day(s) old
Found the llms.txt at https://useblume.dev/llms.txt.
The llms.txt is well-formatted with markdown links, but at 60,619 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.
Pricing structured data (schema.org/Offer) found
API/docs link found on homepage and resolves: /docs
When-to-use guidance found in llms.txt
Entity linking to github.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your Wikipedia page, Wikidata entry, GitHub org, and social profiles. This helps AI disambiguate your brand from similarly named entities.
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://useblume.dev/index.md serves markdown
Code fences balanced across 1 markdown document
OpenAPI spec found at https://useblume.dev/openapi.json (version: 3.1.0)
Developer portal found at /docs
api-catalog linkset[0] has no 'item' entries
How to pass
Publish an API catalog at /.well-known/api-catalog per RFC 9727. Serve it with Content-Type: application/linkset+json;profile="https://www.rfc-editor.org/info/rfc9727" and include a 'linkset' array with item entries pointing to your OpenAPI specs and service descriptions.
Path-suffix markdown docs served with text/markdown content-type: /index.md
All 4 tools on docs MCP have detailed descriptions (>= 30 chars)
4/4 tools on docs MCP have parameter schemas
docs MCP exposes 4 tools - consider consolidating to keep agent attention focused on retrieval
How to pass
Expose 3+ tools via your MCP server's tools/list endpoint. Cover your core API surface - agents need tools for read, write, and search operations.
All 4 tool names follow consistent convention, descriptive, and non-generic
REST API documentation found at https://useblume.dev/docs. Best-of-protocols score: 7/7.
Zero-auth service - documented as open with no authentication required, and API operations responded without credentials
Zero-auth service - no scoping needed, all endpoints are openly accessible to agents
docs MCP is public - correct posture for documentation surface
Zero-friction onboarding verified live: keyless API surface fetched without credentials - no signup step exists
MCP server connected via Streamable HTTP - Blume v2.0.0 (protocol 2025-11-25)
docs MCP returns error for invalid tool call but missing structured code or message
How to pass
Return structured JSON-RPC errors (with code and message) when agents call invalid tools or pass bad arguments. Don't crash or return empty responses.
docs MCP uses modern Streamable HTTP transport
Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /_astro/WebMcp.astro_astro_type_script_index_0_lang.CH0DgukK.js).
API returns JSON error responses (404 at https://useblume.dev/api/v1/orank-probe-test)
OpenAPI uses application/problem+json (RFC 7807) for 4xx/5xx responses
Offset/page-based pagination found in OpenAPI spec - consider migrating to cursor-based pagination for agent friendliness
How to pass
Use a consistent, documented pagination shape on your list endpoints (cursor-based preferred) and define the pagination fields in your OpenAPI response schemas, so agents can page through results without guessing the shape.
CLI tool mentioned at https://useblume.dev/index.md
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, 67% use application/json
docs MCP: 4/4 tools have behavioral annotations
MCP server card found at https://useblume.dev/.well-known/mcp/server-card.json (4 tools advertised)
MCP server exposes 284 resource(s) via resources/list
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
150 native controls, 4 non-native div-soup affordances (97% native).
150/150 interactive elements have a computable accessible name (100%).
2/2 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (9 operations, 100% with operationIds, 100% documented by description or summary)
Partial compatibility: 9/9 operationIds, 4/9 typed schemas
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
25/25 resources read with valid mimeType and non-empty content
What does useblume.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 useblume.dev do and who is it for? Explain it back to me.
22 steps10 reasoning steps1 search
The agent successfully understood Blume's core offer, positioning, and business model by retrieving three markdown documentation pages. The site was highly navigable and agent-friendly: Blume publishes its docs in machine-readable markdown format (via .md file paths), making it straightforward to extract structured information about what the product does, who it's for, how it's priced, and how it differs from alternatives. The agent could not find information about community adoption or interactive AI feature demos, but these were gaps in what the site publishes rather than navigation failures.