RXed AI News

1Password is positioning itself as the credential layer for agentic AI — Credential Broker, agent hooks for Claude Code and Cursor, and SDKs that let agents read secrets at runtime. The developer surface (1password.dev) is strong, but the main site lacks structured data and llms.txt, and enterprise pricing is quote-only.

Airtable

Airtable is one of the most agent-ready platforms scored: an official MCP server with OAuth, a skills library, and full CRUD coverage. The missing piece is agent payment — no programmatic checkout exists.

Asana

Asana runs an official MCP server with 42 tools covering core actions (task creation, project management, search), backed by a mature REST API at v1.0 with 1,500 req/min on paid tiers. Agent payment is the only real gap. The cheapest grade-moving fix: publish a .well-known/mcp.json server card so agents can discover the MCP endpoint without documentation.

Cloudflare

Seventeen official MCP servers, an OpenAPI-backed v4 API and first-party x402/MPP support make this the most agent-usable vendor in the index. Conflict noted: Cloudflare also sells the rival Agent Readiness score and gates AI crawlers on customer sites.

Deel is one of the most agent-ready platforms in the index — an official MCP server with 355 tools, OAuth 2.1 with dynamic client registration, explicit AI-crawler welcome in robots.txt with Content-Signal directives, and a comprehensive llms.txt. The gap is on the money side: an agent cannot pay Deel programmatically, and there is no sandbox for safe testing.

Docusign is strongly agent-ready thanks to an official MCP server (open beta) covering envelope creation, status checking, and workflow automation, plus a comprehensive REST API surface across eSignature, CLM, and Agreement Manager. OAuth 2.0, self-serve sandbox, and SDKs in 7 languages lower the integration barrier. The main gaps: no agent payment protocol support, mediocre recent uptime (91% over 30 days), and a ToS that technically prohibits 'robots' while simultaneously marketing an official MCP server to AI agents. Adding an llms.txt and adopting any agent payment protocol would move the score.

Dropbox runs two official MCP servers and a mature REST API with full file CRUD, but the MCP path is interactive-consent-only with no headless refresh tokens, and no agent payment protocol exists. The cheapest grade-moving fix: publish a .well-known/mcp.json card and add an M2M OAuth grant so background agents can hold long-lived sessions.

e-Boekhouden has a functional SOAP API and a new REST API, but no official agent protocol, no status transparency, and no published rate limits. The cheapest upgrade: publish rate limits and a status page so agents can plan around constraints they currently cannot discover.

Exact Online has a broad REST API with 200+ endpoints and an active partner ecosystem building MCP integrations, but Exact itself publishes no agent protocol and the tight rate limits and app-review gate add friction for autonomous agents.

GitHub

The index's protocol benchmark: an official remote MCP server GA since 04/09/2025, published OpenAPI descriptions, and Terms that explicitly permit machine accounts. The gap is money — plans and Marketplace apps are still bought by a human in the UI.

HubSpot is the strongest agent-ready CRM in the index. Official MCP server (GA April 2026) with read/write on 12 CRM object types, comprehensive API with 100-190 req/10s limits, well-structured llms.txt, and OAuth with scoped credentials. The only material gap is agent payment capability — subscription billing has no programmatic checkout path.

Lightspeed has strong, well-documented REST APIs with OAuth 2.0 and published rate limits — solid infrastructure for programmatic access. But the Acceptable Use Policy explicitly prohibits 'bots and unapproved automation,' creating a legal contradiction with the developer-friendly API surface. No official MCP server exists. The cheapest upgrade: clarify in the AUP that API-authorized integrations are approved automation, removing the ambiguity that makes compliance counsel nervous.

LinkedIn

Beyond OAuth sign-in and 150 posts/day per member, every API is partner-gated behind multi-month review; messaging, connections and people search have no API at all, there is no official MCP server, and LinkedIn litigates scrapers out of existence.

Strong API surface for marketing automation, but the official MCP only covers transactional email — the marketing API that most agents would need has no official agent protocol. Repeated pricing overhauls since the Intuit acquisition make long-term agent cost planning unreliable.

Microsoft 365

Microsoft 365 has one of the deepest API surfaces of any SaaS platform: Microsoft Graph covers email, calendar, files, Teams, SharePoint, and dozens more services with a single endpoint. Documentation is best-in-class. The gap is discoverability — the main domain redirects to a login portal, and there is no first-party MCP server (community servers cover 300+ tools but are not Microsoft-maintained).

Mollie has no verified agent payment protocols or capabilities, despite superficial MCP references.

Notion

