Skip to content
BotJobs

How this works

What we check, and what we don't

Bot Jobs is a directory of things people get Grok Bot to do. This page explains where the listings come from, what each evidence label means, how candidates are ranked, and — the part most directories leave out — the limits of all of it.

428
bots on file
428
listings reconciled
296
on both catalogues
282
creators credited

Where listings come from

Bots are ingested from the public catalogues that publish machine-readable APIs — currently grokbot.dev and bot.store — using their documented endpoints rather than scraping. Every record names the catalogue it was found in and links to it.

Both catalogues are read, which is unusual: none of the directories in this space index each other. 296 of our records appear on both, and the rest exist on only one — so the union is more complete than either source alone.

We take facts and nothing else: the official share URL, the creator, the originating post, tags. We never take a catalogue's write-up. Descriptions on this site are ours, written from the creator's own official listing, and a record cannot be published until somebody has written one.

What the evidence labels mean

Three levels. They answer different questions, and the top one is narrower than it sounds.

Listed
Turned up in a catalogue. We have not taken up its references.
Sourced
We know who built it and where it first appeared.
References checked
Its listing matches the official x.ai page. We have not watched it work.

The limit, stated plainly

“References checked” does not mean we ran the bot. It means we fetched its official x.ai page, confirmed it resolves, and captured what xAI says about it. We have not watched any of these bots work. If you repeat something from this site, repeat that distinction with it — a checked listing is not a tested bot, and we would rather be useful than impressive.

Why reconciliation matters

Every listing is checked against the official x.ai page rather than trusted from the catalogue. That is not a formality. Catalogues disagree with the source of truth: one bot is listed elsewhere as “Forge (dev factory)” while xAI calls it “Forge by Daniel”, and dozens more differ in the same way.

More usefully, it catches bots that no longer exist. We have found install links that are dead while other directories still list them as live. A directory whose whole promise is “here is a bot you can add” is worth nothing if the link 404s, so the check runs weekly and a bot that fails three times in a row is unpublished.

How candidates are ranked

A job page shows the bots we would actually put forward for that job, best fit first, each with a stated reason and its honest caveat. Ranking is comparative — candidates are assessed against each other for a specific job, not scored in isolation.

Fit scores are our editorial judgement. They are not user ratings, and there are no ratings or reviews anywhere on this site, because we have no users to collect them from. Inventing them would be the easiest way to look authoritative and the fastest way to stop being trustworthy.

Rejection is the default. Most bots fit most jobs badly, and a directory that maps everything to something has thrown away the only reason to read it. 2 jobs currently have no candidate at all and are listed as openrather than filled with something that does not do the work.

What we will not do

Check it yourself

Every record is a file in a public repository, so the data, its history and every correction are readable without asking us. The datasets are also available as JSON.

Corrections and removals: botjobs.dev/report. Independent project, not affiliated with or endorsed by xAI.