Skip to content
Developers

Knowledge Vault

Entries

An entry is one card in a Knowledge Vault section. Listing and reading return the full write-up and do not spend AI tokens.

List your entries

Newest first. pillarId limits the list to one section, using an id from Sections. status is active (the default), deprecated, or all. limit defaults to 20 and cannot exceed 50. offset defaults to 0. The response includes total, so you can page through everything you have stored.

Each entry includes id, pillarId, title, summary, content, tags, status, updatedAt, and indexed. indexed: false means search may not find it yet. The list still returns it. Sample cards shown in an empty section are omitted.

GET/api/v1/knowledge/entriesvault:read
curl
curl -sS "https://api.thealtermeai.com/api/v1/knowledge/entries?pillarId=offers&limit=20" \
  -H "Authorization: Bearer emk_YOUR_KEY"

Read one

GET /api/v1/knowledge/entries/{id} returns the same fields. A missing id, another workspace’s id, or a sample card is 404.

GET/api/v1/knowledge/entries/{id}vault:read

Add an entry

pillarId, title, summary, and content are required. content may be plain text. A blank line starts a new paragraph, and the product stores it as HTML. tags is an optional list of strings, at most 20. Title is at most 200 characters, summary 500, content 12,000.

The response is 201 with the saved entry. Indexing spends AI tokens. If the wallet cannot cover it, the entry is still saved and indexed is false until a later index run.

POST/api/v1/knowledge/entriesvault:write
curl
curl -sS https://api.thealtermeai.com/api/v1/knowledge/entries \
  -H "Authorization: Bearer emk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "pillarId": "offers",
    "title": "LinkedIn retainer",
    "summary": "Monthly writing for one partner.",
    "content": "What it is.\n\nWho it is for."
  }'

Update and delete

PATCH changes only the fields you send: pillarId, title, summary, content, tags, or status (active or deprecated). Moving an entry puts it in the new section. Changing the text, the tags, or the section re-indexes the row and can spend AI tokens. Changing only status does not. A deprecated entry stays readable and drops out of search.

DELETE removes the row and returns { "deleted": true, "id" }.

PATCH/api/v1/knowledge/entries/{id}vault:write
DELETE/api/v1/knowledge/entries/{id}vault:write