One of the smoothest agent onboardings: official hosted MCP at mcp.notion.com plus a date-versioned REST API, both free on every plan. Ceilings are ~3 requests/second per connection, OAuth-only MCP that needs a human present, and no billing API at all.

Odoo scores Strong (7) thanks to full ORM API coverage, excellent documentation with the new JSON-2 API, and an open-source core that gives self-hosted agents unrestricted access. The main drag is the absence of any agent payment protocol and the Odoo Online plan gate that locks the external API behind the Custom tier.

Resengo's brand migration to Zenchef leaves agents in limbo: the legacy API is frozen, the successor API documentation is gated behind email requests, and there is no agent protocol surface at all. A restaurant booking platform that an agent cannot programmatically book through without a manual partnership agreement scores poorly on Act & transact.

A strong API for shipping automation with documented rate limits and multi-carrier coverage, but no agent protocol support and no machine-readable pricing or structured data — an agent can ship parcels but cannot discover or negotiate the service without prior knowledge.

Shopify

Shopify co-authored UCP with Google and ships official Catalog, Cart, Checkout and Order MCP servers; since 17 June 2026 agent registration is self-serve. But general-access agents must hand the buyer a continue_url — calling complete_checkout directly stays permission-gated.

Slack

Slack shipped an official MCP server (GA 17/02/2026) and courts agent builders, but its May 2025 terms cut conversations.history to 1 request per minute for commercially distributed non-Marketplace apps and ban using Slack data to train an LLM.

Stripe

The reference implementation for agent commerce: Stripe co-authors both ACP and MPP, runs an official MCP server at mcp.stripe.com, and issues merchant- and amount-scoped payment credentials. The main friction is a read-request allocation that penalises poll-heavy agents.

Teamleader scored 7 (Strong) — a comprehensive RPC-style API with OAuth, date-versioned endpoints, and multiple community MCP servers covering 100+ tools. The gap is the absence of any official agent protocol surface or agent payment path.

Trustpilot has a functional API behind an Enterprise paywall and actively hostile automation policies — bots, scrapers, and AI crawlers are explicitly prohibited in the ToS with legal threats attached. An agent can read public Business Units data with a free key but cannot act on reviews without an Enterprise contract.

A developer-first platform with one of the strongest API ecosystems in the industry — 1,800+ endpoints, OAuth 2.0 GA, 16 years of backward compatibility on a single API version. The official MCP server is read-only docs search; the execution-capable Labs alpha MCP server is unsupported. No agent payment protocols. Publish the Labs MCP server as GA with scoped OAuth and Twilio would move from strong to benchmark.

Typeform is one of the most agent-ready form platforms: an official MCP server covers core actions end to end, OAuth is frictionless, and the developer portal is strong. The gap is payment — forms collect money via Stripe/PayPal integrations, but no agent payment protocol exists for programmatic checkout.

Wix is one of the most agent-ready website builders: official MCP server with 12 tools covering site creation through API execution, comprehensive REST APIs across all business verticals, self-serve OAuth and API keys, and a clear llms.txt. The gap is on the payment side — programmatic checkout still bounces the buyer to a hosted page, and no agent payment protocol is supported yet despite the PayPal agentic-commerce partnership announcement.

X (Twitter)

An official MCP server sits on top of a hostile action surface: since 02/2026 self-serve apps cannot like, follow, quote-post or reply unsolicited, and a post containing a link costs $0.20 against $0.015 without one.

Yuki's absorption into Nmbrs delivers a real REST API with OAuth and sandbox, but the agent surface is immature — no official MCP, no llms.txt, no agent payment path, and pricing is hidden behind 'contact sales' for the payroll/accounting core. The community Pipedream MCP wrapper covers HR/payroll but not accounting.

Zapier

Zapier is the benchmark case for agent readiness in automation — official MCP server, AI catalog, WebMCP, and Content-Signal directives make it the most agent-welcoming platform scored so far. The gap is payment protocols: task metering is self-serve but no ACP/AP2/x402 surface exists.

A strong API-first platform with comprehensive docs and an official MCP server in early access, held back by the absence of any agent payment path and uncertainty around MCP server general availability. Ship the MCP server to GA and Zendesk would move from strong to benchmark.

Solid developer portal and free API, but the core action — taking a payment — lives in native SDKs, not the REST API. PayPal's MCP server does not cover Zettle operations.

Zoom runs an official MCP server and a comprehensive REST API that covers nearly every meeting action, but the MCP layer reads meeting intelligence rather than scheduling or joining. No agent payment protocol exists. The cheapest grade-moving fix: extend the MCP server to cover meeting creation and calendar scheduling so agents can act, not just read.