Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
Preparing the stored Is Agentic score
mm.dreamineering.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.
Ready with gaps
Weighted across 17 applicable checks
Blocked
Weighted across 8 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist - it must print 404.
Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.
On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.
Checks are grouped by relevance for Docs & content sites.
Only 1207 chars of text content, no H1 tag - agents see limited content
How to pass
Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.
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 (2 with substantive content)
No OpenAPI/Swagger specification found
How to pass
Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Not acceptmarkdown.com compliant: Content-Type claims markdown but body opens with HTML doctype/tag
How to pass
On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.
API does not return JSON error responses (or no API detected)
How to pass
Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.
Nonexistent paths return a real HTTP 404. For full credit, include a short markdown body (site map links, where to look next) so agents can recover.
How to pass
Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist - it must print 404.
Agent searched for "dreamineering" developer resources but found nothing relevant
How to pass
Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, 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.
mm.dreamineering.com appears at position #2 in a clean brand-name search for "Dreamineering" (2 total matches)
Valid sitemap found at https://mm.dreamineering.com/sitemap.xml with 2594 entries
Content efficiency: 16.97% (3046 text chars / 18KB HTML)
JSON-LD Organization with name + description - add url and sameAs/logo/address for full score
How to pass
Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.
No public API or documentation page linked from homepage
How to pass
Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
When-to-use guidance found in llms.txt
2/4 metadata signals present - missing: og:image, og:type
How to pass
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
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.
All trust anchor pages verified: About, Contact, Privacy
All 6 measured pages fit an agent context budget (largest ~3K tokens)
Code fences balanced across 1 markdown document
No developer portal found
How to pass
Create a developer portal at /developers with API keys, documentation, quickstart guides, and a sandbox environment.
REST API documentation found at https://mm.dreamineering.com/developers/dreamineering.md. Best-of-protocols score: 7/7.
CLI tool found on PyPI: mm-cli
No API schema detected
How to pass
Make your API spec self-describing: a unique operationId and a description on every operation, typed parameters, and response schemas. For GraphQL, a fully typed schema with a documented cost or rate limit reads best.
No API spec found - function calling requires discoverable endpoints
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
RFC 8288 Link header advertises: service-desc
Found the llms.txt at https://mm.dreamineering.com/llms.txt.
The llms.txt is well-formatted: 58 lines with markdown links, 3,853 characters in total.
All 5 probed llms.txt links resolve to real content
Returns markdown when requested via Accept header
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
32 native controls, 0 non-native div-soup affordances (100% native).
32/32 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does mm.dreamineering.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 mm.dreamineering.com do and who is it for? Explain it back to me.
17 steps1 reasoning step1 search
The agent assembled a comprehensive overview of Dreamineering's mission, framework, and philosophy by navigating the site's playbook and nav structure, but could not find pricing information or clarify the business model and service offering. The site published its core message through machine-readable artifacts (llms.txt, agent.json) and interconnected documentation pages, making the conceptual positioning clear; however, transactional and commercial details were absent or inaccessible, leaving the agent unable to fully answer the "how it's priced" portion of the task.