# Agent Inbox vs Pushary (slim)

> Agent Inbox scores 67.5 (B) to Pushary's 58.5 (C) for human approval. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/agent-inbox-vs-pushary.md (~4,600 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/agent-inbox-vs-pushary.json · canonical https://www.anchorterminal.com/compare/agent-inbox-vs-pushary
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Agent Inbox scores 67.5 (B) on agent readiness against Pushary's 58.5 (C), and leads in 4 of 7 scored categories. Pushary leads on reliability and transparency & trust. Both do human approval.

- Agent Inbox: B 67.5, rank #440 of 1557 · https://www.anchorterminal.com/tools/agent-inbox.min.md
- Pushary: C 58.5, rank #851 of 1557 · https://www.anchorterminal.com/tools/pushary.min.md
- Agent Inbox, good for Agents that need a person's answer or approval while nobody watches the chat, over the channels people already use. Ahead on Security & auth, 72 against 66; Payments & pricing, 75 against 15; Maintenance & community, 70 against 63. Also Free to start without a card; Open source; No incidents deducted, where Pushary loses 3 points for them.
- Pushary, good for One developer running coding agents unattended who wants questions and approvals on a phone. Ahead on Reliability, 42 against 35; Transparency & trust, 76 against 54.

| Category | Agent Inbox | Pushary |
| --- | --- | --- |
| Reliability (16%) | 35 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 83 |
| Agent ergonomics (13%) | 85 | 86 |
| Security & auth (14%) | 72 | 66 |
| Payments & pricing (10%) | 75 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 63 |
| Transparency & trust (7%) | 54 | 76 |

| Fact (where they differ) | Agent Inbox | Pushary |
| --- | --- | --- |
| Vendor | Novu | Pushary |
| Hosted endpoint | `https://mcp.agentinbox.md` | `https://pushary.com/api/mcp/mcp` |
| Transports | Streamable HTTP | Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| Licence | MIT (CLI and MCP server source), hosted service on Novu Cloud only | MIT (skill, hooks and adapters) |
| Tools exposed | 12 | 26 |
| MCP registry | not listed | `io.github.Pushary/pushary` |
| Last release | 2026-11-13 | 2026-11-04 |
| Terms last updated | no date given | 2026-09-27 |
| Privacy policy last updated | no date given | 2026-09-28 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Payments & pricing, Agent Inbox +60: Agent Inbox 75 (No x402, MPP or L402 (0).); Pushary 15 (No machine payment protocol (0).)
- Transparency & trust, Pushary +22: Agent Inbox 54 (The CLI is MIT and the MCP server's source is public in novuhq/novu, but the hosted service needs Novu Cloud's private Agent Inbox endpoints, which self-hosted…); Pushary 76 (Closed hosted service under Estonian law with terms updated 1 November 2026, and MIT-licensed skill and adapters (18 of 30).)
- Reliability, Pushary +7: Agent Inbox 35 (Novu's Better Stack status page at novustatus.com lists the US and EU Novu API, WebSocket service, webhooks, dashboard and Inbox API, each at 100 per cent uptim…); Pushary 42 (No public status page found (0) and no incident history (5).)
- Maintenance & community, Agent Inbox +7: Agent Inbox 70 (@agentinbox/cli 0.5.0 was published on 13 November 2026 (30).); Pushary 63 (The service changelog's newest entries are dated 4 November 2026, covering CLI 1.9.61 to 1.9.100, Pushary for Mac 0.1.104 to 0.1.127, Server SDK 2.5.1, Python S…)
- Security & auth, Agent Inbox +6: Agent Inbox 72 (The MCP server signs in with OAuth through Agent Inbox's Clerk app, with dynamic client registration, and the AI app never sees the account's API key.); Pushary 66 (Bearer API keys in the form `pk_xxx.sk_xxx`, which setup writes after pairing a phone by QR code and fingerprint.)
