What it reads
- System prompt, skills and tool descriptions as one release
- An Ed25519 signature, checked on every read, cached reads included
- Cached in memory and on disk; if Contexory cannot be reached you get the last verified release
The signed API and SDK
Fetch the approved release from your own code.
Your code asks for an agent and a label and gets the signed release: system prompt, skills and tool descriptions together. Node 18 or later; the SDK is ESM-only.
Install
npm install @contexory/sdkexport CONTEXORY_API_TOKEN="con_rt_your_key_here"curl -i -H "Authorization: Bearer $CONTEXORY_API_TOKEN" "https://sync.contexory.com/api/v1/agents/support-agent/resolve?label=production"Use a runtime key: organization-owned, read-only, and scoped to the agents you name. The last command checks it against an agent's production label.
Read the guide →Where things land
- Release cache
- ~/.cache/contexory/sdk, or the directory in CONTEXORY_CACHE_DIR. Created with 0700 permissions.
- Runtime key
- In your environment, as in the commands. Only its hash is stored by Contexory.
Not delivered here
- Anything outside the release: drafts, and changes made after the release a label points at.
- Eval cases and run history. The payload holds the system prompt, skills and tool descriptions only.
- Browsers and edge runtimes. The SDK is Node-only.
Runtime keys are created in a Contexory account.