hazemonitor.com
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
hazemonitor.com
Preparing the stored Is Agentic score
hazemonitor.com
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
Needs work
Weighted across 12 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Build an MCP (Model Context Protocol) server exposing your API as tools. Use Streamable HTTP transport for full score. This lets Claude, ChatGPT, and other AI agents call your product natively.
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.
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.
Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
Checks are grouped by relevance for App sites.
Homepage: 8840 chars, semantic headings (1 H1 + 9 H2s), 18.3% content ratio. 4 of 4 sampled inner pages have text without JavaScript.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 10 checked pages
All 4 sampled pages are publicly readable (4 with substantive content)
OpenAPI spec found at https://hazemonitor.com/openapi.json (version: 3.1.0)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
API returns JSON error responses (400 at GET https://hazemonitor.com/api/regional-air-quality, an operation in the OpenAPI spec)
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://hazemonitor.com/sitemap.xml with 272 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 blocks)
Documentation found at /developers but not linked from homepage
How to pass
Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
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 6 measured pages fit an agent context budget (largest ~2K tokens)
REST API documentation found at https://hazemonitor.com/developers. Best-of-protocols score: 7/7.
Onboarding signals described but not verified live: sandbox/test environment, zero-auth access
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
No MCP server or manifest found
How to pass
Build an MCP (Model Context Protocol) server exposing your API as tools. Use Streamable HTTP transport for full score. This lets Claude, ChatGPT, and other AI agents call your product natively.
No REST rate-limit headers found on probed endpoints
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
No API versioning strategy found - add URL path versioning (/v1/, /v2/) or a versioned header parameter in your OpenAPI spec
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.
No CLI tool found
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 (9 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 9/9 ops with IDs, 7/9 with typed schemas
Agent discovered 1 developer-resource type by name (developer portal) across 1 page
Rich agent mode view at ?mode=agent with 4 agent signals and navigation links
Found the llms.txt at https://hazemonitor.com/llms.txt.
The llms.txt is well-formatted: 28 lines with markdown links, 4,494 characters in total.
When-to-use guidance found in llms.txt
Some extended schema types found: ItemList - add 2 more types that match what the homepage shows, for full coverage
How to pass
Add 2 more JSON-LD types that match what your homepage shows. Only add a type where the page shows that content.
All 5 probed llms.txt links resolve to real content
Code fences balanced across 2 markdown documents
Developer portal found at /developers
Path-suffix markdown docs served with text/markdown content-type: /developers.md
Server HTML is a well-structured document (main=true, landmarks=2/4, h1=1, maxHeadingSkip=1).
176 native controls, 0 non-native div-soup affordances (100% native).
176/176 interactive elements have a computable accessible name (100%).
1/1 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does hazemonitor.com 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 hazemonitor.com do and who is it for? Explain it back to me.
8 steps1 reasoning step1 search
The agent successfully retrieved core information about Haze Monitor's service, target users, and differentiation from two accessible pages (homepage and /about), but could not find pricing information—which either doesn't exist on the site or isn't published. The site offered minimal structural navigation, forcing the agent to guess at URL paths (/features, /pricing, /api, /stations), all of which returned 404s.