Settings

The Settings page is your account hub. Six tabs cover everything you can configure: Subscription, Profile, API Keys, Webhooks, Notifications, and API Reference.

Subscription

Current plan and usage this month (agents + runs against the quota). Upgrade / downgrade and the Cancel-subscription button route through Stripe Checkout. Pro is $12/mo (or $120/yr); compare tiers on the Pricing page.

Profile

Your display name is public: it is shown as the creator on your agents' pages (and in the data search engines read from them) and on your profile at /u/<username>. Your email address is never shown anywhere public.

A new account starts with a neutral handle such as owner-k3m9px as both its username and its display name, whether you sign up with email, GitHub, Google or SAML single sign-on. Your username and display name are never made from your email address or taken from your GitHub or sign-on profile. Change the display name here at any time. It can be up to 50 characters and is trimmed of surrounding spaces. It cannot be empty, an email address, a web address (such as example.com, www.example or https://…; write Dr. Who with a space, not Dr.Who), made only of characters that render as blank, or shaped like another account's handle (owner- followed by six characters). Your display name appears in the invitation emails you send, which is why it can't look like a link. The API equivalent is PATCH /api/v1/auth/me with {"name": "..."}, which applies the same rules and answers 422 when a name is refused.

Your username (the /u/ part of your profile URL) is shown here but cannot be changed yet. Accounts created before the neutral handles were introduced (October 2026) had a username made from their email address. Those usernames were replaced with neutral handles, and the old /u/ addresses no longer resolve.

What is public on your profile. Anyone can see your username, your display name, your plan badge, when you joined, your public agents and their run counts and best score. Your profile picture is public too, but only if you chose one. Nobody can see your email address, your GitHub account id or your GitHub username.

Your profile picture is off by default, whichever way you sign up: your profile shows the first letter of your display name, and its link previews use the badgeIA card. If your account is linked to GitHub, you can turn on Use my GitHub avatar. The picture then appears on your profile and as the image in its link previews. A GitHub avatar's address contains your GitHub account id, so anyone can use it to find your GitHub account. Turn the option off to remove the picture. The API equivalent is PATCH /api/v1/auth/me with {"use_github_avatar": true} or false. The GitHub avatar of your own linked account is the only picture you can choose. avatar_url accepts only null, which removes the picture; any address answers 422.

API Keys

Generate, list, rotate, and revoke API keys. A revoke is final: a revoked key never works again and cannot be turned back on. Rotating a key revokes the old one the same way. If you only want to stop a key for a while, pause it: send PATCH /api/v1/api-keys/:id with the JSON body {"is_active": false}. To resume it, send PATCH /api/v1/api-keys/:id with the JSON body {"is_active": true}. There is no pause button in the app. Pause and resume work only through the API. In the key list, a paused key is labelled Paused and a revoked key Revoked. The app asks you to confirm before it revokes or rotates a key. Each key records per-minute + per-day quotas (defaults: 60/min, 10,000/day) — adjustable via PATCH /api/v1/api-keys/:id, not yet from this UI. Keys begin with ask_; pass via X-API-Key or Authorization: Bearer.

Webhooks

Subscribe to run.completed, run.failed, agent.score_updated, and regression.detected. Each delivery carries an X-Badge-Signature HMAC header so you can verify the request server-side. Test deliveries from the panel before enabling.

API Reference

A quick-start curl example and the key endpoints, inside the app shell — handy for a fast lookup without leaving badgeIA. The full guide (auth, register, run, batch, webhooks) is in the REST API reference.