Build a Discord bot in minutes.

Every bot starts as a conversation. Conjure runs Claude Sonnet 4.5 for fresh generation and routes follow-up edits to Haiku 4.5 when the change is small enough — you get fast, cheap iterations for tweaks and the big model when you need new features.

Long conversations get automatically summarised after 30 turns so you don't pay token costs for ancient back-and-forth, but the recent 10 messages stay verbatim so the AI never "forgets" what you're currently asking about.

The Monaco editor (same one VS Code uses) is right next to the chat. Edit anything by hand — the AI sees your changes on the next turn and adapts. Useful for tweaks that are faster to type than describe.

After deploy, use a private server to try slash commands. Invite the bot with the applications.commands scope. Global commands can take up to an hour to update on Discord's side after a redeploy.

Create an application in the Discord developer portal, grab the bot token, paste it into Conjure's connect modal. We encrypt it with libsodium sealed boxes before it touches the database. The decryption key never leaves the deploy environment. The token is write-only from your end — the UI shows "Connected" but never the value.

Deploys run on Fly.io Machines, one per bot. Each gets a persistent volume mounted at /app/data so your bot can keep state (sqlite, JSON files, level data) across redeploys. We scale to zero when idle with ~1s cold-start.

Logs stream live back into the editor — open the status pill in the bot header to follow along. Iterating on a live bot: edit code, click Deploy again. Old machine shuts down, new one comes up, volume survives.

Don't want managed hosting? Download a ZIP of your bot's code from any plan (including Free). Standard Node project — npm install → DISCORD_TOKEN=… node src/index.js → it runs anywhere Node 20+ does.

If you want the full Hobby experience without committing to a subscription, the trial is a one-off $1 charge that grants 24 hours of Hobby-tier access. No auto-renew — your card never gets touched again unless you explicitly upgrade. After it expires you drop back to Free.

The trial is single-use per account. If you cancel a paid subscription later, you can't restart the trial from scratch — upgrade directly to Hobby or higher.

One chat turn between you and Conjure = one update. Describing a brand-new bot, asking for a tweak, or pasting an error and asking for a fix all count identically. Background calls Conjure makes on your behalf (lint, classify, summarise) don't count against your allowance.

Each row in your workspace. Deleting a bot doesn't free a slot for the rest of the calendar month — this is anti-abuse, documented in the delete confirmation. Bot creation resets on the 1st.

A bot currently in deployedstatus (i.e. burning Fly Machine seconds). Drafts, stopped, and errored bots don't count. Free tier can't deploy at all — you can still build and edit bots on Free without spending Fly money.

https://useconjure.app/api/v1

Send a bearer token in the Authorization header. Tokens are shown once at creation — copy them immediately, we can't recover them after.

curl https://useconjure.app/api/v1/me \
  -H "Authorization: Bearer cnj_live_xxxxxxxxxxxxxxxxx"

Rate limits: 5 burst / 1 token per 3 seconds sustained, same as the dashboard. Quotas:API calls count against your normal monthly AI-update budget — there's no separate API allowance.

# 1. Create a bot
curl -X POST https://useconjure.app/api/v1/bots \
  -H "Authorization: Bearer $CONJURE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "Welcome bot", "description": "Greets new members"}'

# Returns: { "ok": true, "data": { "id": "abc-123", ... } }

# 2. Iterate (streaming SSE)
curl -N -X POST https://useconjure.app/api/v1/bots/abc-123/iterate \
  -H "Authorization: Bearer $CONJURE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"messages":[{"role":"user","content":"Add a /ping command"}]}'

# 3. Deploy
curl -X POST https://useconjure.app/api/v1/bots/abc-123/deploy \
  -H "Authorization: Bearer $CONJURE_TOKEN"

Every endpoint returns either:

{ "ok": true, "data": { ... } }
{ "ok": false, "error": { "code": "...", "message": "..." } }

Status codes follow standard conventions — 401 (missing/bad token), 403 (out of quota), 404 (no such bot), 429 (rate limited), 5xx (us). The error.message field is safe to surface directly to your users.