moss.dev

Visit

Agent readiness reportDeveloper Tools

72/100B · Good

  • Discovery18/20
  • Access27/30
  • Usability20/40
  • PaymentsBonus
Rank
#149of 360
In Developer Tools
#16of 29
Last 7 days
-22 points · -26 places
Scanned
Nov 172026
What the scan found
Access is the strongest area, with a published OpenAPI specification and developer portal, while an MCP server or manifest and support for the assessed OAuth version are missing.

Where the score comes from

65 of 90 points

How moss.dev scores on each of the four questions agents ask.

Discovery18/20

Access27/30

Usability20/40

Paymentsnot scored yet

Strongest

Discovery

ARD discovery and Wikipedia / Wikidata entity presence are missing.

18/20

Most to gain

Usability

Public API with reachable endpoints, OAuth 2.0 support, and 16 more are missing.

20/40

Most to gain

Access

Content without JavaScript, MCP well-known discovery, and 3 more are missing.

27/30

Not scored yet

Payments ( bonus )

6 checks partly met. Counts when scoring opens.

—

Agent path

How an agent movedthrough the site

We asked an agent a question about moss.devand recorded every request it made.

Mmoss.devAnsweredRan Nov 4, 2026

Question

I want to start using Moss (moss.dev). Find its setup and getting-started guide.

5
Steps
31s
Duration
4
Pages opened
0
Failed

Every address the agent typed itself loaded. Every link it followed loaded.

Where the address came fromPage it asked forWhat came backNamed in the question1 stepA link on a page it read2 stepsTyped by the agent1 stepSearched the web1 step“moss.dev setup getting started guide”“moss.dev setup getting started g…moss.dev /moss.dev //docs/docs/docs/api-reference/v1/getting-started/introduction/docs/api-reference/v1/getting-st…/docs/start/quickstart/docs/start/quickstartRead4 stepsDidn’t load0 stepsResults1 step
  1. 2moss.dev /Named in the question → Read
  2. 3/docsA link on a page it read → Read
  3. 4/docs/api-reference/v1/getting-started/introductionA link on a page it read → Read
  4. 5/docs/start/quickstartTyped by the agent → Read
5/5 steps
StepsHow it found itCame back as
Step 5 of 5
docs.moss.dev/docs/start/quickstart
How it got here
Typed by the agent
Response
200
Came back as
Markdown

How it found each page

Named in the question1

A link on a page it read2

Typed by the agent1

A search result0

What it reached

Home pageStep 2

PricingNever reached

DocsStep 3

Its answer

Answers aren’t shown publicly

See what agents answer about your own site.

Run agents on your site and read every answer, with every page they opened.

Get started →

Free to start. No card.

