Account and sign-in
Create a Batchrouter account, sign in on the dashboard, verify your email, and see what each workspace role can do.
A Batchrouter account is an email and a password. The same account is how you use the dashboard, manage API keys, buy credits, and — if you sell inference — open the provider portal. Programmatic calls use an API key from that account. See Authentication.
Create an account
Open dash.batchrouter.com/signup. You need:
- an email address
- a password of at least 10 characters
- acceptance of the Terms, Privacy Policy, and Refund Policy, which the signup page asks for
Batchrouter emails you a verification link. Open it. Until that address is verified, the account is read-only: GET requests work, and every write returns 403 with the error code email_verification_required. That includes submitting a batch, changing billing, inviting someone, and creating an API key. The error tells you where to ask for a fresh link (POST /v1/auth/verify-email/resend).
Sign in later at dash.batchrouter.com/login. Reset a password at dash.batchrouter.com/forgot-password. The dashboard may also show a bot check on those forms.
There is no social or SSO button on the customer dashboard. Dev, test, and production are separate accounts: a production login does not sign you into dev.dash.batchrouter.com.
What you can do after you sign in
| Page | What it is for |
|---|---|
| dash.batchrouter.com | Batches and the rest of the customer console |
| Settings | Account name, members, invitations, and API keys |
| Billing | Buy credits, auto top-up, and spend limits |
| Provider portal | Only if this account also supplies inference |
Buying credits, saving spend limits, and accepting a provider agreement require this signed-in session. An API key alone cannot do those. Spend-limit writes are described on Spending controls.
Workspace roles
Everyone in an account has one role. The owner manages roles and invitations on the Settings page. The dashboard does not offer owner on an invitation. Ownership moves by a separate transfer.
| Role | What that person can do |
|---|---|
owner | Everything an admin can, plus invite and remove members, transfer ownership, close the account, and rotate stored delivery credentials |
admin | Submit work, manage billing and API keys, and change workspace settings. Cannot invite members or transfer ownership |
member | Submit and manage batches, and read billing. Cannot change billing, members, or API keys |
billing | Read and change billing. Cannot submit batches |
read_only | Look at batches, quotes, results, and members. Cannot spend credits or change anything |
An API key carries one of these same roles. The key form on Settings offers Read only and Read and write (read_only and member). The other roles are for people, and for keys created through the API by an owner or admin. Details are on Authentication.
Providers use the same account
Register a provider at dash.batchrouter.com/providers/apply. The portal is a second door on this account. Provider how-to guides on docs.batchrouter.com are public; you do not need provider access to read them. Access to a provider has its own role (owner, admin, billing, or viewer), separate from the workspace role. The owner shares those roles from the portal. Both roles have to allow a change before a capacity write succeeds. See Roles and sharing and Capacity and heartbeats.
Staff
Batchrouter staff use a separate console. It is not part of this site, and a customer login does not open it.