Mailchimp Transactional

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

# Algolia-Crawler-Verif: 1303ECCCE3636DE4

User-agent: *

Sitemap: https://mailchimp.com/sitemap.xml

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://mailchimp.com/developer/transactional/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" xmlns:xhtml="http://www.w3.org/1999/xhtml"><sitemap><loc>https://mailchimp.com/main.xml</loc></sitemap><sitemap><loc>https://mailchimp.com/presents/sitemap/sitemap-index.xml</loc></sitemap><sitemap><loc>https://mailchimp.com/developer/sitemap.xml</loc></sitemap><sitemap><loc>https://mailchimp.com/find-an-expert/sitemap.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

# Mailchimp - Complete Web Content Analysis

> Comprehensive analysis and documentation of web content

## Executive Summary

This documentation contains analysis of **990 web pages** across **19 categories**. Each page has been analyzed for content quality, categorized by type, and ranked by importance. This comprehensive resource provides insights into the structure and content of the analyzed website.

## Statistics Overview

- **Total Pages Analyzed**: 990
- **Categories Covered**: 19
- **High Importance Pages (4-5/5)**: 326
- **Medium Importance Pages (3/5)**: 597
- **Analysis Date**: 7/29/2025

---

## About (5 pages)

### [About Mailchimp](https://mailchimp.com/about/)

**Summary**: This page offers an overview of Mailchimp's history, mission, and corporate culture. It highlights the company's evolution and its commitment to empowering businesses with marketing technology.

**Key Points**:
- Mailchimp was founded in 2001 and acquired by Intuit in 2021.
- The company focuses on providing marketing solutions for businesses of all sizes.
- Mailchimp emphasizes data-backed marketing and customer support.

**Importance**: 5/5  
**Category**: about

---

### [Get To Know Our Senior Leadership Team At Mailchimp](https://mailchimp.com/about/founders/)

**Summary**: This page introduces Mailchimp's co-founders, Ben Chestnut and Dan Kurzius, detailing their roles, achievements, and the company's history, including its acquisition by Intuit.

**Key Points**:
- Introduces Mailchimp's co-founders and their roles
- Highlights company history and achievements
- Details acquisition by Intuit

**Importance**: 4/5  
**Category**: about

---

### [Mailchimp Brand Assets and Resources Guidelines | Mailchimp](https://mailchimp.com/about/brand-assets/)

**Summary**: This page outlines the guidelines for using Mailchimp's brand assets, including logos, colors, and other proprietary elements, to ensure consistent brand representation.

**Key Points**:
- Guidelines for proper use of brand assets.
- Importance of maintaining brand consistency.
- Downloadable brand assets available.

**Importance**: 3/5  
**Category**: about

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 property="og:description" content="Find all the Mailchimp API documentation and tools developers need to send marketing and transactional emails.">

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>Fundamentals</h1>
<h2>The basics</h2>
<h3>Sending via the API or SMTP</h3>
<h3>Using Mailchimp Transactional</h3>
<h3>Contact lists</h3>
<h3>Mailchimp Transactional and Mandrill</h3>
<h2>Getting started</h2>
<h3>Launch Mailchimp Transactional</h3>
<h3>Set up your sending domain</h3>
<h3>Sending messages</h3>

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

<div data-language="json" class="fern-code-block not-prose bg-card-background border-card-border rounded-3 shadow-card-grayscale group relative mb-6 mt-4 flex w-full border language-json">

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

tsch IT Italiano Request a demo: +1 (800) 315-5939 Hi, %s Back Close Main Menu Account Audience Campaigns Account Log Out Mailchimp Home Log In Start Free Trial 50% Off 1M+ Emails for 12 months**. Contact Sales today . Email Marketing Email Marketing Email & SMS Transactional Email Marketing Email & SMS

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

> This page is for Mailchimp Transactional.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://mailchimp.com/developer/llms.txt.

# Fundamentals

> Learn the basics to start sending with Mailchimp Transactional.

## The basics

Mailchimp Transactional is a powerful email delivery service that lets you send personalized, one-to-one emails like password resets, order confirmations, and welcome messages.

