NeuronLens
Browse the documentation
API reference

Authentication

Base URL, API keys, headers and request format.


https://api.neuronlens.com/v1

API keys

Create keys at neuronlens.com → Profile → API keys. A key looks like nl_ followed by 64 characters, is shown once, and is stored only as a hash. Delete a key on the same page; it stops working within a minute.

Send it as a bearer token, or in X-API-Key. Both work everywhere:

curl https://api.neuronlens.com/v1/me -H "Authorization: Bearer nl_..."
curl https://api.neuronlens.com/v1/me -H "X-API-Key: nl_..."

The Agent Lens integrations read the key from NEURONLENS_API_KEY or AGENTLENS_API_KEY.

Keys belong to your account: every key you create shares the account's daily allowance.

Keep keys out of source code and browsers. Use an environment variable (NEURONLENS_API_KEY) or a secret store, and call the API from your server.

Requests and responses

  • POST bodies are JSON: send Content-Type: application/json.
  • Responses are JSON. Errors have one shape: see Errors.
  • Every response carries a request_id; quote it when you contact us.
  • Runs answer with X-Quota-Limit and X-Quota-Remaining.

Endpoints

MethodPathCounts as a run
GET/v1/meno
GET/v1/healthno
POST/v1/scoreyes, one per answer or step
POST/v1/tracesyes, one per new tool call
GET/v1/probesno
GET/v1/decisions/{id}no
POST/v1/labelsno
GET/v1/requests, /v1/runsno
POST/v1/integrity/scansyes
GET/v1/integrity/scans/{id}, /models, /sources, /whoami …no
POST/v1/integrity/scan (one call)yes, except stored results and Unknown
GET/v1/integrity/familiesno