yiminyang.dev
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
yiminyang.dev
Preparing the stored Is Agentic score
yiminyang.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
Blocked
Weighted across 8 applicable checks
Blocked
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
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.
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.
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.
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
Checks are grouped by relevance for Docs & content sites.
1667 chars, semantic headings (1 H1 + 2 H2s + 8 H3s), 6.9% 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)
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.
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 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 HTTP 404 with markdown guidance for agents - the strongest 404 contract
Name search surfaced no pages on yiminyang.dev, although developer resources exist on the site (API docs, 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.
yiminyang.dev appears once in brand-name search results for "Yi Min Yang" (position #7 out of 10)
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.yiminyang.dev/sitemap.xml with 70 entries
Rich JSON-LD identity: Person with name, description, url, and sameAs/jobTitle (2 blocks)
API/docs link found on homepage (/api/mcp) but page is thin or unreachable
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
All metadata signals present: canonical URL, lang="en", og:image, og:type
All trust anchor pages verified: About, Contact, Privacy
All 7 measured pages fit an agent context budget (largest ~1K tokens)
Code fences balanced across 2 markdown documents
Developer portal found at /developers
REST API documentation found at https://www.yiminyang.dev/api/mcp. Best-of-protocols score: 7/7.
MCP mentioned at https://yiminyang.dev/developers.md but no standard manifest endpoint 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 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.
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.
MCP server referenced in llms.txt
RFC 8288 Link header advertises: service-desc, alternate(markdown)
97% of 70 sampled sitemap entries carry lastmod; newest is 7 day(s) old
Found the llms.txt at https://yiminyang.dev/llms.txt.
The llms.txt is well-formatted: 125 lines with markdown links, 8,022 characters in total.
Strong entity linking via sameAs: linkedin.com, github.com
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://www.yiminyang.dev/index.html.md serves markdown
Path-suffix markdown docs served with text/markdown content-type: /developers.md
MCP server card found at https://yiminyang.dev/.well-known/mcp/server-card.json but missing tools[]
How to pass
Publish a server card at /.well-known/mcp/server-card.json describing your MCP server. Required fields: name, description, version, serverUrl, tools[]. This lets agents preview your server before opening a transport connection.
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
39 native controls, 0 non-native div-soup affordances (100% native).
39/39 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does yiminyang.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 yiminyang.dev do and who is it for? Explain it back to me.
16 steps4 reasoning steps
The agent successfully understood yiminyang.dev by retrieving and synthesizing content from six markdown/text sources, assembling a coherent picture of the site's purpose, audience, pricing, and differentiation. The site was navigable via direct markdown URLs and predictable routing, though the agent had to combine fragments rather than encounter a single authoritative overview document. Key gaps remain: the MCP server's purpose and usage instructions are underdocumented, the primary call-to-action is unclear, and pricing/services are not explicitly stated (though correctly inferred as free).