Accounts, teams and API keys

An account holds your balance, API keys, tasks and webhook settings. People reach it through the dashboard, as its members.

Accounts and sign-in

There are no passwords. Enter your email on the sign-in page and we send you a link. The link works once and expires after 15 minutes; signing in also spends any older links sent to the same mailbox. If you open it on a different device from the one that asked for it, the dashboard asks you to confirm the address first. When the sign-in page shows Continue with Google, you can also sign in with a Google account whose email Google has verified. A session lasts 30 days.

Addresses that reach the same mailbox, such as a +tag variant or a Gmail address with dots, sign in as the same user. Disposable email addresses are refused.

Your first sign-in creates your user and an account of your own with 100 free requests, with you as its owner, named after your address. You join other accounts by invitation. If you belong to more than one, switch between them with the account picker at the top of the dashboard.

Every account has unlimited seats.

Members and roles

Each member of an account has one role. An owner runs the account: billing, the team and every API key. A developer runs the integration: their own API keys and MCP connections, the Playground and webhooks. A viewer sees the account and changes nothing.

Owners change anyone's role with the role picker on their row of the Team page. This is also how you hand an account on: make the other person an owner, then leave or pick another role for yourself. An account always keeps at least one owner, so a change that would leave it with none is refused.

Owners remove any member, other owners included, with Remove. Any member can leave with Leave on their own row. When someone leaves or is removed, the API keys they created are revoked and the invites they sent that are still pending are deleted. An owner given another role also loses their pending invites, and anyone made a viewer loses the API keys and MCP connections they created.

Invites

Owners invite people on the Team page with an email address and a role, Owner, Developer or Viewer. We email the invite link, with what the role lets them do. An invite expires after 7 days. Pending invites are listed with their role and expiry date, and owners can cancel one with Revoke: its link stops working and its seat is freed.

• Inviting an address that already has a pending invite replaces it, and the earlier link stops working.
• Inviting someone who is already a member is refused.
• A pending invite holds a seat until it is accepted, revoked or expires.
• An account can send up to 20 invites an hour.

To accept, open the link and sign in with the invited address, or another address of the same mailbox. If you are signed in with a different address, the dashboard shows which address the invite was for, partly masked, and offers Sign out and continue. A link that was used, revoked or has expired cannot be accepted, and neither can an invite whose sender is no longer an owner. Ask an owner to send a new one.

API keys

Owners and developers create keys on the API keys page: type a name of 1 to 100 characters, such as production, and click Create key. The full key is shown once, right after it is created, so copy it then. After that the page shows the key's name, its first characters, who created it, when and when it was last used. Owners revoke any key, developers the keys they created. Viewers see the list but cannot create or revoke keys.

One key works for every endpoint; keys have no scopes. Every key spends the account's balance. An account can have up to 50 active keys; revoke one to create another. See Authentication for how to send a key.

Revoke stops a key within a minute. Revoked keys stay listed under Show revoked.

A key is tied to the person who created it. When that person leaves the account, is removed, is made a viewer, or deletes their user, every key they created is revoked. Before then, move your services to a key created by someone who is staying.

To rotate a key without downtime:

1. Create a new key.
2. Deploy it everywhere the old key is used. Both keys work in the meantime.
3. Wait until the old key's Last used time stops changing. It can lag by up to a minute.
4. Revoke the old key.

Audit log

Owners read the account's history on the Audit log page and can filter it by action. Each event shows when it happened, who acted (a user, our operators, Stripe or the system), the action, its target, the client IP where one was recorded, and details. Events are kept for 400 days. The log records:

• sign-ins, Sign out everywhere and deleted users;
• API keys created and revoked;
• invites sent, accepted and revoked, members removed or leaving, and role changes;
• webhook secret rotations, test deliveries and redeliveries;
• bonus claims and their review;
• completed top-ups, refunds and disputes taken back, and auto top-up changes;
• changes our operators make to the account's tier, limits and balance.

Email notifications

Owners get an email when the balance falls under 10% of the last top-up; owners and developers get one at most once a week when webhook deliveries fail for good. Each person can turn these off under Email notifications on the Settings page. Outage emails, for owners and developers, are off until you turn them on: one when an engine you used in the last week almost stops answering, one when it is back. Sign-in links, invites and failed auto top-ups always send.

Each of these emails ends with an Unsubscribe link, and your inbox may show its own Unsubscribe button. Either one turns off all three kinds at once, without signing in. Turn any back on in Settings.

Your data and sessions

Download my data on the Settings page (GET /me/export) gives you personal-data.json. It holds:

• your user: id, email address, your email settings and when it was created;
• the accounts you belong to, with your role in each;
• your sessions, with when each started and expires;
• the notification emails sent to you;
• for each account you own: its tier, balance and billing details, API keys (name, first characters and dates), members, invites, bonus claims, referral commissions and daily usage by engine.

It never contains API keys, session tokens, invite links or the webhook signing secret. You can download it 5 times an hour.

Sign out everywhere on the same page ends every session of your user on every device, this one included. API keys keep working.

Deleting your user or an account

Delete account on the Settings page deletes your user. Type your email address to confirm. This cannot be undone.

• You leave every account you belong to.
• An account where you are the only member is deleted with you. Its queued tasks are dropped, its API keys stop working, and its auto top-up is cancelled at once. Its remaining balance is forfeited, without a refund.
• An account with other members stays. If you are its only owner, make another member an owner first; until then the deletion is refused.
• In accounts that stay, the keys you created are revoked and the invites you sent that are still pending are deleted.
• Your address is removed from the audit logs and notification records of your accounts.
• 30 days after an account is deleted, its name, invite addresses and bonus claim links are erased and its keys and audit events are deleted. Records of amounts charged and billed are kept.
• If you sign up again with the same mailbox, the new account starts without free requests.

There is no separate button to delete an account. An account is deleted when its last member deletes their user. To close an account that has other members, or to close one without deleting your user, an owner can email support@answerline.dev.