Skip to main content
This page does one job: authenticate a request and confirm that Adapt-1 returns a structured Core result. The example uses the State gateway for a first call. It does not require a Domain, generated language, a labeled dataset, demonstrations, solved trajectories, or learner tuning.

Base URL and authentication

Use the canonical versioned API:
Send the Unit API Key as a bearer token:
Keep the key on the server side. The hosted service resolves the effective identity from the bearer token. A body session_id is retained for request compatibility and cannot access another API key’s state.

Make one call

Replace YOUR_SECRET_TOKEN and run:

Read the result

Read these response fields: Application code can validate and use the JSON result directly. Generated language is optional.

Continue to the adaptive loop

This call verifies authentication and the response contract. It does not yet test retained state or feedback-driven adaptation.
Use continuity across calls to test retained evidence and correction. For a Domain, learn from an outcome, then verify adaptation by checking both the intended scoped learned signal and the later application behavior.

Build with an AI agent

Give a coding agent an exact implementation brief, contract sources, and verification checklist.

Choose the next workflow

Decide whether the application needs a stateless route, the State gateway, or a Domain.