AscensionBot

Guide d'automatisation

Comment s'authentifier, quelles portées existent, et des exemples détaillés pour les automatisations les plus courantes.

Claude Code, Cursor, Windsurf, or any automation tool can talk directly to your Discord server through the AscensionBot Developer API — create channels, wire up roles and permissions, build a ticket system, moderate. No bot code, no gateway connection, just an HTTPS call with a bearer token.

Get a key in under a minute

Every key is created and scoped from your own server dashboard — never shared, never generated for you.

  1. Open Developer API — In your dashboard: server → Admin → Developer API.
  2. Create a key, pick scopes — Name it after the agent using it (e.g. "Cursor — ticket setup") and grant only the scopes that task needs.
  3. Copy it once — The raw key is shown only at creation. Paste it into the prompt below and hand it to your agent.

Three tiers, one axis: blast radius

The tier you pick when creating a key decides what it's even capable of — independent of which scopes you grant it.

Staging — Try things safely

  • Can't hold delete/kick/ban scopes — ever, even if you try to grant them
  • Rate limit capped to 20% of your server's normal limit
  • Good default for a first agent connection

Prod — Full control, one server

  • Any scope, full rate limit
  • Locked to the server it was created on
  • What most agents should run on day-to-day

Dev — Cross-server tooling

  • Only the bot application owner can create or edit one
  • Can target a different server per-request via target_guild_id
  • For your own multi-server automation, not for a typical integration

API scopes

Ground rules before you connect an agent