DOCS
PreviewContext API
One endpoint, one job: return the smallest high-signal slice of the record that answers a question. Agents consume slices of context, never raw files.
Three properties worth knowing
It resolves against the hierarchy first. The capability map is an index for progressive disclosure: a caller descends the tree and pulls one slice rather than retrieving over the whole corpus.
Curation state is the ranking rule. Confirmed outranks reviewed, which outranks derived, which outranks auto-placed. Retrieval inherits human judgment for free, and a caller can refuse anything below a floor it sets.
The budget is declared, and truncation is never silent. Every response states the budget it was given, what it used, whether it truncated, and what it dropped. Lowest signal goes first. A caller always knows whether it got the whole answer.
Evidence is available by reference rather than inline, so a slice stays compact while every claim in it remains checkable.
REQUEST
POST /v1/context/slice
{
"question": "Who approves a rebill above the threshold, and where is that written?",
"scope": { "process": "meter-to-cash/exception-handling" },
"budget": { "maxTokens": 1500 },
"minCuration": "derived"
}RESPONSE
{
"slice": {
"process": "Exception handling",
"elements": [
{
"type": "event",
"name": "RebillApproved",
"curation": "confirmed",
"facets": [
{ "kind": "person", "role": "Credit Manager", "responsibility": "approves" },
{ "kind": "policy", "name": "Rebill approval threshold" }
],
"evidenceRef": "ev-0042#provenance"
}
]
},
"budget": {
"declared": 1500,
"used": 862,
"truncated": false,
"droppedLowestSignalFirst": []
},
"ranking": "confirmed > reviewed > derived > auto-placed"
}THIS IS A PREVIEW
The shape above is settled enough to publish and not settled enough to build against without talking to us. If you want to know when it stabilises, leave an address. One email, when it is ready, and nothing else.
FOR THE PERSON DECIDING
Which tiers include API access, and what it costs →