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

bland.ai publishes 5 agent-facing standards across 3 of 9 lifecycle steps (grade A, checked 2026-10-25).

Which AI agent discovery manifests and crawler policies does bland.ai publish?

bland.ai publishes 5 observed agentic-web standards (llms.txt, Agentic Resource Discovery, AI Catalog well-known file, AI Crawler User-Agent Tokens in robots.txt, Markdown for Agents). Preferred agent routing mode: mcp.

bland.ai agentic web readiness

A Manifest validity: 100% (4/4 valid, 0 errors, 14 warnings) · Surface score 54 (coverage 30 + breadth 9 + conformance 15). 5 standards observed across 3 of 9 steps; 4 manifests present (+ security.txt), 0 errors, 14 warnings. Checked 2026-10-25 03:09:40 UTC via www.bland.ai. This grades the agent-facing files published at bland.ai, not the organisation's products.

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

Coverage by step

01 DiscoverARD, AI Catalog well-known file 02 Identifynothing observed 03 PermitAI Crawler User-Agent Tokens in robots.txt 04 Readllms.txt, Markdown for Agents 05 Actnothing observed 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.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 no entry has representativeQueries; ARD registries use 2-5 example queries to index entries
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 no entry has representativeQueries; ARD registries use 2-5 example queries to index entries
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
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116) `/.well-known/security.txt`	valid	Canonical: missing
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://api.bland.ai/v1/mcp (streamable-http) — from /.well-known/ard.json#urn:air:bland.ai:mcp:bland
MCP endpoint https://docs.bland.ai/mcp (streamable-http) — from /.well-known/ard.json#urn:air:bland.ai:mcp:bland-docs
MCP endpoint https://api.bland.ai/v1/mcp (streamable-http) — from /.well-known/ai-catalog.json#urn:air:bland.ai:mcp:bland
MCP endpoint https://docs.bland.ai/mcp (streamable-http) — from /.well-known/ai-catalog.json#urn:air:bland.ai:mcp:bland-docs
llms.txt: Bland AI, 92 links, llms-full.txt present
robots.txt AI policy: blocks meta-externalagent, Bytespider; allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, anthropic-ai, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Applebot-Extended, Amazonbot, cohere-ai, Diffbot, DuckAssistBot, MistralAI-User, YouBot; unlisted crawlers partial
ARD bridge (/.well-known/ard.json): 2/4 valid, 0 legacy, 0 dead/broken

Standards observed

llms.txt https://bland.ai/llms.txt
Agentic Resource Discovery https://bland.ai/.well-known/ard.json
AI Catalog well-known file https://bland.ai/.well-known/ai-catalog.json
AI Crawler User-Agent Tokens in robots.txt https://bland.ai/robots.txt
Markdown for Agents https://bland.ai/

Cheapest next steps

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

Generate starter /AGENTS.md for bland.ai

# Bland for agents

Bland and what it offers to agents

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

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

api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "bland.ai"}))
MCP Server Cards (SEP-2127): if you run an MCP server, a SEP-2127 card at <mcp-url>/server-card lets clients configure themselves (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "mcp-server-cards", "domain": "bland.ai"}))

Agent pre-flight & practical readiness

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

Fetch: POST https://api.bland.ai/v1/mcp 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.

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

Readiness subscores: reach 19/20, readability 30/30, capabilities 21/35, conformance 15/15, total 85/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