POST /v1/signup creates a workspace, a login, an empty wallet, and your first API key in one call. It is the only endpoint on the Sandbox API that takes no Authorization header, because it is where the key comes from.
Use it when the caller is a program. If you are a person, sign up in the dashboard instead: you get the same workspace and the same key, on a screen.
Sign up and start running
Request
string
required
Where to reach the workspace’s owner, and the address its
claim_url is scoped to. It is not a login, and it is not verified. One API-created workspace per address: a second signup on the same address returns 409 email_in_use and creates nothing.string
optional
The workspace name, up to 100 characters. Defaults to a name derived from the email address.
number
default:"5"
optional
What
top_up_url is worth, $5 to $10,000. It only sizes the returned payment link; nothing is charged by this call.Response
string
The workspace the key belongs to. Everything the key creates is owned by it.
string
Your
sk_live_ key, shown once and never again. The account has no other key until you mint one.string
The address the account was created on, lowercased.
number
Always
0. Fund the wallet before creating an instance.string
A hosted Stripe Checkout link for
top_up_usd. null if the link could not be created, in which case POST /v1/billing/top-up mints another one.number
The amount
top_up_url charges.An admin invitation link for
email, so a human can take over the workspace in the dashboard. Give it to the person who owns that address. See The email, and who owns the account.The email, and who owns the account
The address is a contact address and a claim ticket, not a login. Nothing is emailed, and the workspace is owned by an account that has no email address and no password, so nobody can sign in as it. That matters because this endpoint is unauthenticated: if it registered a login on the address you send, anyone could sign upsomeone@theircompany.com and keep a working key in the workspace that person later landed in.
claim_url is how a human gets in. It is an ordinary admin invitation scoped to the address you signed up with, so give it to the person who owns that address. They sign in (or sign up) with it and accept, which makes them a full admin: from there they mint and revoke keys, see the ledger, fund the wallet, and manage the team in the dashboard. The link does not expire and is used once.
That is the intended path to a second key. There is no endpoint that mints keys, on purpose: a key that can mint keys is no protection, because a stolen one just mints another.
Signing up does not touch any Agent37 account that address may already have, and an address that already has an API-created workspace returns 409 email_in_use rather than a second one.
An account created by POST /v1/signup does not receive the one-time $5 starter credit. That credit exists so a person can try the product before paying; fund the wallet to start.
Fund it, then create
A new workspace is on the free tier: balance $0, and one instance once it is funded. Creating an instance with an empty wallet returns402 insufficient_balance, which is the signal to pay. The first top-up of any amount raises the ceiling to 10 instances. See Billing for the tiers, the rates, and both ways to pay.