InfoLang API
API by InfoLang · rest
The InfoLang gateway. /v2 is the console + runtime API; the raw Kairos runtime surface stays proxied at /v1 and /mcp, and Canon — the coordination layer — at /coord/v1 where the deployment serves it (capabilities.canon on GET /v2/me). Three credential lanes Every /v2 request carries a bearer token, and its prefix decides the lane: | Lane | Credential | For | |---|---|---| | session (sessionAuth) | Supabase session JWT | the website / console | | oauth (oauthTokenAuth) | il_oauth_… | a HUMAN who connected an MCP client (Claude, an IDE) | | key (apiKeyAuth) | il_live_… / il_test_… | MACHINES — SDKs, servers, CI | The gateway verifies only the session lane, minting a separate Kairos runtime token for upstream calls; the two il_* credentials are classified and forwarded verbatim, and Kairos verifies them and enforces the credential↔workspace binding. Which lanes a route accepts The general rule: anything scoped to a workspace…
Endpoint: https://api.infolang.ai/
Verification: observed. Source: crawl.
Capabilities (133)
- Authorization server metadata (RFC 8414)
- Protected resource metadata (RFC 9728)
- Provider OAuth redirect target
- Record a claim about a subject
- Read what is currently believed about one or more subjects
- Acquire advisory mutual exclusion over a resource
- Drain the workspace's coordination event log
- Is Canon available on this deployment?
- Release a held advisory claim
- Liveness
- MCP event stream (streamable-HTTP transport)
- MCP JSON-RPC endpoint
- End an MCP session (streamable-HTTP transport)
- Authorization endpoint
- Complete consent (console only)
- Approve or deny a device (console only)
- Resolve a typed user code (console only)
- Device authorization request (RFC 8628 §3.1)
- Dynamic client registration (RFC 7591)
- Token endpoint (authorization code + device grant)
- Readiness
- Encode text to an embedding
- Batch operations
- List memories
- Forget a memory