Discord infrastructure

One quiet edge for every Panludia bot.

Panludia hosts multiple isolated Discord applications behind one hardened HTTP interaction gateway.

Bot-specific interaction routes

Every application has its own slug and Discord public key. Requests are accepted only after their Ed25519 signature has been verified against the matching application.

https://bot.panludia.com/<bot-slug>/interactions

Discord event webhooks

Discord can report application authorization and deauthorization events through a separate signed route. Event requests are authenticated and acknowledged independently from commands.

https://bot.panludia.com/<bot-slug>/events

Linked roles

Applications that enable linked roles use a dedicated OAuth2 route. Access tokens are used for the one requested update and are not persisted by this gateway.

https://bot.panludia.com/<bot-slug>/linked-role

Private notification webhooks

Panludia services can send a bounded message to a bot-specific Discord webhook. Every request must carry a short-lived HMAC signature and a replayed request is rejected.

POST https://bot.panludia.com/<bot-slug>/webhook

Shared legal URLs

The public legal documents apply to every official Panludia Discord application hosted here.

https://bot.panludia.com/terms-of-servicehttps://bot.panludia.com/privacy-policy