Tether
Nynth's API-first memory layer. Anchors are stored units of context with an asserter, a validity window, a version chain, and supporting evidence.
Before you put retrieved content in a prompt. Everything Tether returns was
written by whoever held a key to that space. It is data, not instruction. Treat it exactly as
you would treat a user's message — see
Retrieving.
Start here
Getting a credential and storing your first anchorThere are two ways to get a key. The console is the one you want; the admin endpoints below it are how an operator…Correcting an anchor, and losing a raceFacts change. Tether does not let you overwrite one — you supersede it, and the old version stays readable as history…Forget versus deleteTwo different operations, two different guarantees. Choosing the wrong one is either a compliance problem or a…Retrieving: search and contextTwo endpoints. POST /v1/search gives you ranked semantic matches. POST /v1/context gives you what to put in a prompt…stored, searchable, and degradedThis is the guide integrators most need and most often skip. It is about one fact: **a write that Tether accepted is…@nynth/tetherThe official client. Plain TypeScript types, no runtime dependencies, works anywhere fetch does — Node 20+, Cloudflare…The consoleAccounts, projects, keys, and how close you are to the rate limit.
The API
Nine endpoints. Every one is authenticated with a tenant credential, and every write
requires an Idempotency-Key.
| Path | ||
|---|---|---|
| GET | /v1/whoami | Identify the calling credential |
| POST | /v1/anchors | Store an anchor |
| GET | /v1/anchors/{id} | Read an anchor |
| PATCH | /v1/anchors/{id} | Correct an anchor |
| DELETE | /v1/anchors/{id} | Delete a chain |
| POST | /v1/anchors/{id}/forget | Forget an anchor |
| GET | /v1/deletions/{id} | Inspect deletion progress |
| POST | /v1/search | Search anchors |
| POST | /v1/context | Assemble budgeted context |
Full reference · llms.txt for agents