To sign up for Mailchimp Transactional, you need a Mailchimp account. You can try the [Mailchimp Transactional demo](https://mailchimp.com/help/transactional-email-demo/) with any level account, but to use the full version you must have a [Standard or Premium account](https://mailchimp.com/help/add-or-remove-transactional-email/).

### Sending via the API or SMTP

Once you’ve [set up your account](/developer/transactional/docs/fundamentals#getting-started) and [verified your domain](/developer/transactional/docs/authentication-delivery#authentication), there are two routes to start sending: via the [Transactional API](/developer/transactional/guides/quick-start) or with [SMTP integration](/developer/transactional/docs/smtp-integration). If you’re already sending transactional emails through SMTP, you can typically change your SMTP credentials to Mailchimp Transactional’s and begin sending immediately. SMTP is a sending-only protocol, but the Transactional API allows you not only to send but also to view and parse reporting data in your own app or system. The API also offers more comprehensive integration, so it reports more specific errors when sending.

There are no discernible differences in terms of deliverability between using the API or SMTP integration—the actual process Mailchimp Transactional uses to send your emails is the same for both, and ISPs will see both your information and Mailchimp’s in your message headers.

Generally, the Transactional API is faster in terms of accepting mail because HTTP is less “chatty” than SMTP, but we’ve taken steps to help reduce the latency when you’re using SMTP, so you may not see as much of a difference between the two. If speed is a consideration, you may want to test both, including any content generation, to see which is faster overall for your particular environment.

Mailchimp Transactional offers many ways to customize how your emails are tracked, tagged, and more. Throughout the documentation, you’ll often see parallel instructions, one using the API, and one using SMTP. To review the full list of Transactional API endpoints and parameters, see [the API Reference](/developer/transactional/api); for a complete list of custom SMTP headers, check out [the SMTP docs](/developer/transactional/docs/smtp-integration#customize-messages-with-smtp-headers).

### Using Mailchimp Transactional

Whether you send via the API or SMTP, Mailchimp Transactional has a host of features to help optimize, track, and analyze your sends.

To learn the basics of sending—like scheduling, prioritization, and unsubscribing—check out the [outbound email docs](/developer/transactional/docs/outbound-email). You can create [templates](/developer/transactional/docs/templates-dynamic-content) that let you reuse email designs and inject dynamic content with one of several merge languages. And if you need to send email on behalf of multiple clients or separate sending for different users, you can set up [subaccounts](/developer/transactional/docs/subaccounts) as well.

Once you’ve started sending, you can monitor your [reputation](/developer/transactional/docs/reputation-rejections), which is partly determined by your ratio of bounces, spam complaints, and other factors to overall sending. You can also add [tags and metadata](/developer/transactional/docs/tags-metadata) to help track your messages, alongside other [reporting tools](/developer/transactional/docs/activity-reports) like open and click tracking, Google Analytics, and more.

And finally, to receive and respond to information about your email events, you can set up [inbound email processing](/developer/transactional/guides/set-up-inbound-email-processing) as well as [webhooks](/developer/transactional/docs/webhooks), or set up [conditional rules](/developer/transactional/docs/rules-engine) that let you take specific actions when events or messages meet criteria you’ve set.

### Contact lists

Contact lists cannot be uploaded or stored in Mailchimp Transactional. Your application's database should serve as the source of truth for user emails and contact lists; you will only pass that information to Mailchimp in your API request or SMTP message when you’re ready to send an email.

> **Note**
>
> **Note**:\*\* \*\*If you’re looking for a service that provides list management and the ability to create and track bulk emails, you should use Mailchimp, rather than Mailchimp Transactional. View our [Acceptable Use Policy](http://mailchimp.com/legal/acceptable_use/) for additional details.

### Mailchimp Transactional and Mandrill

Throughout the Mailchimp Transactional guides and docs, you may notice the occasional reference to the product’s original name, Mandrill. Mandrill is in the process of being fully integrated into Mailchimp proper, and while this process is ongoing, you will from time to time see artifacts of this migration.

## Getting started

If you have a Mailchimp Standard plan or higher, you can enable Mailchimp Transactional from the [Billing](https://us1.admin.mailchimp.com/account/billing-plan/) section of your account; if you don’t have a Mailchimp account, you can [sign up directly](https://login.mailchimp.com/signup/?entrypoint=mandrill) for Mailchimp Transactional.

Once you enter your information, you can adjust how many blocks of emails you want to purchase each month, as well as set your preferences for when you run low on emails. You can change these settings at any time on the [Transactional page](https://us19.admin.mailchimp.com/transactional/) of your Mailchimp account.

### Launch M

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://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"mailchimp.com","item":"https://mailchimp.com/developer"},{"@type":"ListItem","position":2,"name":"Essential email and SMS messages, delivered every time | Mailchimp Developer","item":"https://mailchimp.com/developer/transactional"}]},{"@context":"https://schema.org","@type":"TechArticle","headline":"Essential email and SMS messages, delivered every time | Mailchimp Developer","url":"https://mailchimp.com/developer/transactional","inLanguage":"en","dateModified":"2026-10-29T17:52:09.818Z","isPartOf":{"@type":"WebSite","name":"Mailchimp Developer","url":"https://mailchimp.com"}}]

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.

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 MCP do? Our MCP mirrors what our API can already do. Tool Description account_status Check account status build_template Build/construct a template call_api Call a Transactional Messaging API endpoint describe_api Describe a specific API endpoint (parameters, schema) diagnose_failed_send Diagnose why a se

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

yarn add @mailchimp/mailchimp_transactional
pip install mailchimp_transactional

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.

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

rding help regarding Transactional Messaging, and submit feedback. What can the MCP do? Our MCP mirrors what our API can already do. Tool Description account_status Check account status build_template Build/construct a template call_api Call a Transactional Messaging API endpoint describe_api Describe a specific

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": "run-bulk-jobs",
      "type": "skill-md",
      "description": "Use when a Mailchimp Marketing API job is too large for one request—importing or updating thousands of contacts, pulling bulk report data, or any loop that would run for minutes—and you need to pick between the bulk endpoints, poll a batch without becoming a rate-limit problem, and tell a partially failed job from a successful one.",
      "url": "/.well-known/agent-skills/run-bulk-jobs/SKILL.md",
      "digest": "sha256:5b74ddb46afad51ed0ee8b1dc1c8091ac9b173eacfcae15f0c61562504cee892"
    },
    {
      "name": "set-consent-correctly",
      "type": "skill-md",
      "description": "Use when adding or updating Mailchimp contacts from a signup form, checkout, CRM sync, or any flow where a person chose whether to receive marketing email or SMS, and you need to record that choice without overwriting consent they already gave.",
      "url": "/.well-known/agent-skills/set-consent-correctly/SKILL.md",
      "digest": "sha256:e948e6923c853f47562a0808fbd34b43b93ececffadd82cdd31ce33468d368f9"
    },
    {
      "name": "set-up-oauth",
      "type": "skill-md",
      "description": "Use when implementing Mailchimp OAuth 2 in an application that connects other people's Mailchimp accounts, including the authorize redirect, the callback and code exchange, and storing access tokens for one or many connected accounts.",
      "url": "/.well-known/agent-skills/set-up-oauth/SKILL.md",
      "digest": "sha256:a27e6c245e610389c4b8ad6fc0fb802d4dbea156f024b586f97e1e1d096b753c"
    },
    {
      "name": "subscribe-to-webhooks",
      "type": "skill-md",
      "description": "Use when building a Mailchimp webhook integration—creating a webhook through the API, verifying delivery signatures, or keeping an external database in sync with an audience—and you need the handler to survive duplicate deliveries and avoid echoing your own writes back at yourself.",
      "url": "/.well-known/agent-skills/subscribe-to-webhooks/SKILL.md",
      "digest": "sha256:6ecd58edca09d239ce6d51ff5e0b88f6b4942d8d514e94f75e9b2017634f5e54"
    }
  ]
}

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.

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.

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.