Bird (ex-SparkPost)

What our check kept, up to 60 lines or 6 KB

User-Agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=yes
Allow: /
Disallow: /admin
# These sections are an unlisted import of the GitBook corpora.
# Disallow normally hides the per-page noindex from crawlers; safe here because
# these URLs are new, carry no inbound links, and are in no sitemap — and it is
# what keeps the site-wide Content-Signal from inviting AI crawlers into them.
# Content-Signal is group-scoped, not per-path, so the per-resource X-Robots-Tag
# in next.config.ts is what actually carries "no AI" for these URLs.
# The one exception, and it must come before the Disallow below it: the retired
# knowledge base is a content-collection served under that same prefix, and its
# old /knowledge-base URLs are indexed. A crawler following one through the 301
# has to be able to fetch the page to read its noindex, which a Disallow would
# stop it doing, leaving the old entries in the index forever.
Allow: /docs/engagement-platform/knowledge-base
Allow: /*/docs/engagement-platform/knowledge-base
Disallow: /docs/engagement-platform
Disallow: /*/docs/engagement-platform
Disallow: /docs/connectivity-platform
Disallow: /*/docs/connectivity-platform
Disallow: /docs/taxi
Disallow: /*/docs/taxi
Disallow: /docs/pusher
Disallow: /*/docs/pusher
Disallow: /docs/24sessions
Disallow: /*/docs/24sessions
Disallow: /docs/24sessions-nl
Disallow: /*/docs/24sessions-nl
Disallow: /docs/toky
Disallow: /*/docs/toky
Disallow: /docs/toky-es
Disallow: /*/docs/toky-es
Disallow: /gitbook-assets

Sitemap: https://bird.com/sitemap.xml
Sitemap: https://bird.com/video-sitemap.xml
Agentmap: https://bird.com/.well-known/ard.json

How we test this:

• We read robots.txt and check it doesn't disallow / for the agents that fetch for a user or find sites for AI search: ChatGPT-User, OAI-SearchBot, Claude-User, Claude-SearchBot, Perplexity-User, PerplexityBot (no robots.txt counts as allowed).
• We show blocks on GPTBot (OpenAI model training), not scored; ClaudeBot (Anthropic model training), not scored; Google-Extended (Gemini training and grounding), not scored in v1; CCBot (Common Crawl's open dataset), not scored: blocking them is the site's own call.
• Whether Google-Extended should be scored is a rubric v2 question, and we'll announce it before changing anything.
• Then we fetch your homepage as LeaderfileBot and check it returns 2xx after redirects, with no challenge page.

How we test this:

• We fetch your homepage and your docs page as LeaderfileBot, our own scanner, and check neither answers with a challenge page, or a 401 or 403 that a normal browser gets past.
• One blocked page is a fail; both caps your score at 39.
• Firewalls often let in crawlers they can verify, so ChatGPT or Claude may still get in where our scanner can't.

How we test this:

• We look for your docs page: the first homepage link to a docs., dev. or developer(s). subdomain of your domain, or to a /docs or /developer(s) path; with none, we try https://docs.<host>/ then https://<host>/docs.
• It passes if that page returns 200.
• Board companies use a docs URL we confirmed by hand.

What our check kept, up to 60 lines or 6 KB

a Link header: https://bird.com/llms.txt

How we test this:

• We read your homepage and your docs page and look for a pointer to an llms.txt: a link to it, a <link> tag, a Link header with rel="llms-txt" or an X-Llms-Txt header, or a line on the page naming /llms.txt.
• It passes when one points at an llms.txt that answers with markdown links.
• AFDocs checks the same (llms-txt-directive).

What our check kept, up to 60 lines or 6 KB

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><sitemap><loc>https://bird.com/sitemaps/sitemap/0.xml</loc></sitemap><sitemap><loc>https://bird.com/sitemaps/sitemap/1.xml</loc></sitemap><sitemap><loc>https://bird.com/sitemaps/sitemap/2.xml</loc></sitemap></sitemapindex>

How we test this:

• We fetch the Sitemap: URL from robots.txt, else /sitemap.xml, and check it returns 200 with a <urlset> or <sitemapindex> root element.

How we test this:

• We count the visible words in the raw HTML (no JavaScript run) of your homepage and your docs page, and check each has at least 150.
• With no docs page found (AR-FIND-02), the homepage is judged alone.

How we test this:

• We read your docs page and up to 7 more docs pages (the ones we read for other checks, then links on your docs page).
• A page fails when it answers 401 or 403 to a normal browser too, redirects to a sign-in page, or is a sign-in form with little else on it.
• A redirect counts as a sign-in when it adds one: a sign-in path the page didn't have, a login subdomain, or an identity provider's site such as Okta's when the page was on another site.
• A sign-up page, one whose title or main heading says sign up or create an account, isn't a login.
• A refusal only to automated readers is our scanner being blocked, not a login.
• A login on your docs page caps your score at 39; across the pages, a share of 25% or less caps it at 39, 50% or less at 59.

How we test this:

• We fetch /leaderfile-check-404, a page that shouldn't exist, and check it returns 404 or 410 after redirects.
• Off the board, if that address refuses automated readers, we try /leaderfile-check-404.html.

What our check kept, up to 60 lines or 6 KB

# Bird

> Bird connects customer communications across email, SMS, WhatsApp, Apple
> Messages and voice, with verification, lookup, mailboxes, eSIM and realtime
> tools. Build with the API, SDKs, CLI or hosted MCP server.

## Check capabilities before integrating

- **Email, SMS and WhatsApp**: send messages and inspect their delivery through
  the developer API. WhatsApp also exposes reads for templates, numbers and
  aggregate stats. Check the operation reference for supported writes.
- **Verify**: create a verification to send a one-time passcode, check the code
  the user enters, and resend on the next channel through the developer API.
  Listing and reading verifications is available in the dashboard only.
- **Voice**: read call legs through the developer API. Use the Voice and SIP
  guides to choose a calling integration.
- **Receiving, setup and administration**: support varies by product and operation.
  Read the product guide and discover the available tools before acting.
- Use the live MCP tool list and OpenAPI specification to verify operations,
  authorization, required inputs and response states.

## Start here

- [Quickstart](https://bird.com/docs/get-started/send-your-first-email): Create an API key and send your first email
- [SMS quickstart](https://bird.com/docs/get-started/send-your-first-sms): Enable a destination, send a built-in template SMS, and read its delivery status
- [Verify quickstart](https://bird.com/docs/get-started/verify-your-first-customer): Send a one-time passcode and check the code
- Install the CLI: `curl 'https://cli.bird.com/install.sh' | sh`, or with Homebrew: `brew install messagebird/tap/bird`
- Connect the hosted MCP: `claude mcp add --transport http bird https://mcp.bird.com`,
  then authenticate it (OAuth-gated, tools fail without a grant): in Claude Code run
  `/mcp`, select `bird`, choose Authenticate; headless, `claude mcp login bird`.
  In Claude, add Bird from the connector directory: https://claude.ai/directory/bird
  Install Bird in Codex: codex://plugins/plugin_asdk_app_6ac74d2aa37481918759cbb0ea8aa6c6
  Or in ChatGPT: https://chatgpt.com/plugins/plugin_asdk_app_6ac74d2aa37481918759cbb0ea8aa6c6
  Other hosts: https://bird.com/docs/ai/mcp-server#connect-a-client

## Get help

- Stuck or have ideas? `bird platform feedback` (MCP: `platform_feedback`) tells us what to improve; `bird platform support create` (MCP: `platform_support_create`) gets you help when something is broken. `bird platform status` shows Bird's service status.

## For AI agents

- [MCP server](https://bird.com/docs/ai/mcp-server): Hosted at mcp.bird.com. OAuth authentication, scoped per workspace, curated task-level tools, destructive operations annotated
- [Agent skills (bird-ai plugin)](https://bird.com/docs/ai/agent-skills): Skills + MCP, installed in one step
- [CLI for agents](https://bird.com/docs/ai/cli-for-agents): JSON output, semantic exit codes, fewer tokens per operation
- [llms-full.txt](https://bird.com/llms-full.txt): English authored guides in one file; generated operation references are available separately

## Machine-readable surfaces

- [OpenAPI 3.1 spec](https://bird.com/openapi.json): every public endpoint, schema, and error code. Same file as [/openapi.yaml](https://bird.com/openapi.yaml), and the file the SDKs are generated from
- [OAuth 2.0 authorization server metadata](https://platform.bird.com/.well-known/oauth-authorization-server): RFC 8414 discovery, at the issuer itself. Authorization, token, device, revocation, and dynamic client registration endpoints, plus every delegable scope
- [Search the docs](https://us1.platform.bird.com/v1/docs/search?q=webhook+signature&limit=3): public GET endpoint; set `q` to your task. Read the matching `markdown_url` and linked references before loading a larger corpus
- [Sitemap](https://bird.com/sitemap.xml): Indexable pages by locale
- [auth.md](https://bird.com/auth.md): how an agent obtains, uses, and revokes a credential, in prose
- Any page as Markdown: append `.md` to its URL, or send `Accept: text/markdown`
- Code examples: TypeScript/JavaScript, Python, Go and PHP SDKs; Swift and Kotlin Realtime clients; and CLI, cURL, MCP or shell examples, wherever offered. Follow a Markdown page's `Examples:` links for focused language views such as `.py.md`; the links list the alternatives that page offers.
- To select examples within the full page, send `Accept-Language: en-us, python` to choose a named example. Matching examples change in place; other examples and content remain. A preference with no matching example keeps the default. The page URL selects the content locale.

## Learn and practise

- [Topic and resource catalog](https://bird.com/content-map.json): Versioned relationships between current products, docs, answers, tools, videos and practice briefs

How we test this:

• We read llms.txt at your site root and, if your docs live on another host, at your docs root, and check one returns 200, isn't HTML and has at least one markdown link.
• Off the board, we also try your docs. host and /docs/llms.txt.
• We read the first 2 MB: a larger file is judged on that part, and the result says "read the first 2 MB; the file is larger".

How we test this:

• We read the llms.txt AR-READ-07 passes on (the first with markdown links) and fetch up to 12 of its links, spread through the file, two at a time.
• A link is broken when it answers 404 or 410, or its host doesn't exist.
• A 2xx after redirects resolves, and so does an answer like 400, 405 or 406 that shows the address is there (an MCP endpoint answers a plain GET with 405).
• A refusal, a 429 or a server error isn't judged.
• The credit is the share that resolve, halved when the file runs to 50,000 characters or more, and nothing past 100,000: AFDocs' size bands.
• With no llms.txt it isn't counted: AR-READ-07 counts that.

How we test this:

• On each docs page we read (up to 7) we count the characters of visible text in the raw HTML, and of its Markdown copy if it has one, and judge the page by the larger of the two: an agent reading either may be cut off.
• Under 50,000 passes, up to 100,000 is half, more fails: AFDocs' bands, from the limits agents cut pages at.
• The credit is the average across the pages.

What our check kept, up to 60 lines or 6 KB

<meta name="description" content="Send transactional emails, run marketing campaigns, and handle replies in one place. Reach the inbox reliably and build with the Bird API, SDKs, or MCP."/>

How we test this:

• We check your homepage's raw HTML (no JavaScript run) has a non-empty meta description or og:description.

What our check kept, up to 60 lines or 6 KB

<h1>Email overview</h1>
<h2>How sending works</h2>
<h2>The Email section of the dashboard</h2>
<h2>Where each guide fits</h2>
<h2>Related resources</h2>

How we test this:

• We check your docs page's raw HTML (no JavaScript run) has at least 2 headings (h1 to h3) with text and at least 150 visible words.
• Off the board, a docs page that comes back as markdown counts # to ### lines outside code blocks as its headings.

What our check kept, up to 60 lines or 6 KB

<code class="text-foreground bg-card rounded-sm border px-1 font-mono wrap-anywhere group-[&amp;]/code-block:rounded-none group-[&amp;]/code-block:border-none group-[&amp;]/code-block:bg-transparent group-[&amp;]/code-block:p-0 group-[&amp;]/code-block:text-inherit language-bash">

How we test this:

• On your docs surface, we look for a code block that carries a language tag: language-* or lang-* on <pre> or <code>, code-language-* on any element (a code block's wrapper, say), or a data-language or data-lang attribute.
• In markdown files, a fenced block with a language (```ts) counts.
• If no page shows one, we read the markdown copy each HTML page declares (a <link rel="alternate" type="text/markdown">, or its URL plus .md listed in your llms.txt), since many docs sites add the language label with JavaScript.
• If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.

What our check kept, up to 60 lines or 6 KB

CLI reference Webhooks MCP Server Integrations Tools Changelog Pricing Log in Get Started Menu Email pricing. Built to grow. Start with the published Free allowance. A paid Email plan adds its monthly deposit to your Bird balance. Email usage is charged from the first send at your applicable rate. Get S

How we test this:

• We fetch the first homepage link with 'pricing' in its path, else /pricing (board companies: a pricing URL we confirmed by hand), and check it returns 200 and its raw text (no JavaScript run) shows a price or 'free' within 80 characters of month, mo, year or yr.
• Off the board, a pricing address that answers with JSON counts when it has a price field.

What our check kept, up to 60 lines or 6 KB

---
title: "Email overview"
description: "Understand how Bird sends and receives email, how delivery progresses after acceptance, and where to configure Email in the dashboard."
canonical: "https://bird.com/docs/guides/email/overview"
---

# Email overview

Send transactional and marketing email through `POST /v1/email/messages`. Use a `bk_{region}_...` key with its matching regional host: `https://us1.platform.bird.com` or `https://eu1.platform.bird.com`. We sign the message with DKIM, deliver it, and report each recipient's outcome.

To send something before reading further, the [quickstart](/docs/get-started/send-your-first-email) takes you from an API key to a delivered message. This page covers the model the rest of this section assumes, and points at the guide for each part of it.

## How sending works

A send is accepted in one call and delivered asynchronously. `POST /v1/email/messages` validates the payload and sending domain, then returns `202 Accepted` with an `em_` message ID. Read each recipient's outcome through [webhook events](/docs/guides/email/events) or the message endpoints. [Sending email](/docs/guides/email/sending-email) covers the payload, field limits, and response.

Two consequences of that model shape the rest of this section.

**One message, many recipients, one lifecycle each.** A message to five addresses produces five independent outcomes, and the message-level status you read back is an aggregate over them. Suppression is evaluated the same way: one [suppressed](/docs/guides/email/suppressions) address comes back `rejected` while the other four deliver.

**Every message declares why you are sending it.** A [category](/docs/guides/email/categories) of `transactional` or `marketing` decides which suppressions apply to it. Someone who unsubscribed from your newsletter still needs their password reset to arrive, and the category is what tells us the difference.

A send can also arrive by another route, or leave later. [SMTP](/docs/guides/email/smtp) accepts submissions from anything that speaks the protocol, and [scheduled sending](/docs/guides/email/scheduled-sending) holds a message until a time you set.

## The Email section of the dashboard

Email is one of the channels in the dashboard sidebar. Its pages, in the order they appear:

| Page                     | What it holds                                                                                                                                 |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Onboarding**           | A three-step checklist: create an API key, send an email, add your domain. It shows until you have finished it                                |
| **Metrics**              | Delivery, open, bounce, and complaint rates over time; see [Email metrics](/docs/guides/email/tracking-and-metrics)                           |
| **Emails**               | Every message sent; see the [email log](/docs/guides/email/email-log). Its Receiving tab lists what came in                                   |
| **Mailboxes**            | Programmable inboxes your code reads and replies from; see [Agent mailboxes](/docs/guides/email/mailboxes)                                    |
| **Templates**            | Reusable subject and body content, with a draft and published versions; see [Email templates](/docs/guides/email/templates)                   |
| **Domains**              | Your sending domains, their DNS records, and live verification status; see [Sending domains](/docs/guides/email/sending-domains)              |
| **IP Pools**             | Dedicated IPs and the pools they sit in; see [Dedicated IPs and pools](/docs/guides/email/dedicated-ips-and-pools)                            |
| **Broadcasts**           | One email to a stored audience, with delivery tracked per recipient; see [Broadcasts](/docs/guides/email/broadcasts)                          |
| **Suppressions**         | Addresses we do not send to, and why; see [Suppressions](/docs/guides/email/suppressions)                                                     |
| **Unsubscribe page**     | Branding for the hosted page every marketing email links to; see [Unsubscribe links](/docs/guides/email/unsubscribe-links)                    |
| **SMTP**                 | Connection settings, per-key send defaults, and live connections; see [SMTP](/docs/guides/email/smtp)                                         |
| **Inbox Insights**       | Inbox placement and sender reputation across mailbox providers; see [Inbox Insights](/docs/guides/email/inbox-insights)                       |
| **Competitive insights** | Panel-derived sending volume, cadence, and engagement for watched brands; see [Competitive Insights](/docs/guides/email/competitive-insights) |

Recipients live outside the Email section, in **Contacts** in the sidebar: **All contacts** stores people with typed custom properties (see [Contacts](/docs/guides/email/contacts)), and **Audiences** groups them into the reusable lists a broadcast sends to (see [Audiences](/docs/guides/email/audiences)).

## Where each guide fits

**Sending.** [Sending email](/docs/guides/email/sending-email) is the one to read first: it owns the payload every other send path is a variation on. From there, [templates](/docs/guides/email/templates) store content you reuse, [attachments](/docs/guides/email/attachments) add files, [batch sending](/docs/guides/email/sending-bulk) submits up to 100 messages in one request, and [broadcasts](/docs/guides/email/broadcasts) send one email to a whole audience.

**Domains and authentication.** [Sending domains](/docs/guides/email/sending-domains) covers registering a domain and getting it verified. [DKIM, SPF, and DMARC](/docs/guides/email/dkim-spf-dmarc) explains what each record proves to a receiving mailbox provider, and [BIMI](/docs/guides/email/bimi) shows your logo beside your messages in email apps that support it.

**Reputation.** [Su

How we test this:

• On each docs page we read (up to 7), one Markdown answer with content passes the page: it answers Accept: text/markdown with text/markdown, declares a copy with <link rel="alternate" type="text/markdown"> that returns Markdown, or the address the page lands on, after redirects, ending in .md does (for one ending in a slash, both /page.md and /page/index.md).
• An empty answer doesn't count.
• The credit is the share of pages that pass.
• AFDocs, Cloudflare's isitagentready and is-agentic check it.

What our check kept, up to 60 lines or 6 KB

{"@context":"https:\u002F\u002Fschema.org","@graph":[{"@type":"Organization","@id":"https:\u002F\u002Fbird.com\u002F#organization","name":"Bird","legalName":"Bird B.V.","alternateName":["MessageBird","SparkPost"],"description":"Reach your customers, wherever they are. Email, SMS, WhatsApp, Apple Messages, and Voice.","url":"https:\u002F\u002Fbird.com","foundingDate":"2011","contactPoint":{"@type":"ContactPoint","contactType":"customer support","email":"support@bird.com","url":"https:\u002F\u002Fbird.com\u002Fhelp\u002Fsupport"},"address":{"@type":"PostalAddress","streetAddress":"Keizersgracht 268","postalCode":"1016 EV","addressLocality":"Amsterdam","addressCountry":"NL"},"logo":"https:\u002F\u002Fbird.com\u002Ffavicon-light.png","sameAs":["https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fbirdhq","https:\u002F\u002Fx.com\u002Fmessagebird","https:\u002F\u002Fwww.instagram.com\u002Fmessagebird","https:\u002F\u002Fgithub.com\u002Fmessagebird","https:\u002F\u002Fwww.youtube.com\u002F@birdHQ","https:\u002F\u002Fwww.ycombinator.com\u002Fcompanies\u002Fbird","https:\u002F\u002Fwww.crunchbase.com\u002Forganization\u002Fmessagebird","https:\u002F\u002Fnl.wikipedia.org\u002Fwiki\u002FBird_(bedrijf)","https:\u002F\u002Fwww.wikidata.org\u002Fwiki\u002FQ106845206","https:\u002F\u002Fwww.capterra.com\u002Fp\u002F160795\u002FBird\u002F","https:\u002F\u002Fwww.g2.com\u002Fproducts\u002Fmessagebird-bird"]},{"@type":"WebSite","@id":"https:\u002F\u002Fbird.com\u002F#website","name":"Bird","url":"https:\u002F\u002Fbird.com","publisher":{"@id":"https:\u002F\u002Fbird.com\u002F#organization"}}]}

How we test this:

• We check your homepage's raw HTML has an application/ld+json block that parses as JSON and has @type or @context.

What our check kept, up to 60 lines or 6 KB

{"issuer":"https://platform.bird.com","authorization_endpoint":"https://platform.bird.com/v1/oauth/authorize","token_endpoint":"https://platform.bird.com/v1/oauth/token","device_authorization_endpoint":"https://platform.bird.com/v1/oauth/device","revocation_endpoint":"https://platform.bird.com/v1/oauth/revoke","registration_endpoint":"https://platform.bird.com/v1/oauth/register","grant_types_supported":["authorization_code","urn:ietf:params:oauth:grant-type:device_code","refresh_token"],"response_types_supported":["code"],"scopes_supported":["access_restrictions:read","access_restrictions:write","amb:read","amb:write","amb_management:read","amb_management:write","analytics:read","analytics:write","api_keys:read","api_keys:write","assets:read","assets:write","audit:read","audit:write","competitive:read","competitive:write","compliance:read","compliance:write","domains:read","domains:write","email_management:read","email_management:write","email_marketing:read","email_marketing:write","emails:read","emails:write","esim:read","esim:write","esim_credentials:read","esim_credentials:write","inbox_insights:read","inbox_insights:write","ip_pools:read","ip_pools:write","lookup:read","lookup:write","mailbox:read","mailbox:write","mailbox_management:read","mailbox_management:write","members:read","members:write","numbers:read","numbers:write","preferences:read","preferences:write","rcs:read","rcs:write","rcs_management:read","rcs_management:write","realtime:read","realtime:write","request_logs:read","request_logs:write","service_accounts:read","service_accounts:write","sms:read","sms:write","sms_management:read","sms_management:write","trust:read","trust:write","verify:read","verify:write","verify_management:read","verify_management:write","voice:read","voice:write","voice_management:read","voice_management:write","webhooks:read","webhooks:write","whatsapp:read","whatsapp:write","whatsapp_management:read","whatsapp_management:write","workspace:read","workspace:write","org:access_restrictions:read","org:access_restrictions:write","org:audit:read","org:audit:write","org:billing:read","org:billing:write","org:ip_pools:read","org:ip_pools:write","org:members:read","org:members:write","org:settings:read","org:settings:write","org:trust:read","org:trust:write","org:workspaces:read","org:workspaces:write"],"code_challenge_methods_supported":["S256"],"token_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post"],"revocation_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post"],"authorization_response_iss_parameter_supported":true}

How we test this:

• We fetch five standard .well-known files and check at least one returns 200 with valid JSON: oauth-authorization-server (RFC 8414), oauth-protected-resource (RFC 9728), openid-configuration, api-catalog (RFC 9727) and agent-card.json (A2A).
• This list is ours: AgentReady v2.0 doesn't name one.
• Off the board, on a miss, we also read oauth-protected-resource on the mcp., api. and docs. hosts of your domain, where that metadata usually lives, and it counts only with its resource field.

What our check kept, up to 60 lines or 6 KB

e most tools, because it has the most surface to configure. The other channels carry the same send-and-read shape. Messaging Send and inspect email : email_send , email_send_batch , email_list , and email_get , which returns the message with its aggregate delivery status. Per-recipient delivery statuses and t

How we test this:

• Passes when AR-ACT-03 passes (your docs surface names your own MCP server, not just a mention or a blog post about one; on the board, only an MCP server with a tool that acts on the product: send, manage or query, not only search docs, since AgentReady calls this "the interface an agent acts through"), or when your docs surface shows a CLI install: brew install, npm i -g, npm install -g, pipx install, uv tool install, go install, az extension add, or curl ... | sh (or | bash).
• A mention of MCP that isn't your own server, with no CLI install, isn't counted.
• For board companies, the CLI half counts only a command of the product's own CLI that we confirmed by hand, like az communication email send or twilio email:send, on the pages we read or on the docs page that shows it: an install alone could be any tool (an MCP setup guide installing pnpm, say).
• For a product inside a larger platform, the platform's MCP server or CLI counts when its docs show it covers the product.
• An MCP server earns both this check and AR-ACT-03, because AgentReady lists them as two items.
• If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.

How we test this:

• We look for an OpenAPI or Swagger document: for board companies, a URL we confirmed by hand; then up to 2 links on your docs surface whose URL mentions openapi or swagger, or whose link text does for a .json or .yaml file (files on other sites count when your docs link them; an address written out in your llms.txt or another text file counts as a link, and its line as the link text); then /openapi.json and /openapi.yaml on your host and your docs host.
• Off the board, a .json or .yaml link under an llms.txt heading that names OpenAPI counts as a link to a spec, or, where that section has none, a link with no file extension, and on a miss we also try those two on the docs., developers. and api. hosts of your domain.
• It passes if one parses as JSON or YAML with an openapi or swagger key and at least one path.
• A spec over 10 MB counts as couldn't check.

What our check kept, up to 60 lines or 6 KB

npm install @messagebird/sdk
pip install messagebird-sdk

How we test this:

• On your docs surface we look for an npm install (npm, yarn, pnpm or bun) and a pip install (pip, poetry or uv) of a named package.
• Both must appear, on any of the pages (AgentReady: npm and PyPI).
• Off the board, uv tool install and pipx install also count as a pip install.
• Off the board, if one is missing we also read the markdown copy each HTML page declares (a <link rel="alternate" type="text/markdown">, or its URL plus .md listed in your llms.txt), then up to 2 pages your llms.txt names for that language.
• AgentReady v2.0 asks for SDKs and a CLI here; this check tests the npm and PyPI half, and a CLI counts under AR-ACT-10.
• If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.

What our check kept, up to 60 lines or 6 KB

{"issuer":"https://platform.bird.com","authorization_endpoint":"https://platform.bird.com/v1/oauth/authorize","token_endpoint":"https://platform.bird.com/v1/oauth/token","device_authorization_endpoint":"https://platform.bird.com/v1/oauth/device","revocation_endpoint":"https://platform.bird.com/v1/oauth/revoke","registration_endpoint":"https://platform.bird.com/v1/oauth/register","grant_types_supported":["authorization_code","urn:ietf:params:oauth:grant-type:device_code","refresh_token"],"response_types_supported":["code"],"scopes_supported":["access_restrictions:read","access_restrictions:write","amb:read","amb:write","amb_management:read","amb_management:write","analytics:read","analytics:write","api_keys:read","api_keys:write","assets:read","assets:write","audit:read","audit:write","competitive:read","competitive:write","compliance:read","compliance:write","domains:read","domains:write","email_management:read","email_management:write","email_marketing:read","email_marketing:write","emails:read","emails:write","esim:read","esim:write","esim_credentials:read","esim_credentials:write","inbox_insights:read","inbox_insights:write","ip_pools:read","ip_pools:write","lookup:read","lookup:write","mailbox:read","mailbox:write","mailbox_management:read","mailbox_management:write","members:read","members:write","numbers:read","numbers:write","preferences:read","preferences:write","rcs:read","rcs:write","rcs_management:read","rcs_management:write","realtime:read","realtime:write","request_logs:read","request_logs:write","service_accounts:read","service_accounts:write","sms:read","sms:write","sms_management:read","sms_management:write","trust:read","trust:write","verify:read","verify:write","verify_management:read","verify_management:write","voice:read","voice:write","voice_management:read","voice_management:write","webhooks:read","webhooks:write","whatsapp:read","whatsapp:write","whatsapp_management:read","whatsapp_management:write","workspace:read","workspace:write","org:access_restrictions:read","org:access_restrictions:write","org:audit:read","org:audit:write","org:billing:read","org:billing:write","org:ip_pools:read","org:ip_pools:write","org:members:read","org:members:write","org:settings:read","org:settings:write","org:trust:read","org:trust:write","org:workspaces:read","org:workspaces:write"],"code_challenge_methods_supported":["S256"],"token_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post"],"revocation_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post"],"authorization_response_iss_parameter_supported":true}

How we test this:

• A stand-in: AgentReady asks for self-serve key generation with documented scopes, or OAuth metadata, and key sign-up can't be tested in code.
• It passes if OAuth metadata parses as JSON with the field its RFC requires (issuer for RFC 8414, resource for RFC 9728), or if your docs say "API key" or "API token" (also inside a placeholder like YOUR_API_KEY) within 200 characters of a documented auth header: an X-...-Key or X-...-Token header, a header named ...-Key or ...-Token, Authorization with Bearer, or "Bearer API key".
• The word "token" on its own doesn't count.
• For board companies we also read the authentication page their docs link.
• Off the board, OAuth metadata with its resource field on your mcp., api. or docs. host also counts.
• A board company whose API signs each request (like AWS Signature Version 4) or takes the key in the request body isn't counted: this stand-in can't judge that kind of auth either way.
• If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.

How we test this:

• In the OpenAPI spec AR-ACT-02 finds, we count the operations with a non-empty operationId.
• The credit is the share that have one.
• With no spec, it isn't counted: AR-ACT-02 already counts that.

What our check kept, up to 60 lines or 6 KB

e most tools, because it has the most surface to configure. The other channels carry the same send-and-read shape. Messaging Send and inspect email : email_send , email_send_batch , email_list , and email_get , which returns the message with its aggregate delivery status. Per-recipient delivery statuses and t

How we test this:

• On your docs surface we look for your own MCP server and quote the line: your name next to "MCP" ("Acme MCP server"), "our" or "official" MCP server, or an mcp.<your domain> address.
• Any other mention of "MCP server" or "Model Context Protocol", like a directory or an explainer, isn't counted: it can't fail you and it earns no points, because we can't tell the server is yours.
• A mention in a link to a blog post, or on an llms.txt line that links to one, doesn't count at all: a post about building a server isn't one you ship.
• For board companies we read the MCP page their docs link and list the tools it documents: a server that only searches your docs counts here, as AgentReady describes an MCP server as a "standard tool protocol for docs search and actions".
• We don't probe /mcp or call any server.
• Off the board, OAuth metadata with its resource field on your mcp. host also counts: it's the server's own file.
• If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.

How we test this:

• In the OpenAPI spec AR-ACT-02 finds, we count the operations that declare a 4xx, 5xx or default response with a schema, directly or through a $ref.
• The credit is the share that do.
• We note when they use application/problem+json (RFC 9457), the standard shape.
• With no spec, it isn't counted.
• The IETF's draft agent-friendly API profile, is-agentic and Alpic check it.

How we test this:

• We check your homepage's raw HTML, inline scripts included, contains modelContext (AgentReady names document.modelContext).
• External scripts aren't fetched.

What our check kept, up to 60 lines or 6 KB

{
  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
  "skills": [
    {
      "name": "bird-cli",
      "type": "archive",
      "description": "Use when operating Bird through the bird CLI to preview or send messages, inspect or manage API resources, register or inspect Inbox Insights seed tests, or onboard an account; excludes client development.",
      "url": "https://bird.com/.well-known/agent-skills/bird-cli.zip",
      "digest": "sha256:3b5bd4762eb4b82497f20d465867efb453029808df587edded56f23edd15c7e2"
    },
    {
      "name": "email-audit",
      "type": "archive",
      "description": "Use when auditing a live domain's email authentication or spam-delivery problems involving DMARC, SPF, DKIM, BIMI, or MX; single-record drafts use bird validators.",
      "url": "https://bird.com/.well-known/agent-skills/email-audit.zip",
      "digest": "sha256:4ff608d8364062a32571c9f6cc2fc2043020adb4aa26e945f9262fd578f8ea80"
    }
  ]
}

How we test this:

• Any of three passes: /.well-known/agent-skills/index.json on your site or your docs (or one a Link header names) lists a skill whose file answers; your docs or llms.txt link a SKILL.md that answers with a name and a description; or your docs show a skills install command, on a page we read or on up to 3 pages your docs or llms.txt link about skills or your CLI.
• An install is npx skills add, claude plugin install, a git clone into a skills folder, or your own command line running plugin install or skills add right after the word skill.
• An index under a folder, like /developer/, may list its files from that folder.
• Cloudflare's isitagentready, agenticplug and Alpic check it.

What our check kept, up to 60 lines or 6 KB

{"issuer":"https://platform.bird.com","authorization_endpoint":"https://platform.bird.com/v1/oauth/authorize","token_endpoint":"https://platform.bird.com/v1/oauth/token","device_authorization_endpoint":"https://platform.bird.com/v1/oauth/device","revocation_endpoint":"https://platform.bird.com/v1/oauth/revoke","registration_endpoint":"https://platform.bird.com/v1/oauth/register","grant_types_supported":["authorization_code","urn:ietf:params:oauth:grant-type:device_code","refresh_token"],"response_types_supported":["code"],"scopes_supported":["access_restrictions:read","access_restrictions:write","amb:read","amb:write","amb_management:read","amb_management:write","analytics:read","analytics:write","api_keys:read","api_keys:write","assets:read","assets:write","audit:read","audit:write","competitive:read","competitive:write","compliance:read","compliance:write","domains:read","domains:write","email_management:read","email_management:write","email_marketing:read","email_marketing:write","emails:read","emails:write","esim:read","esim:write","esim_credentials:read","esim_credentials:write","inbox_insights:read","inbox_insights:write","ip_pools:read","ip_pools:write","lookup:read","lookup:write","mailbox:read","mailbox:write","mailbox_management:read","mailbox_management:write","members:read","members:write","numbers:read","numbers:write","preferences:read","preferences:write","rcs:read","rcs:write","rcs_management:read","rcs_management:write","realtime:read","realtime:write","request_logs:read","request_logs:write","service_accounts:read","service_accounts:write","sms:read","sms:write","sms_management:read","sms_management:write","trust:read","trust:write","verify:read","verify:write","verify_management:read","verify_management:write","voice:read","voice:write","voice_management:read","voice_management:write","webhooks:read","webhooks:write","whatsapp:read","whatsapp:write","whatsapp_management:read","whatsapp_management:write","workspace:read","workspace:write","org:access_restrictions:read","org:access_restrictions:write","org:audit:read","org:audit:write","org:billing:read","org:billing:write","org:ip_pools:read","org:ip_pools:write","org:members:read","org:members:write","org:settings:read","org:settings:write","org:trust:read","org:trust:write","org:workspaces:read","org:workspaces:write"],"code_challenge_methods_supported":["S256"],"token_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post"],"revocation_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post"],"authorization_response_iss_parameter_supported":true}

How we test this:

• We look for OAuth authorization server metadata (RFC 8414): at /.well-known/oauth-authorization-server on your site, through the authorization_servers your protected-resource metadata (RFC 9728) names, and on your mcp. host.
• It passes when it lists S256 in code_challenge_methods_supported, has scopes_supported, and has a registration_endpoint or client_id_metadata_document_supported, as the MCP authorization spec asks.
• With no OAuth metadata, it isn't counted.

How we test this:

• On your docs surface we look for an install in each of four languages: TypeScript/JavaScript (npm, yarn, pnpm or bun), Python (pip, poetry or uv), Go (go get) and Java (a Maven <artifactId> or a Gradle implementation line).
• All four must appear.
• This shows how to install, not that a package is official.
• If none of the pages we read is a quickstart or SDK page, a miss isn't counted: it can't fail you or withhold your score.
• Ours, not AgentReady's.

How we test this:

• In the OpenAPI spec AR-ACT-02 found, we look for a POST operation on a path containing mail, email, message or send.
• No spec counts as a fail.
• Ours, not AgentReady's.

What our check kept, up to 60 lines or 6 KB

mpare published monthly deposits. Sending rates appear when Bird publishes them for each plan. Select a currency to see available prices. USD Free $0 1K emails / month included Get Started Sending stops at the Free plan limit Startup $15 / month Approx. 37.5K emails / month Get Started Deposit becomes spendable Bird

How we test this:

• On the pricing page AR-READ-11 reads, we look for "free" within 300 characters of a number followed by emails, messages or sends and a period (a month, a day, or 30 days), like "3,000 emails/month" or "4,000 sends in any rolling 30-day window", in the raw text (no JavaScript run).
• A one-time allowance with no period doesn't count.
• Ours, not AgentReady's.