Skip to main content
Use GET /openapi/v1/runtime-config when your integration starts, then refresh it on a configurable interval. The endpoint requires both config:read and policies:read.

​
Response

contentHash is a lowercase SHA-256 hex digest of the prompt content. Verify it before replacing a cached prompt.

​
Conditional refresh

The response includes an ETag based on revision. Save it and send it on the next refresh:
A 304 Not Modified response has no body. Keep using the current cache and update its last-checked time.

​
Cache behavior

Your implementation should:
  1. Load a previously validated cache from local storage.
  2. Request the current configuration during startup without blocking normal event delivery.
  3. Replace the cache atomically only after the complete response validates.
  4. Refresh on a configurable interval with jitter.
  5. Keep the last known good configuration when the API is unavailable.
  6. expose prompts by stable ID or name and return their versionId with the content.
Attach versionId as promptVersionId to relevant run events and issue records. This connects behavior to the exact Lynx-managed prompt version. Policies are designed for local evaluation before a tool call. Do not call the API for every tool execution.
Prompt content can contain confidential instructions. Protect the local cache with the same access controls as application configuration, and do not write prompt content or API keys to diagnostic logs.