# Neuro Sandbox Context

## Purpose

Neuro provides trusted infrastructure for identity, agreements, digital assets, wallets, payments and verifiable events. A Neuron is the server node your backend integrates with. FIRSTBLOCK-ATHON participants receive sandbox access at the event; it is not a production environment.

## Rules for AI coding agents

- Never invent Neuro API endpoints, authentication flows, request fields, or response semantics.
- Inspect the current [Neuro documentation](https://docs.neuro-tech.io/) and OpenAPI reference before implementing an integration.
- Keep private API keys and secrets server-side. Never put them in browser bundles, logs, commits, screenshots, or `.env.example`.
- The Sandbox page may display explicitly designated public participant credentials from `SANDBOX1_PUBLIC_PARTICIPANT_API_KEY` / `SANDBOX1_PUBLIC_PARTICIPANT_API_SECRET` and the Sandbox 2 equivalents. These are intentionally shared with participants through the runtime API; never fall back to the generator's private Agent API or manager credentials. Keep the public values out of committed files and build artifacts too.
- Use sandbox credentials and sandbox value only. Test transactions have no real-world monetary value.
- Prefer the simplest documented Neuro capability that meets the product need.
- Explain assumptions and link to the relevant documentation whenever a requested capability is not documented.
- Do not circumvent security controls or use production infrastructure unless explicitly configured.

## Development workflow

1. Read the [Neuron quickstart](https://docs.neuro-tech.io/neuron-api/quickstart) and authentication documentation.
2. Configure secrets in the server environment, never the client.
3. Validate connectivity using the documented API flow.
4. Build one verified workflow at a time and inspect the resulting records in the Sandbox Explorer.
5. Keep a clear separation between application UI, backend integration, and secrets.

## Sandbox account and identity behavior

The page's account generator handles enablement and identity approval. When
creating accounts directly through the Agent API, enable the new account on the
same Sandbox before logging in:

```http
POST /hackathon-contract-approver/account/enable
Content-Type: application/json

{ "account": "your-account-username" }
```

This Sandbox endpoint requires no login or bearer token. The `account` field is
the account username. Confirm `enabled: true` in the response; repeated calls for
an already enabled account are safe.

The Hackathon service automatically approves newly created test identities
without manual identity review. Approval runs asynchronously: retrieve the
identity and wait for its state to become `Approved` before depending on approval.
This does not verify a real person or organisation; production approval differs.

These are Sandbox-specific extensions. Inspect the selected server's installed
contract for its current endpoints and authentication requirements:

- [Sandbox 1 service OpenAPI](https://sandbox1.neuro-tech.io/hackathon-contract-approver/openapi.json)
- [Sandbox 2 service OpenAPI](https://sandbox2.neuro-tech.io/hackathon-contract-approver/openapi.json)

## Useful documentation

- [How Neuro works](https://docs.neuro-tech.io/concepts/overview)
- [What is a Neuron?](https://docs.neuro-tech.io/overview/what-is-the-neuron)
- [Agent API quickstart](https://docs.neuro-tech.io/neuron-api/quickstart)
- [OpenAPI playground](https://docs.neuro-tech.io/neuron-api/api-reference/openapi/overview)
- [Documentation index for AI tools](https://docs.neuro-tech.io/llms.txt)