verapli
Sign inJoin free
Menu

Guides · devtools · Everyday developer services

Inngest

Durable workflow and background job platform. Each environment has a signing key; event keys let apps send events.

Researched · not yet run liveLast researched 25 October 2026 · Inngest · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in or create a Inngest account

    Sign in to Inngest. If you have no account yet, you create it yourself; verapli does not create accounts.

    • Guided by hand
    • Human step: You sign in

    Where: https://app.inngest.com/

  2. Copy the environment's signing key

    Select the environment (e.g. Production) and copy the key from its Signing Key tab into INNGEST_SIGNING_KEY. Or run stripe projects add inngest/app.

    • Guided by hand
    • After: Sign in or create a Inngest account

    verapli captures INNGEST_SIGNING_KEY here by plain code: encrypted in your browser, never shown to AI.

  3. Create an event key

    On the environment's Event Keys page create a key for the app that sends events and set it as INNGEST_EVENT_KEY. Keep it out of browser code.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a Inngest account

    verapli captures INNGEST_EVENT_KEY here by plain code: encrypted in your browser, never shown to AI.

What you end up with

Env varSecretFormatWhat it is
INNGEST_SIGNING_KEYsecretInngest signing key for one environment
INNGEST_EVENT_KEYsecretInngest event key used to send events

Pricing

  • Free tier: Hobby, 50k executions, 5 concurrent steps, 500k events/month.
  • Costs: Pro from $99/month.

Source [5]

For agents

The same entry as JSON: /api/v1/entries/inngest/app · requirements /api/v1/requirements/inngest/app · terms /api/v1/terms/inngest/app.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Inngest, and how long will it take?"
  → tools/call requirements { "provider_id": "inngest/app" }

Sources

  1. Stripe Projects CLI (Available providers) Inngest is listed as a Stripe Projects provider (Queue) · accessed 25 October 2026 · official
  2. projects.dev provider catalogue Catalogue service id inngest/app · accessed 25 October 2026 · official
  3. Inngest docs - Signing keys INNGEST_SIGNING_KEY env var; signing key per environment in its Signing Key tab; branch environments share a signing key · accessed 25 October 2026 · official
  4. Inngest docs - Creating an event key Event Keys page per environment; INNGEST_EVENT_KEY in the sender; separate key per app; never in browser code · accessed 25 October 2026 · official
  5. Inngest pricing Hobby free 50k executions, 5 concurrent steps, 500k events; Pro from $99/month · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Inngest is not affiliated with verapli.