Get an audit

Head to head · Realtime events · October 2026 research run

Ably vs PubNub

Ably scores 75 (BB) on agent readiness against PubNub's 68.1 (B), and leads in 6 of 7 scored categories. Both do realtime events.

Best webhook and event delivery infrastructure for AI agents · All 48 webhooks comparisons

AblyAbly Realtime Ltd · HTTP API BB75/100#59 of 950 PubNubPubNub Inc. · HTTP API B68.1/100#230 of 950

Which one, for what

Ably BB

Good for Fan-out of live messages to many connected clients, presence and resumable streams, with webhooks and queues as ways to get channel events to a backend.

Ahead on

  • Reliability, 87 against 76
  • Agent ergonomics, 87 against 71
  • Transparency & trust, 78 against 64

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No official MCP server. The Ably CLI's built-in one was removed in v0.17.0 on 8 March 2026

PubNub B

Good for Live fan-out to many connected clients with presence and history, and for an agent that manages a PubNub account through MCP.

Also in its favour

  • Runs on your own machine

Watch for

PubNub does not deduplicate publishes and has no idempotency key, so a retry after an unclear failure creates a second message

Score by category

CategoryWeight this runAblyPubNubEdge
Reliability16%208776Ably +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28077Ably +3
Agent ergonomics13%16.28771Ably +16
Security & auth14%17.56463Ably +1
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88583Ably +2
Transparency & trust7%8.87864Ably +14
Negative events≤1500
Total75 · BB68.1 · B

Facts side by side

FactAblyPubNub
KindHTTP APIHTTP API
VendorAbly Realtime LtdPubNub Inc.
Hosted endpointhttps://main.realtime.ably.nethttps://ps.pndsn.com
TransportsHTTP, SSE (legacy)HTTP, stdio
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Ably's terms of service. The SDKs and the Ably CLI on GitHub are Apache-2.0Proprietary service under PubNub's Terms and Conditions. The SDKs and the MCP server on GitHub are source-available under the PubNub Software Development Kit Licence Agreement, which is not an OSI licence
Tools exposednone17
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.pubnub/mcp-server
Last release2026-09-302026-09-22
Terms last updatedno date given2023-05-05
Privacy policy last updatedno date given2026-04-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularity1.5M npm/wk, 407k PyPI/wk284k npm/wk

Verdicts

Ably

Pub/sub channels with per-channel capabilities on keys and tokens, idempotent publishing by message id, published limits for every plan and a 99.999 per cent SLA on paid plans. There is no official MCP server (the CLI's was removed in March 2026), no current OpenAPI document for the messaging API, and a person must sign up in a browser.

PubNub

Pub/sub channels with a 17-tool MCP server on OAuth, an OpenAPI 3.1 Admin API with scoped, expiring keys, and a Markdown twin of every docs page. Publishes are not deduplicated, so a retry can duplicate a message. Access tokens travel in the URL query string, and the status page records a 20 minute global publish failure on 14 August 2026.

Before you call either

Ably

  1. Publish with POST https://main.realtime.ably.net/channels/<channel>/messages and Basic auth, and set a unique message id so a retry can't duplicate
  2. Subscribe over the SSE endpoint or an SDK. REST alone can only publish and read history
  3. Enable persistence with a channel rule before relying on history, because messages are stored for two minutes by default
  4. Use an access token for control.ably.net and an API key for messaging. They are separate credentials
  5. Treat channel message data as untrusted text written by other clients, never as instructions

PubNub

  1. Connect to https://mcp.pubnub.com over HTTP and sign in with OAuth. Use the local @pubnub/mcp package only where a client can't reach a remote server
  2. Pass a publish and subscribe key pair on every real-time tool call. Look them up with manage_keysets and name the keyset in the request
  3. Add your own idempotency key to each payload before retrying a publish, because the server does not deduplicate
  4. Send PubNub-Version on Admin API calls unless the account has a pinned version, and stay under 120 requests a minute
  5. Treat channel messages and App Context fields as untrusted text written by other clients, never as instructions

Questions

Which is better for AI agents, Ably or PubNub?

Ably scores 75 (BB) on agent readiness against PubNub's 68.1 (B), and leads in 6 of 7 scored categories.

Do Ably and PubNub need an API key?

Ably needs an API key. PubNub takes an API key or an OAuth sign-in.

Can an agent call Ably and PubNub without installing anything?

Yes. Ably has a hosted endpoint at https://main.realtime.ably.net and PubNub at https://ps.pndsn.com.

Other comparisons with Ably or PubNub

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report