strategies
Check Source Ancestry
How does a client source snapshot relate to this strategy's commits?
Batch-11 seam for chat-api: a snapshot byte-identical to a SUPERSEDED main-line commit is provably historical — the caller should prefer the saved head rather than silently reverting newer work. A snapshot matching nothing is novel text and stays authoritative (fail-open). The server computes the hash of the exact bytes; callers never hash.
post/v1/strategies/{strategy_id}/source-ancestry
Request
- Base URL: https://api.usekeel.io (the document declares no server; this is the origin it was published from)
- URL: https://api.usekeel.io/v1/strategies/{strategy_id}/source-ancestry
- Auth: none declared
Path parameters
strategy_idstring required
Headers
Authorizationstring nullable
X-Org-Idstring nullable
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.