Prepare a development environment - Neuro Developer Documentation

Obtain an environment

For the current operator-mediated flow, obtain these values from the Neuron operator:

Neuron host
Account username and password, or onboarding instructions
Agent API key and secret when trusted account creation is required
Required privileges
Available identity, contract, token, wallet, and MCP services

Never commit passwords, API secrets, JWTs, private keys, or wallet credentials.

Confirm how the environment behaves

Before building, ask the operator to confirm:

Question	Why it matters
Is this development, staging, or production?	Determines whether state is disposable or operational
Are identities and signatures legally meaningful?	Prevents test data from being mistaken for production evidence
Is eDaler test value or real value?	Prevents unintended financial activity
Can this Neuron federate with production?	Prevents development actors from crossing an environment boundary
Which Trust and Identity Providers are enabled?	Determines whether identity workflows can complete
Which templates and fixtures are pre-approved?	Determines whether contract and token tutorials can run
How is state reset?	Makes tests repeatable

These semantics are deployment decisions. Do not infer them from a hostname or from the fact that a request succeeds.

Ask for repeatable test data

A useful development environment should let your application exercise these states:

Identity: approved, pending, rejected
Contract: approved, pending, rejected
Wallet: funded, empty
Neuro-Feature: active, transferred, revoked

If the operator cannot provide repeatable test data, record which identities, templates, wallets, and state changes are available before you begin.

​Obtain an environment

​Confirm how the environment behaves

​Ask for repeatable test data

​Make your first request

Obtain an environment

Confirm how the environment behaves

Ask for repeatable test data

Make your first request