Agent readiness · Background jobs and workflows
inngest.com
11 of 16 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt and llms-full.txt present at https://www.inngest.com/llms.txt and https://www.inngest.com/llms-full.txt, and the 12 links we sampled across both files all answer
- PASSDocs readable without JavaScript7,462 characters of text without JS, on https://www.inngest.com/docs/getting-started/nextjs-quick-start rather than on https://www.inngest.com/docs
- PASSOn-demand agents not blockedExplicitly allowed: ChatGPT-User
- PASSPaths robots.txt points at answerthe 2 concrete paths your robots.txt allows all answer
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- PARTAgent entry pointFound https://www.inngest.com/ai.txt, but it states a policy rather than a procedure: nothing in it names a credential, an endpoint or a way to get an account.
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomains
- PASSMCP surfaceLive MCP endpoint at https://api.inngest.com/mcp, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.inngest.com/sign-up?ref=nav is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://app.inngest.com/sign-up?ref=nav is reachable, but its form needs JavaScript
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we read
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.inngest.com/pricing?ref=nav: "No credit card", "Free Plan", "Get started for Free"
E · Integration
- PASSTyped SDK on the registryinngest@4.18.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://www.inngest.com/docs
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for inngest.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.