Head to head · Human approval · October 2026 research run

Inngest vs Permit MCP Gateway

Inngest scores 73.1 (BB) on agent readiness against Permit MCP Gateway's 57.3 (C), and leads in 5 of 7 scored categories. Permit MCP Gateway leads on agent ergonomics and security & auth. Both do human approval.

Best human approval and handoff for AI agents · All 66 human approval comparisons

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Best auth and delegated access for AI agents · All 168 agent auth comparisons

Which one, for what

Inngest BB

Best for A TypeScript, Python or Go team that already runs agent steps as durable functions and wants a cheap, long wait for a human answer.

Ahead on

  • Reliability, 72 against 55
  • Schema & documentation, 89 against 53
  • Payments & pricing, 60 against 30
  • Maintenance & community, 88 against 28
  • Transparency & trust, 54 against 46

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

No reviewer inbox, Slack app or email, so the human side is your code

Permit MCP Gateway C

Best for A security team that wants approvals and per-user limits on MCP tools across many clients without touching agent code.

Ahead on

  • Agent ergonomics, 83 against 76
  • Security & auth, 80 against 74

Watch for

Approvals and on-premises deployment are Enterprise only, priced on request

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Inngest +60

Inngest 88

TypeScript SDK 4.26.2 on 29 October 2026 (30). Since 3 August, 15 TypeScript SDK releases (4.15.0 to 4.26.2), server releases v1.42.0 to v1.49.0 and changelog entries on 7 August, 12 August and 6 October (20). Responsiveness per the 1 October check, not re-read on 1 November (GitHub's pages and API refuse us), with 55 open issues and 182 open pull requests on the server repository, reply times not sampled (15 of 25). Current official SDKs in TypeScript, Python (0.5.19 stable, 0.5.20a1 on 30 October) and Go (15). CI badge on main and a Node 20 floor (8 of 10).

Permit MCP Gateway 28

No release notes or changelog for the gateway, and the docs changelog page still says the Canny changelog has no entries after 16 May 2024. The newest gateway capability recorded in the docs repository is the HTTP egress proxy, added on 28 July and extended on 30 July 2026, 97 days before this check (10). The gateway docs changed on 17 and 20 September and 6 October 2026 with rewrites and new answer blocks. Docs commits are not releases or changelog entries, and the release dates of the @permitio/agent-security-cli package could not be read, so no dated release falls in the 90 days from 6 August (0). Closed service with a Slack community and support email (5 of 15). Permit SDKs in six languages for the policy API, none needed for the gateway (10 of 15). The docs repository's only GitHub workflow, an Algolia crawl, was removed on 17 September; a Dependabot config and a Netlify build with link checks remain, and the line keeps its earlier partial value (3 of 10).

Schema & documentation Inngest +36

Inngest 89

OpenAPI 3.0.3 for REST API v2, 35 paths, at api-docs.inngest.com/api-specs/v2.json (25). llms.txt on the main site and the API docs, plus llms-full.txt and a .md copy of each API page (10). The wait docs say when to use waitForSignal instead of waitForEvent and spell out the race where an early answer is missed (15 of 20). Typed SDKs in TypeScript, Python and Go. The if match is a CEL string (12 of 15). Many code examples and 429 and error responses in the spec (12 of 15). Dated changelog, release notes that flag breaking changes, and versioned v1 and v2 APIs (15).

Permit MCP Gateway 53

The gateway adds no tools of its own and passes upstream tool schemas through. Permit's management API has an OpenAPI-backed reference (15 of 25). No llms.txt or Markdown copies of the docs found (0). The docs say what the agent sees while waiting, what a rejection returns and what the gateway doesn't cover (15 of 20). Approval rules are toggles and trust levels in the dashboard, with nothing for the agent to type (8 of 15). The waiting message, the rejection error and the 429 body are documented with examples (12 of 15). The product changelog on Canny has no entry after May 2024, and the gateway has no changelog (3 of 15).

Payments & pricing Inngest +30

Inngest 60

No machine payment protocol (0). Per-execution prices published, $50 per million over the Pro allowance, tiering down to $15 per million (20). Free plan of 50,000 executions a month with no card (20). A person signs up in the browser for Cloud (0). The local Dev Server runs without an account, but the rubric scores the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Permit MCP Gateway 30

No machine payment protocol (0). The gateway pricing page publishes plan prices, Community at $0, Pro from $25 a month and Enterprise on request, with nothing priced per call (10). Community is free with no credit card, but approvals and on-premises deployment are Enterprise only, so the line keeps its earlier partial value (10). A person signs in through the browser consent flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Inngest +17

Inngest 72

Status page at status.inngest.com (incident.io) with component history (20). Its feed lists 14 incidents from 10 August to 20 October, and each one hit part of the service. Degraded or delayed function execution on 10, 19 and 20 August, 4 and 18 September (the latter labelled partial outage, 16:31 to 18:33 UTC), 26 September and 9, 10 and 12 October (the 9 October one a 44-minute Rackspace network outage), Connect routing delays for "a subset of customers using Inngest Connect" on 24 and 26 August, delayed observability on 20 August and 26 September, and intermittent Event API errors on 20 October (updates from 13:07 to 13:20 UTC, components marked affected until 15:33 UTC, labelled degraded performance). The 7 and 16 July incidents behind the earlier 5 have left the 90-day window. Minor incidents only (20 of 30). Plan limits are published with numbers (concurrency, queue depth, event size, 5,000 events per send), but no request rate for the event or REST API (10 of 15, per the 1 October check). The OpenAPI spec documents 429 on /events and invoke, event IDs deduplicate for 24 hours and functions take idempotency keys, with no Retry-After guidance found (12 of 15, per the 1 October check). No SLA on the pricing page, which mentions only support response SLAs (0). step.waitForEvent(), step.waitForSignal() and the Cloud MCP are GA (10).

Permit MCP Gateway 55

Permit's status page at permit-io.instatus.com lists Backend, OPAL, Frontend, Marketing Website, PDP Deltas and PDP Data, all US East, with no component for the gateway or agent.security. A vendor page with no component for the product takes 15 (15). The incident line is read from the components the gateway depends on. The architecture page says the hosted gateway calls the Cloud PDP on every tool call and that gateway policies update through OPAL. history.atom shows three OPAL US East outages since 6 August, on 27 October (29 minutes), 1 November (9 minutes) and 4 November (15 minutes), each one component for under an hour, so minor (20). The hosted gateway rate-limits per client IP on sign-in, client registration and MCP endpoints, and the docs say they don't publish the numbers (0). A 429 carries a rate_limited JSON body and the docs say to back off and grow the wait on each retry, with no safe-retry guidance for tool calls that write, which this run scores 10 (10). The gateway pricing page lists 99.95 per cent uptime on Pro and 99.99 per cent on Enterprise, and Permit's pricing page an optional 99.99 per cent SLA, but no SLA document was found (0). The gateway carries no beta label, and approvals carry an Enterprise label (10).

Transparency & trust Inngest +8

Inngest 54

Server under the SSPL with delayed Apache-2.0 publication, which isn't an OSI licence, and Apache-2.0 SDKs (20 of 30). The privacy policy (updated 2026-04-03) gives no retention periods, trace retention by plan sits on the pricing page, and we found no DPA. The terms and the privacy policy give different San Francisco addresses (12 of 30). Dated changelog entries and a v4 SDK migration, but no deprecation policy with a notice period (8 of 20). The security page says all data sits in AWS databases in the United States, and the privacy policy names GA4, Google Tag Manager, Stripe, AWS and iubenda. No full subprocessor list we could read (12 of 20). Per the 1 October check, not re-read on 1 November.

Permit MCP Gateway 46

Closed service under terms whose revision list ends on 1 July 2026 (termination and amendment provisions), naming Permit Inc., a Delaware corporation, under Delaware law (15 of 30). The docs say hosted traffic, including tool arguments and upstream responses, passes through Permit's infrastructure, and that customer-controlled or on-premises deployments keep it in your network. The terms let Permit delete data on termination, the trust centre says retention is limited by purpose, contract and legal requirements, and gateway audit logs are kept 7 days on Community (15 of 30). The terms let Permit change the service without notice, and the changelog stopped in May 2024 (0 of 20). The trust centre now lists nine subprocessors with their purposes (AWS, Datadog, Google, Twilio Segment, Mixpanel, Stripe, Sentry, Auth0, WorkOS) and promises at least 14 days' notice of changes, and says hosted services run on AWS, with no locations per provider (15 of 20).

Agent ergonomics Permit MCP Gateway +7

Inngest 76

The Cloud MCP has 34 tools (14 shared with the Dev Server, 20 Cloud-only) (5), while REST v2 responses can be sized with cursor pagination and optional output (20). We average the two surfaces to 12 of 25. Runs list with app, function, status and time filters (20). SDK error classes for non-retriable and retry-after cases and error responses in the spec (14 of 20). Event-ID deduplication, function idempotency keys and step memoisation, and the MCP docs mark which tools change state, though we didn't confirm annotations in the tool definitions (15 of 20). A wait needs an event name, a timeout and a match, and official SDKs cover TypeScript, Python and Go (15).

Permit MCP Gateway 83

It adds nothing to the agent's context, since the client keeps the upstream tool list (25). The approval queue has batch actions for the admin, but nothing pages or filters for the agent (10 of 20). The agent gets a waiting message with the timeout and a rejection error carrying the admin's reason, which it can act on (18 of 20). Each tool gets a low, medium or high trust level at import, close to read-only and destructive hints, and a dropped connection cancels the request instead of leaving it to run later (15 of 20). One URL change and no SDK, with Permit SDKs in six languages for the policy side (15).

Score by category

CategoryWeightInngestPermit MCP GatewayEdge
Reliability16%7255Inngest +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8953Inngest +36
Agent ergonomics13%7683Permit MCP Gateway +7
Security & auth14%7480Permit MCP Gateway +6
Payments & pricing10%6030Inngest +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8828Inngest +60
Transparency & trust7%5446Inngest +8
Negative events≤15-10
TotalBB 73.1/100C 57.3/100

Facts side by side

FactInngestPermit MCP Gateway
KindPlatformPlatform
VendorInngestPermit.io
Hosted endpointhttps://inn.gs/e/https://{subdomain}.agent.security/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402nono
LicenceSSPL with delayed Apache-2.0 (server), Apache-2.0 (SDKs)none
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-29none
Terms last updatedno date givenno date given
Privacy policy last updatedcouldn't be read2024-07-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

ReviewerInngestPermit MCP Gateway
KeelOperations and maintenance reviewer 3/5 Long waits on a server that breaks in minors 1/5 Terms allow change without notice
WardenSecurity auditor 2/5 The event key sits in the URL path 4/5 Timeouts reject and disconnects cancel

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Inngest

Waits are durable and cost nothing while suspended, with runs up to 30 days on Free and 366 on Business, and the Cloud MCP now signs in with read or write permissions. No reviewer inbox, Slack app or email, so the human side is your code.

Permit MCP Gateway

No SDK or client change, since the client points at the gateway URL and keeps its tool list, and each tool call is checked against Permit policy and logged. Approvals and on-premises deployment are Enterprise only, rate limits are unpublished, and the status page has no gateway component.

Before you call either

Inngest

  1. Use step.waitForSignal() when one run waits for one answer, and waitForEvent only when one answer resumes many runs
  2. Register the wait before you send the approval request, or check the external state first, since early events are missed
  3. Use a unique approval ID per tool call and match on it, so parallel approvals resolve independently
  4. Treat null or undefined as a timeout and decide on purpose whether that rejects, approves or escalates
  5. Ask for a read-only OAuth session for the Cloud MCP when you only inspect runs; write tools return insufficient_scope without write permission

Permit MCP Gateway

  1. Expect a waiting message before an approval-gated tool returns, and don't retry the call while it waits
  2. Read the rejection reason in the error and change approach instead of calling the same tool again
  3. Treat a timeout as a rejection and ask the user to have an admin online before a batch of destructive calls
  4. Stay connected while waiting, since dropping the connection cancels the request
  5. On a 429 with rate_limited, back off for a few seconds and grow the wait on each retry

Questions

Which is better for AI agents, Inngest or Permit MCP Gateway?

Inngest scores 73.1 (BB) on agent readiness against Permit MCP Gateway's 57.3 (C), and leads in 5 of 7 scored categories. Permit MCP Gateway leads on agent ergonomics and security & auth.

Other comparisons with Inngest or Permit MCP Gateway

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.