Neumera

API demos

Generated from docs/registry/demo_registry.json to keep examples synchronized with the current interface.

runtime / continuity demos

Runtime continuity status

Check runtime identity and continuity telemetry through the public API.

Learn: How to authenticate and inspect runtime health signals.

System creation focus: Creates an operator-visible runtime baseline snapshot before mutating any world state.

  • GET /v1/runtime/status

Suggested sequence:

  1. Call GET /v1/runtime/status to fetch continuity/runtime state.
  2. Record the request ID for audit correlation.
  3. Store returned payload snapshots for longitudinal monitoring.

world-building demos

World loop basics

Create and update world tasks through runtime-facing world APIs.

Learn: How to model external world objects and task state transitions.

System creation focus: Creates a new world task, evolves it to in-progress state, and verifies object projection.

  • POST /v1/worlds/tasks
  • PATCH /v1/worlds/tasks/{task_id}
  • GET /v1/worlds/objects

Suggested sequence:

  1. Create a world task with POST /v1/worlds/tasks.
  2. Apply updates with PATCH /v1/worlds/tasks/{task_id}.
  3. Inspect world object projections with GET /v1/worlds/objects.

multi-entity demos

Multi-entity social assay

Run a social assay using prebuilt social world manifests.

Learn: How to execute assays and retrieve generated reports.

System creation focus: Creates assay execution state and records result pointers for downstream governance workflows.

  • POST /v1/assays/social/run
  • GET /v1/artifacts/{artifact_path}

Suggested sequence:

  1. Run an assay with POST /v1/assays/social/run.
  2. Read artifact/report output with GET /v1/artifacts/{artifact_path}.
  3. Index artifact paths into your lab workflow metadata.

social/cultural assay demos

Cultural assay artifact retrieval

Retrieve machine-readable assay artifacts and reports for analysis pipelines.

Learn: How to integrate Neumera artifacts into downstream governance tooling.

System creation focus: Builds an evidence handoff bundle by collecting generated JSON and Markdown report outputs.

  • GET /v1/artifacts/{artifact_path}

Suggested sequence:

  1. Locate assay output artifact paths from run responses.
  2. Fetch each artifact with GET /v1/artifacts/{artifact_path}.
  3. Validate and archive JSON/Markdown outputs in governance systems.

continuous-ops demos

Continuous ops checkpoint

Trigger runtime lifecycle and checkpoint orchestration through runtime ops APIs.

Learn: How to run controlled long-horizon operations and recover state.

System creation focus: Creates a recoverable checkpoint boundary used by release gates and incident workflows.

  • POST /v1/continuous-ops/checkpoint
  • GET /v1/runtime/status

Suggested sequence:

  1. Call POST /v1/continuous-ops/checkpoint with an artifact path.
  2. Verify runtime status via GET /v1/runtime/status.
  3. Repeat checkpointing on your operational cadence.

membrane demos

Membrane render pass

Render runtime/world state into natural language for operator-facing reporting.

Learn: How to use membrane translation to bridge machine-readable and human-readable output.

System creation focus: Creates operator-readable summaries from runtime and assay payloads for incident channels.

  • POST /v1/membrane/render/runtime
  • POST /v1/membrane/render/assay

Suggested sequence:

  1. Render live runtime context via POST /v1/membrane/render/runtime.
  2. Render assay payloads via POST /v1/membrane/render/assay.
  3. Attach membrane summaries to operational reports.

governed outbound demos

Bounded external actions

Propose, dry-run, approve, execute, and inspect bounded outbound action contracts.

Learn: How explicit approval-gated outbound actions reconcile into ordinary runtime/task state.

System creation focus: Creates a durable action ledger entry and records approval/execution evidence under a bounded adapter.

  • POST /v1/external-actions/propose
  • POST /v1/external-actions/dry-run
  • POST /v1/external-actions/{action_id}/approve
  • POST /v1/external-actions/{action_id}/execute
  • GET /v1/external-actions/{action_id}

Suggested sequence:

  1. Propose a typed action with POST /v1/external-actions/propose.
  2. Validate and inspect non-mutating intent with POST /v1/external-actions/dry-run.
  3. Approve and execute the action with explicit actor attribution.
  4. Read ledger and reconciliation state through GET /v1/external-actions/{action_id} and /v1/external-actions/history.