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

infobip.com publishes 8 agent-facing standards across 4 of 9 lifecycle steps (grade A+, checked 2026-10-26).

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

infobip.com publishes 8 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, MCP Server Cards (SEP-2127), Model Context Protocol). Preferred agent routing mode: mcp.

infobip.com agentic web readiness

A+ Manifest validity: 80% (4/5 valid, 1 error, 25 warnings) · Surface score 65 (coverage 40 + breadth 15 + conformance 10). 8 standards observed across 4 of 9 steps; 5 manifests present (+ security.txt), 1 error, 25 warnings. Checked 2026-10-26 03:05:33 UTC via www.infobip.com. This grades the agent-facing files published at infobip.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/infobip.com.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	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) Content-Type is application/json; charset=UTF-8; SEP-2127 says serve application/mcp-server-card+json description is over 100 characters remotes[0].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[1].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[2].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[3].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[4].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[5].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[6].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[7].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[8].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[9].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[10].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[11].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[12].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[13].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[14].supportedProtocolVersions missing; clients use it to pick a version before connecting remotes[15].supportedProtocolVersions missing; clients use it to pick a version before connecting no Access-Control-Allow-Origin: * (required for browser clients) no ETag View valid `/mcp/server-card` template for infobip.com { "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json", "name": "com.infobip/infobip", "title": "Infobip", "version": "1.0.0", "description": "Infobip and what it offers to agents", "websiteUrl": "https://infobip.com/", "icons": [ { "src": "https://infobip.com/icon.png", "mimeType": "image/png", "sizes": [ "180x180" ] } ], "remotes": [ { "type": "streamable-http", "url": "https://infobip.com/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	no blockquote summary under the title
AGENTS.md `/AGENTS.md`	blocked HTTP 403
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`	valid	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	valid	Canonical: missing
auth.md `/auth.md`	blocked HTTP 403
Open Knowledge Format `/okf/index.md`	blocked HTTP 403

What an agent can call

MCP endpoint https://mcp.infobip.com/sms (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/email (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/whatsapp (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/whatsapp-flow (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/viber (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/rcs (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/voice (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/mobile-app-messaging (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/2fa (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/camara (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/people (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/account-management (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/application-entity (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/provision (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/search (streamable-http) — from /.well-known/mcp/server-card.json
MCP endpoint https://mcp.infobip.com/deep-research (streamable-http) — from /.well-known/mcp/server-card.json
API description https://api.infobip.com/platform/1/openapi (application/json)
API description https://www.infobip.com/docs/api (text/html)
API description https://www.infobip.com/docs/llms.txt (text/plain)
API description https://www.infobip.com/.well-known/mcp/server-card.json (application/json)
API description https://www.infobip.com/docs/mcp (text/html)
llms.txt: Infobip, 67 links
robots.txt AI policy: blocks meta-externalagent, Bytespider, Diffbot; allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, Google-Extended, PerplexityBot, Perplexity-User, CCBot, Applebot-Extended, Amazonbot; unlisted crawlers allowed

Standards observed

llms.txt https://infobip.com/llms.txt
Content Signals Policy https://infobip.com/robots.txt
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://infobip.com/.well-known/api-catalog
AI Crawler User-Agent Tokens in robots.txt https://infobip.com/robots.txt
Agent Skills https://infobip.com/.well-known/agent-skills/index.json
Markdown for Agents https://infobip.com/
MCP Server Cards (SEP-2127)
Model Context Protocol

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": "infobip.com"}))

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

Generate starter /AGENTS.md for infobip.com

# Infobip for agents

Infobip and what it offers to agents

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

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

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://mcp.infobip.com/sms first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://mcp.infobip.com/sms 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 1.93×.

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 31/35, conformance 10/15, total 89/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