Discovery18 of 202 to fix4 passed
ARD discoveryRequired0 / 1
Wikipedia / Wikidata entity presenceRecommended0 / 4
Developer resource discoverabilityRecommended3 / 3
Brand name discoverabilityRequired3 / 3
robots.txt AI crawler policyRequired2 / 2
NPM/PyPI SDK packageRecommended1 / 1
+ 9 checks not in the score
AI Catalog discoveryRecommendedNot counted
ARD entry validityRecommendedNot counted
ARD trust manifestRecommendedNot counted
Category share of voiceRecommendedNot counted
Listed in MCP registriesRecommendedNot counted
Agent platform configsEmergingNot counted
Agent Plugins manifestEmergingNot counted
Registry brandingEmergingNot counted
ChatGPT app listedRecommendedNot counted
Access27 of 302 to fix3 partly22 passed
MCP well-known discoveryRecommended0 / 2
Trust anchor pagesRequired0 / 2
Content without JavaScriptRequired1 / 3
Page token budgetRecommended0 / 1
API catalog (RFC 9727)Required1 / 2
Sitemap existsRequired2 / 2
Not blocked by bot detectionRequired2 / 2
Agent discovery fileRequired2 / 2
A2A / agent-cardRecommended2 / 2
HTTP Link headers (RFC 8288)Required1 / 1
Sitemap freshness (lastmod)Recommended1 / 1
robots.txt agent-user policyRequired2 / 2
llms.txt existsRequired1 / 1
llms.txt formattingRecommended2 / 2
JSON-LD structured dataRequired4 / 4
Pricing info accessibleRequired3 / 3
Public API/docs linked from homepageRequired3 / 3
JSON-LD entity linking (sameAs)Recommended2 / 2
Metadata completenessRequired2 / 2
Organization schema completenessRecommended2 / 2
Schema type breadthRecommended2 / 2
llms.txt links resolveRecommended2 / 2
Redirect hygieneRecommended1 / 1
OpenAPI spec publishedRequired7 / 7
Developer portalRecommended6 / 6
Markdown content negotiation (acceptmarkdown.com)Recommended1 / 1
Agent crawler reachabilityRecommended2 / 2
+ 15 checks not in the score
Agent Skills index conformance (v0.2.0)EmergingNot counted
Listed on skills.shEmergingNot counted
pricing.md existsEmergingNot counted
NLWeb Schema FeedsEmergingNot counted
Agent mode viewEmergingNot counted
Markdown URL fallbackEmergingNot counted
Modular llms.txt per product areaEmergingNot counted
Agent instruction / when-to-useRequiredNot counted
Skills.sh skill qualityEmergingNot counted
Markdown alternate linkEmergingNot counted
Markdown frontmatter metadataEmergingNot counted
Code fence validityEmergingNot counted
Content behind authRecommendedNot counted
Markdown agent docsEmergingNot counted
Bot-UA markdown servingEmergingNot counted
Usability20 of 4013 to fix5 partly8 passed
OAuth 2.0 supportRequired0 / 5
auth.md existsRequired0 / 2
auth.md structureRecommended0 / 2
Agent auth WWW-Authenticate hintRecommended0 / 1
agent_auth endpoints reachableRecommended0 / 2
MCP server / manifestRequired0 / 6
WebMCP supportRequired0 / 5
Rate limit response headersRecommended0 / 2
Idempotency-Key supportRecommended0 / 3
REST typed error modelRecommended0 / 3
Sandbox / test environmentRecommended0 / 2
REST batch / bulk endpointRecommended0 / 2
Accessible document structureRecommended0 / 3
Public API with reachable endpointsRequired3 / 7
Agent onboarding frictionRecommended1 / 2
Agent auth discovery metadataRecommended1 / 3
REST versioning / deprecation policyRecommended2 / 3
Agent-friendly 404sRecommended1 / 2
Scoped permissionsRecommended5 / 5
OAuth Protected Resource metadata (RFC 9728)Required2 / 2
JSON error responsesRequired4 / 4
REST async-job patternRecommended2 / 2
CLI tool availableRecommended3 / 3
Accessible names on controlsRecommended2 / 2
API schema complexity analysisRecommended2 / 2
Function calling compatibilityRecommended2 / 2
+ 36 checks not in the score
MCP tool descriptionsRecommendedNot counted
MCP parameter schemasRecommendedNot counted
MCP server identityRecommendedNot counted
MCP tool listingRecommendedNot counted
MCP tool namingRecommendedNot counted
MCP auth mechanismRecommendedNot counted
MCP OAuth metadataRecommendedNot counted
MCP PKCE S256 supportRecommendedNot counted
Web Bot Auth directoryEmergingNot counted
auth.md walkthrough simulationRecommendedNot counted
MCP error handlingRecommendedNot counted
MCP modern transportRecommendedNot counted
REST pagination patternRecommendedNot counted
Multi-language SDK packagesRecommendedNot counted
NLWeb /ask endpointEmergingNot counted
NLWeb streaming supportEmergingNot counted
REST response schema coverageRecommendedNot counted
MCP tool annotationsRecommendedNot counted
MCP server-card.jsonRecommendedNot counted
Product + docs MCP coverageRecommendedNot counted
MCP resources exposedRecommendedNot counted
GraphQL typed error modelRecommendedNot counted
GraphQL versioning / deprecation policyRecommendedNot counted
GraphQL pagination patternRecommendedNot counted
GraphQL async-job patternRecommendedNot counted
GraphQL schema description coverageRecommendedNot counted
GraphQL batch mutationsRecommendedNot counted
Native interactive controlsRecommendedNot counted
Form control labelingRecommendedNot counted
Accessibility-tree injection safety (bonus)RecommendedNot counted
MCP Apps supportRecommendedNot counted
A2UI / generative UI supportEmergingNot counted
MCP Apps UI qualityRecommendedNot counted
MCP App view reachableRecommendedNot counted
MCP App view CSPRecommendedNot counted
MCP resource qualityRecommendedNot counted
PaymentsNot scored yet6 partly
MPP payment protocolRequired0 / 2
x402 payment protocolRequired0 / 2
UCP - Universal Commerce ProtocolRequired0 / 3
ACP - Agentic Commerce ProtocolRequired0 / 3
ACP delegate paymentRecommended0 / 3
AP2 - Agent Payments ProtocolRecommended0 / 3

Field notes on agent users, every other week.

The newest agent journey teardowns, straight to your inbox. No launches, no fluff.

One email every two weeks. Unsubscribe anytime.