Try our new Setup Skill to automatically integrate Hyperspell into your project
API Documentation
Memories
Messages
Traces
Authentication
Daemon
Integrations
Connections
Folder Policies
Vault
Context Documents
- GETList conflicts for the authenticated app
- POSTApprove or reject a pending conflict
- GETEvent log for a conflict
- POSTManually trigger conflict detection for a tree
- POSTGenerate a context document
- GETPreview available data for context document generation
- GETList context documents
- GETGet a context document
- POSTGenerate context docs folder structure in Google Drive
- POSTGenerate a three-tier context document tree
- GETGet tree generation progress
- GETGet the latest context document tree
- GETGet a specific context document tree by tree_id
- POSTPublish a COMPLETED tree (require_review flow)
- PATCHEdit files in a context document tree
- POSTRename a team — persists to config, applied on next regen
- GETList active team rename overrides
- DELClear a team rename override
- GETList persisted user edits for an app
- POSTLLM-based three-way merge of a user edit with the current LLM output
- POSTMark the user's decision on an edit — records which baseline they reviewed
- DELClear (soft-archive) a persisted edit
- GETDiff a tree against the previous tree
- GETCheck staleness of context documents
Mark the user's decision on an edit — records which baseline they reviewed
curl --request POST \
--url https://api.hyperspell.com/context-documents/tree/{tree_id}/edits/{edit_id}/resolve \
--header 'Authorization: Bearer <token>'{}Context Documents
Mark the user's decision on an edit — records which baseline they reviewed
Stamp reviewed_baseline on the edit with the current tree’s
baseline for this edit’s path.
Called by the UI after Keep-mine and careful-merge save, so the row disappears from “needs review” until the next regen produces a different baseline. Auto-merge handles this in its own handler.
POST
/
context-documents
/
tree
/
{tree_id}
/
edits
/
{edit_id}
/
resolve
Mark the user's decision on an edit — records which baseline they reviewed
curl --request POST \
--url https://api.hyperspell.com/context-documents/tree/{tree_id}/edits/{edit_id}/resolve \
--header 'Authorization: Bearer <token>'{}Documentation Index
Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
APIKeyAsUser
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
Response
Successful Response
Was this page helpful?
LLM-based three-way merge of a user edit with the current LLM output
Previous
Clear (soft-archive) a persisted edit
Next
⌘I
Assistant
Responses are generated using AI and may contain mistakes.