Start

Neumera is a hosted architecture for systems that must remain coherent as consequences accumulate.

It provides long-lived sessions, persistent world state, governed action surfaces, and evidence-bearing outputs that can be inspected and replayed.

Softminds are persistent computational minds with continuity, memory, commitments, and world participation across time.

The systems people increasingly want to build already exceed the limits of stateless generation, shallow orchestration, and disposable tool loops.

They must persist.
They must remember in ways that change future behaviour.
They must coordinate across shared state.
They must act under governance.
They must produce outputs that can be inspected, replayed, and trusted.

Those are architectural requirements.

Use Neumera when the system you are building must remain coherent as consequences accumulate.

If the job is disposable generation, one-off interaction, or simple tool invocation with no need for continuity, accountability, shared state, or evidence, use something simpler.

Neumera is for systems that must keep living with what they have already done.

Sandbox access is immediate and bounded for first-build usage.

Request a sandbox key through the hosted API and use it with the X-API-Key header on authenticated routes.

curl -X POST https://api.neumera.io/v1/access/request \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example Builder",
    "email": "builder@example.com",
    "intended_use": "Prototype a persistent research workspace"
  }'

You do not need a dashboard or manual approval to begin sandbox integration work.

Sandbox access is immediate and bounded. It is designed for first builds, evaluation, and early integration work.

Full access unlocks broader route families, richer operational limits, and deeper capabilities. That path remains governed and available by request.

Studio lets you watch Neumera run live scenarios through the public API.

Start a walkthrough, follow the behavior as it unfolds, and inspect the underlying route history and payload evidence in the same place.

Use the canonical first sequence:

1. Obtain a sandbox key.
2. Create a session.
3. Step the session with real input.
4. Inspect runtime summary and world state before expanding scope.

Workflow guides map common build intents to concrete call sequences for sessions, world state, external events, governed actions, and evidence.

Use workflows to move from first request to stable application behaviour with explicit route ordering and common next calls.

A coding LLM can use the hosted API directly, including the sandbox access route.

You can ask your model to:

• request a sandbox key
• inspect the Start and API pages
• create a session
• step the session
• expand into world, event, action, or evidence flows as needed

For safety and clarity, decide whether the model should display the issued key back to you or use it immediately within the build flow.

You are building an application using the Neumera hosted API.

Read:
- https://www.neumera.io/start
- https://www.neumera.io/api

Use:
- Site URL: https://www.neumera.io
- Base URL: https://api.neumera.io
- Authentication: X-API-Key header
- Build mode: hosted API only

If no API key has been provided yet, first request a sandbox key from the public access route described in the Start guide.

Then:
1. Read the Start page and API reference carefully.
2. Inspect real request and response shapes before making assumptions.
3. Create a session.
4. Step the session with a real input.
5. Use world, event, action, or evidence routes only when needed by the application.
6. Do not invent endpoints.
7. Do not assume a local runtime.
8. Build against the hosted API only.

If payload shape is unclear, inspect the schema or make a small exploratory request first.
Return the issued sandbox key to the user if appropriate and clearly label it.

For best results, give the model a concrete goal and ask it to implement one working flow end to end before expanding scope.

These starter apps are the fastest way to move from a first key to a working integration.

They use the same public sandbox flow documented in Quickstart:

• request a key
• create a session
• step the session
• inspect runtime and world state

Sandbox access is intended for immediate first use. Full access is available for builders, researchers, and institutions whose systems require broader capabilities, richer route families, or higher operational limits.

Use this form when your project moves beyond first build and needs a deeper integration path.