Add Neuro to your application - Neuro Developer Documentation

Use a trusted backend to keep Neuro credentials out of browser and mobile code. Start with the tested backend sample, then add the capability your application needs.

Architecture

User
  ↓
Web or mobile client
  ↓
Application backend
  ↓
Supported SDK or Agent API
  ↓
Neuron

The application backend protects Agent API secrets and coordinates persistence. A browser can participate in the dedicated web-form onboarding and session flow; it must not receive a trusted account-creation secret.

Prerequisites

A confirmed development environment.
A supported Node.js runtime for the current Agent API Quickstart.
The host and credentials required by that Quickstart.
A storage mechanism for application state and Neuro identifiers.

Build sequence

Run the Agent API Quickstart.
Run the trusted-backend sample from a clean repository clone.
Store environment configuration outside the source repository.
Confirm that only allowlisted account fields reach the browser.
Add an identity, agreement, asset, payment, messaging, or AI-tool capability that your Neuron supports.
Store the identifiers and state named by that capability’s guide.
Test the success, rejected-session, invalid-configuration, and unavailable-Neuron paths supported by the environment.

Expected result

The client shows account information obtained through the application backend. No Agent API secret, password, JWT, or private key appears in the browser source, URL, analytics, or logs.

State created

Value	Persist?	Notes
Neuron host	Yes	Environment-specific configuration
Application user to Neuro account mapping	Yes	Keep the mapping scoped to the application
JWT	Usually temporary	Store only in a protected server-side session where possible
Legal Identity status and identifier	After identity onboarding	Follow the identity guide’s storage rules

Next step

Choose a capability from What can I build?. Each capability page tells you what you can implement now and what you must confirm with the Neuron operator.

​Architecture

​Prerequisites

​Build sequence

​Expected result

​State created

​Next step