Skip to main content
Use the web-form endpoint when an untrusted browser must create an account directly. Unlike the JSON Create account flow, the browser flow uses reCAPTCHA and redirects rather than exposing the account-creation API key to JavaScript.
Before launch, test the form fields, allowed redirect origins, cookie attributes, CORS behavior, reCAPTCHA settings, and session-token response on the target Neuron.

Prerequisites

The Neuron operator must:
  • configure Google reCAPTCHA;
  • create an API key whose owner is Agent API and whose account limit has not been reached;
  • configure email delivery and, if phone verification is required, SMS delivery;
  • serve the signup page over HTTPS.
Removing the API key or setting its limit to the current account count disables public account creation.

Submit the form

Render the reCAPTCHA widget and submit a normal HTML form to /Agent/Account/CreateWebForm:
The endpoint consumes form data, not JSON. The redirect target must be an application URL you trust; do not copy a redirect URL from arbitrary query input.

Recover the new session

After the Neuron redirects the browser, preserve its session cookie and exchange the creation session for account state:
The created account starts disabled. Ask the user for the code delivered to their email and call Verify email. If a phone number was supplied, complete phone verification too.
Keep the returned JWT in memory where possible. Never place it in a URL, page source, analytics event, or browser log.