Can AI agents automate Inngest?

Inngest is automatable today through its REST API. The v2 API at https://api.inngest.com/v2 is documented as stable and still in development. It covers apps, functions, runs, traces, events, environments, webhooks, insights, sandboxes, and sessions. Requests send Authorization Bearer. API keys, which start with sk-inn-api-, are for scripts, CI, and AI tools and apply to v2. Signing keys, which start with signkey-, are the app credential and can also be sent as a bearer token. The v2 send-event endpoint is for testing and debugging, not high-volume ingestion. The Inngest CLI exposes every v2 endpoint as an inngest api subcommand, prints compact JSON by default, and uses INNGEST_API_KEY or --api-key. It targets the local Dev Server unless --prod is set. Inngest documents a Cloud MCP server at https://api.inngest.com/mcp, authenticated with the same API key, and a Dev Server MCP server at http://127.0.0.1:8288/mcp with no auth. Shared tools include list and get for apps, functions, runs, and traces, plus send_event, invoke_function, rerun, and cancel_run. The official TypeScript SDK package is inngest. It defines functions and sends events from Node.js, Bun, Deno, and edge runtimes. A Free cloud plan is $0 per month with no credit card required. Pro starts at $99 per month and Business at $499 per month. The pricing page says the core engine can be self-hosted. https://api-docs.inngest.com/llms.txt is a first-party API index. Zapier, Make, Power Automate, and n8n were not assessed. Computer-use viability is unassessed. API, CLI, and MCP each score 8. API is the best path because a bearer token calls the documented endpoints directly, without a CLI install or an MCP client.

Best path today: api · Overall automatability: 8/10