Add justdiscord.org

[umutxyp]

Adds JustDiscord as a list.

A Discord directory covering servers, bots, emojis, stickers and packs. Ownership is verified through Discord itself — a server's owner via OAuth guilds with MANAGE_GUILD, a bot's developer by inviting the application to the verification server and having it answer a challenge — and ranked order comes from votes, ratings and written reviews. Sponsored placements are sold separately, are labelled wherever they appear, and do not change any ranked position.

API

Documented at https://justdiscord.org/docs/introduction. /api/v0 deliberately follows the conventional bot-list shape so existing libraries work unchanged:

api_post	POST /api/v0/bots/:id/stats — server_count, shard_count, shards
vote check	GET /api/v0/bots/:id/check?userId=… → {"voted": 1}
voting_data	GET /api/v0/bots/:id/votes
api_all	GET /api/v1/listings?kind=bot (public, rate limited)
webhooks	https://justdiscord.org/docs/webhooks

Fields left null, and why

• view_bot / bot_widget — listing pages resolve by an owner-chosen slug (/bots/<slug>), not by application id, and there is no widget image. Neither can be built from a bot id alone. Happy to add view_bot in a follow-up if id-based lookup is added upstream on our side.
• api_get — GET /api/v0/bots/:id/stats exists but is scoped to the listing's own token, so it can't be used to look up an arbitrary bot.
• owners — the schema pattern requires the legacy name#0000 (id) discriminator format, which no current Discord username has.

npx jest passes locally (39/39).

[Copilot]

Pull request overview

Adds JustDiscord (justdiscord.org) to the bot-list dataset so BotBlock can recognize it as a supported directory/listing site with its API endpoints and capabilities.

Changes:

• Introduces a new list definition for JustDiscord including API docs, stats POST endpoint, and public listings endpoint.
• Declares supported feature flags and metadata (language(s), Discord invite, display/defunct status).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[umutxyp]

Follow-up: `view_bot` is now set to `https://justdiscord.org/bots/:id\`.

It was null when this was opened because listing pages resolve by an owner-chosen slug and `/bots/<application_id>` answered 404. JustDiscord now resolves the id form — an id-shaped address that matches no slug is looked up by application id and 308s to the canonical slug page, with the subpath and language prefix carried over. Live now:

```
/bots/774043716797071371 -> 308 -> /bots/beatra (200)
/bots/774043716797071371/commands -> 308 -> /bots/beatra/commands
/tr/bots/774043716797071371 -> 308 -> /tr/bots/beatra
```

The slug stays canonical — the id address is a permanent alias, not a second page — so nothing is indexed twice. The same is in place for server listings by guild id.

`api_get` stays null: the per-bot GET is scoped to the listing's own token and cannot answer for an arbitrary bot id.

[umutxyp]

Correction to my own earlier comment: I have set api_all back to null.

I filed it as /api/v1/listings?kind=bot describing it as an all-bots endpoint. It is not one — it has no pagination of any kind (no offset, no cursor, no page parameter), so it answers with the top of a sort and stops, capped at 50 rows per request. Anything walking it expecting the full catalogue would get the first page and believe it had everything, which is a worse failure than the field simply being absent.

view_bot is unaffected and still correct — /bots/<application_id> 308s to the canonical slug page, verified live.

Current state of the entry: api_post (+ api_field / api_shard_count / api_shards) and view_bot set; api_get, api_all, bot_widget, content, owners null.

[MattIPv4]

This should be a single language, the primary language for the site

[umutxyp]

Done — set to English.

[MattIPv4]

This should be a list of the Discord account of the folks that own/operate the bot list

[umutxyp]

Done — set to umutxyp#0000 (518341959765458985). I had left it null because no current Discord username carries a discriminator; I see now that #0000 is the established convention here for those.