What is jasper.ai's AI agent readiness grade?

jasper.ai 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 jasper.ai publish?

jasper.ai publishes 6 observed agentic-web standards (llms.txt, Content Signals Policy, api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs, AI Crawler User-Agent Tokens in robots.txt, Agent Skills, Markdown for Agents). Preferred agent routing mode: mcp.

jasper.ai agentic web readiness

A Manifest validity: 60% (3/5 valid, 4 errors, 12 warnings) · Surface score 57 (coverage 40 + breadth 12 + conformance 5). 6 standards observed across 4 of 9 steps; 5 manifests present, 4 errors, 12 warnings. Checked 2026-10-25 03:14:16 UTC via www.jasper.ai. This grades the agent-facing files published at jasper.ai, not the organisation's products.

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

Coverage by step

01 DiscoverRFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt 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`	absent HTTP 404
MCP Server Cards (SEP-2127) `/.well-known/mcp/server-card.json`	errors	name missing description missing Content-Type is application/json; SEP-2127 says serve application/mcp-server-card+json pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[] $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json remotes missing: a card with no remotes gives clients nothing to connect to tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key) no Access-Control-Allow-Origin: * (required for browser clients) no Cache-Control max-age; clients should be able to cache the card no ETag View valid `/mcp/server-card` template for jasper.ai { "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json", "name": "ai.jasper/jasper", "title": "Jasper", "version": "1.0.0", "description": "Jasper and what it offers to agents", "websiteUrl": "https://jasper.ai/", "icons": [ { "src": "https://jasper.ai/icon.png", "mimeType": "image/png", "sizes": [ "180x180" ] } ], "remotes": [ { "type": "streamable-http", "url": "https://jasper.ai/mcp", "supportedProtocolVersions": [ "2025-11-25", "2025-06-18", "2025-03-26" ] } ] }
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	errors	skills[0].url missing skills[1].url missing skills[0].digest missing skills[1].digest missing View valid `/.well-known/agent-skills/index.json` template for jasper.ai { "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json", "skills": [ { "name": "jasper", "type": "skill-md", "description": "Jasper and what it offers to agents", "url": "https://jasper.ai/.well-known/agent-skills/jasper/SKILL.md", "digest": "sha256:0000000000000000000000000000000000000000000000000000000000000000" } ] }
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`	valid	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

MCP endpoint https://mcp.jasper.ai (streamable-http), tools: generate-content, get-jasper-agents, run-jasper-agent, get-jasper-brand-voices, get-jasper-audiences, get-jasper-style-guides, search-knowledge-base — from /.well-known/mcp/server-card.json
API description https://developers.jasper.ai/reference (text/html)
API description https://developers.jasper.ai (service-doc)
API description https://developers.jasper.ai/docs/using-commands (service-doc)
API description https://developers.jasper.ai/docs/using-agents (service-doc)
API description https://developers.jasper.ai/docs/jasper-mcp-server (service-doc)
llms.txt: Jasper, 61 links
robots.txt AI policy: allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, Google-Extended, PerplexityBot, CCBot, Applebot-Extended, meta-externalagent, Bytespider, cohere-ai, Diffbot, YouBot; unlisted crawlers partial

Standards observed

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

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": "jasper.ai"}))

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

Generate starter /AGENTS.md for jasper.ai

# Jasper for agents

Jasper and what it offers to agents

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

## Calling
- MCP server (Streamable HTTP): https://jasper.ai/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@jasper.ai

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

Generate starter /.well-known/security.txt for jasper.ai

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

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback llms_txt). Call the MCP endpoint at https://mcp.jasper.ai first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://mcp.jasper.ai POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

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 3.87×.

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

Readiness subscores: reach 20/20, readability 30/30, capabilities 18/35, conformance 5/15, total 73/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