Inngest

Inngest invokes application functions through a public serve endpoint, commonly /api/inngest. The SDK adapter uses GET for development metadata, POST to invoke functions, and PUT to synchronize function configuration. Requests seen under the Inngest token are therefore part of an application that has been connected to Inngest, not visits to ordinary site pages.

Each Inngest environment has a pre-shared signing key. Requests to the serve endpoint include a signed timestamp, and the Inngest SDK verifies both the signature and freshness before exposing the invocation to function code. The same key also authenticates configuration sent from the application to the Inngest API.

Failed functions and step.run() work are retried by Inngest. The default is four retries in addition to the first attempt, though applications can change that setting. Completed step results are persisted, but external side effects still need idempotency so a retry cannot create duplicates.

This traffic coordinates code that the site owner registered with Inngest. It does not crawl pages for discovery and has no direct effect on AI answer inclusion or model training. Robots.txt is irrelevant to the serve endpoint because Inngest authenticates an explicit application callback with its signing key.