Skip to main content
Make a direct Adapt-1 request and use the JSON result in your application. The cURL, Python, and JavaScript examples send the same request.

Set your API key

Use an Adapt-1 Unit API key, stored in your local environment or server-side secret store:
Environment
The examples use https://rei-neuroadapt-api.reilabs.org/api/v1. Keep the key out of browser code, source control, and logs.

Make your first call

This request asks the State gateway for available evidence. It is read-only: update_memory_state is explicitly false.
Python uses the standard library. Run JavaScript as an .mjs file with Node.js 20 or later. Both examples run on the server.

Read the result

An empty evidence result is valid when nothing relevant has been stored. The following illustrative minimal response shows the empty-evidence shape. The service can return additional fields.
Empty-evidence illustration
Application code can consume these fields directly.
The hosted service resolves the effective identity from the bearer token. The body field satisfies this request’s compatibility contract; changing it does not select another tenant or create isolated state. Use a separate credential for a separate identity, or a separate domain_id for a task-scoped Domain.

Continue with your application

The first call checks authentication and the response boundary. Continue with State to use accumulated evidence in later requests, or build a predictor in a Domain from completed observations.

Reason with project context

Store related project records, request context and reasoning, then inspect the result after a correction. This example uses the domainless State gateway.

Build your first learned result

Ingest observations into a Domain and compare predictions before and after learning with a complete Python example.

Choose a workflow

Start from the prediction, decision, evidence, or control result your application needs.

Build with an AI agent

Give your coding agent the request contract and an implementation checklist.

If the call fails

For exact request boundaries and schema coverage, see HTTP and request contracts.