Skip to main content
Use the Agent API for your Neuro application. A standard HTTP client is enough; the examples do not require a Neuro SDK or an XMPP connection.

​
Backend services

Your backend signs a login request, receives a JWT, and calls the required HTTP operations. Keep passwords, signing credentials, and JWTs in protected server-side storage. Use the first-call example to verify access.

​
Browser and mobile applications

Route privileged operations through your application backend:
The backend exposes only the data and actions needed by the UI. Do not place an account-creation secret, account password, signing-key password, or privileged JWT in browser code or a distributable app. Follow Add Neuro to your application to connect your interface and track API results. For supported user-interactive signup, follow browser signup, including its session handoff.

​
Contracts and tokens

Author contract XML locally and validate it with the schema resources. Your application submits templates, creates instances, and retrieves results through the Agent API. LegalLab can help edit XML; it is optional for application integration. A state machine or embedded Neuron Script defines behavior inside the token creation contract. It does not change how your application connects.

​
Messages and asynchronous results

Paths such as /Agent/Xmpp/SendXmlMessage are HTTP endpoints. Use the exact message format in contract proposal delivery. Your application does not need to manage the underlying transport connection. Persist returned identifiers and observe completion. Successful submission can precede identity review, template approval, signatures, or token creation.