What is deepeval.com's AI agent readiness grade?

deepeval.com publishes 6 agent-facing standards across 4 of 9 lifecycle steps (grade A+, checked 2026-10-25).

Which AI agent discovery manifests and crawler policies does deepeval.com publish?

deepeval.com publishes 6 observed agentic-web standards (llms.txt, Content Signals Policy, AI Catalog well-known file, api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs, Agent Skills, Markdown for Agents). Preferred agent routing mode: agent_skills.

deepeval.com agentic web readiness

A+ Manifest validity: 100% (4/4 valid, 0 errors, 9 warnings) · Surface score 67 (coverage 40 + breadth 12 + conformance 15). 6 standards observed across 4 of 9 steps; 4 manifests present (+ robots.txt), 0 errors, 9 warnings. Checked 2026-10-25 23:11:08 UTC. This grades the agent-facing files published at deepeval.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/deepeval.com.svg) · JSON · Markdown · Re-check now

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt, Markdown for Agents 05 ActAgent Skills 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 404
AI Catalog well-known file `/.well-known/ai-catalog.json`	valid	entries[0] has no description; registries index on it entries[1] has no description; registries index on it entries[2] has no description; registries index on it entries[3] has no description; registries index on it entries[4] has no description; registries index on it served only at deprecated /.well-known/ai-catalog.json; ARD v0.91+ expects /.well-known/ard.json (serve both during migration)
MCP Server Cards (SEP-2127) `/mcp/server-card`	absent HTTP 404
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid	no blockquote summary under the title
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	valid
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	valid
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	no AI tokens	no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (allowed) no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

API description https://deepeval.com/.well-known/api-catalog (application/linkset+json)
API description https://www.confident-ai.com/docs/openapi.yaml (application/vnd.oai.openapi)
API description https://www.confident-ai.com/docs/api-reference (text/html)
API description https://www.confident-ai.com/docs/openapi.yaml (application/vnd.oai.openapi)
API description https://www.confident-ai.com/docs/api-reference (text/html)
API description https://www.confident-ai.com/.well-known/mcp/server-card.json (application/mcp-server-card+json)
API description https://www.confident-ai.com/docs/coding-agents/mcp (text/html)
API description https://www.confident-ai.com/.well-known/mcp/server-card.json (application/mcp-server-card+json)
API description https://www.confident-ai.com/docs/coding-agents/mcp (text/html)
llms.txt: Docs, 151 links, llms-full.txt present
robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed
ARD bridge (/.well-known/ai-catalog.json): 4/5 valid, 0 legacy, 0 dead/broken (served at deprecated path only)

Standards observed

llms.txt https://deepeval.com/llms.txt
Content Signals Policy https://deepeval.com/robots.txt
AI Catalog well-known file https://deepeval.com/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://deepeval.com/.well-known/api-catalog
Agent Skills https://deepeval.com/.well-known/agent-skills/index.json
Markdown for Agents https://deepeval.com/

Cheapest next steps

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "deepeval.com"}))

AGENTS.md: instructions for coding agents working on or with the site

Generate starter /AGENTS.md for deepeval.com

# Deepeval for agents

Deepeval and what it offers to agents

## Read the data, not the HTML
- Index: https://deepeval.com/llms.txt
- API description: https://deepeval.com/openapi.json
- Discovery catalog: https://deepeval.com/.well-known/ard.json

## Calling
- MCP server (Streamable HTTP): https://deepeval.com/mcp
- Rate limits and authentication: describe them here

## Conventions
- How to cite or attribute content
- What not to do (no scraping of /account/, no automated sign-ups, etc.)

Contact: security@deepeval.com

security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

Generate starter /.well-known/security.txt for deepeval.com

Contact: mailto:security@deepeval.com
Expires: 2027-09-20T23:11:08Z
Canonical: https://deepeval.com/.well-known/security.txt
Preferred-Languages: en
Policy: https://deepeval.com/security-policy

Agent pre-flight & practical readiness

Preferred mode: agent_skills (fallback llms_txt). GET the Agent Skills index and load the SKILL.md files it lists. Those files are the procedure; the HTML is not.

Fetch: GET https://deepeval.com/.well-known/agent-skills/index.json GET the Agent Skills index, then fetch the SKILL.md URLs it lists.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0, HTML-to-llms.txt token ratio 2.255×.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 28/30, capabilities 14/35, conformance 15/15, total 77/100, grade A+.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules