Nowhere in your documentation does an agent learn how to get a key without a human.

No management API, service account or programmatic key creation is described in the pages we read.

11/ 16

A · Discovery: 6/6
B · Agent entry: 2/4
C · Registration: 0/1
D · Provisioning: 1/3
E · Integration: 2/2

of the 16 points that apply to you and we could measure · 1 of 17 were not scored

You 11 · category median 9 · best inngest.com 11 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+3points, taking 11/16 to 14/16

This is the whole list: everything we could measure and you do not pass. Another 1 point sits behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

1
Programmatic key provisioningan afternoon · +2
Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.
2
Agent entry pointan afternoon · +1
The file is there and it states a policy rather than a procedure. It counts when it names a credential, an endpoint or a way to get an account: the path from nothing to a working key, in steps. Ours is at /agent-signup.md and it is 1.7 kB.

Then, when you have room

OAuth dynamic client registration a project · +1Publish OAuth authorization server metadata with an RFC 7591 registration_endpoint in it. It is the only standard way an agent registers itself without a human.
Signup reachable without a browser a project · +1Let https://app.inngest.com/sign-up?ref=nav render its form in server HTML and stop refusing non-browser requests to it.

Take it with you

4 of the checks an agent depends on, inngest.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on inngest.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Read the audits in full What the same run on inngest.com costs

Against background jobs and workflows

You lead the 7 we have scanned in this category.

1
inngest.comyou
11/16
2
trigger.dev
11/16
3
temporal.io
10/15
4
windmill.dev
9/15
5
upstash.com
8/15
6
restate.dev
6/13
7
hatchet.run
6/15

Where competitors pass and inngest.com does not

Signup reachable without a browsertrigger.dev
Programmatic key provisioningtemporal.io

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

DiscoveryCan an agent find and read you?

6/6

Agent entryIs there a door built for a machine?

2/4

RegistrationCan an agent get an account?

0/1

ProvisioningCan it get credentials without a human?

1/3

IntegrationCan it ship working code?

2/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

A · Discovery

PASS
Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
PASS
llms.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
PASS
Docs 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
PASS
On-demand agents not blockedExplicitly allowed: ChatGPT-User
PASS
Paths robots.txt points at answerthe 2 concrete paths your robots.txt allows all answer
PASS
No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

PART
Agent 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.A markdown file written for a machine turns a guessing game into a procedure it can follow.
FAIL
OAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomainsRFC 7591 is the only standard path by which an agent can register itself without a human.
PASS
MCP surfaceLive MCP endpoint at https://api.inngest.com/mcp, answered 401 with an auth challenge

C · Registration

UNMEASURED
No 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.
FAIL
Signup reachable without a browserhttps://app.inngest.com/sign-up?ref=nav is reachable, but its form needs JavaScriptIf a bare HTTP request gets a 403, the agent never sees the form at all.

D · Provisioning

FAIL
Programmatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
PASS
Free 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

PASS
Typed 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
PASS
Machine-readable API descriptionDocs serve markdown to machines, at https://www.inngest.com/docs

What we discovered on the way

Docs: https://www.inngest.com/docs · found on a subdomain
Pricing: https://www.inngest.com/pricing?ref=nav · linked from the site
Signup: https://app.inngest.com/sign-up?ref=nav · linked from the site
npm package: inngest (registry guess)
GitHub: inngest/inngest
Package licence: Apache-2.0
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none