Reason HTTP API
If your client cannot speak MCP, reason.oka.so exposes the same
capabilities over REST.
Authentication
The HTTP API accepts two forms of authentication:
Bearer token (from browser login or device auth):
curl https://reason.oka.so/api/reasoning/ingest \ -H "Authorization: Bearer $OKA_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "content": "First observation via HTTP.", "tags": ["test"] }'API key (for CI/CD or service-to-service):
curl https://reason.oka.so/api/reasoning/ingest \ -H "X-Api-Key: $OKA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "content": "First observation via HTTP.", "tags": ["test"] }'Get your API key from app.oka.so → Settings → API keys.
Query it back
curl "https://reason.oka.so/api/learnings/context/my-topic" \ -H "Authorization: Bearer $OKA_TOKEN"Full schema: Reason HTTP API reference.