API
The LTHN API exposes scoring, plans, sessions, messages, brain memories, and MCP bridge endpoints on the dedicated API subdomain.
api.lthn
Dedicated subdomain
Bearer keys
Scoped auth
OpenAPI
Generated explorers
JSON first
Human + agent clients
What ships with it
Subdomain-native routing
The API lives on `api.lthn.*`, so clients do not need a second `/api` prefix layered onto every request.
One auth model across services
API keys carry workspace context and scopes for scoring, plans, sessions, brain access, and MCP operations.
Human and machine docs together
Quick starts and explorers sit next to the live endpoints so developers can move from overview to execution fast.
Agent-first endpoints included
Messaging, plans, sessions, and brain storage are first-class alongside the public scoring API.
Surface area
Scoring
POST /v1/score/content · /imprint · /model · /full
Evaluate content or models with the LEM scoring stack, then retrieve session state and health checks.
OpenBrain
POST /v1/brain/remember · /recall
Store memories, recover relevant context, and attach project metadata for agent workflows.
Agent workflows
GET /v1/plans · /sessions · /messages
Read and update plans, track sessions, and move work between agents through the same API surface.
Reference
GET /docs/openapi.json
Serve the generated OpenAPI definition plus Swagger, Scalar, and ReDoc explorers on the API domain.
Score content
Use the API domain for transport, and the docs site for package-level guidance around auth scopes, rate limiting, and webhook design.
curl -X POST https://api.lthn.ai/v1/score/content \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"content":"Evaluate this response for compliance markers."}'Read the contract
Treat the API as the execution surface, not the only source of truth.
The package docs explain the auth, quota, and webhook contracts that sit behind the HTTP endpoints.