Contextick

Use this when the user asks what is new in their knowledge rather than about a topic — e.g. "what did I add since Monday?" or "catch me up on what I've saved" — for a topic, use search. It is a cursor-based incremental feed over insertion order: since sets the starting point on the first call, and every response carries a cursor that continues from where that page ended. Items come back with their titles and summaries; the full text comes from get. Ordering is ascending, so a page holds the oldest items after the cursor rather than the most recent ones — a period is expressed with since, not with a small limit. The feed carries additions only: an item deleted afterwards is simply absent, and an item whose status changes later does not reappear, because that is not a new item.

changes

Use this when the user wants you to forget saved items — pass one or more ids from a prior search result. Permanently removes them from the user's knowledge and can't be undone, so confirm which items with the user before deleting. If you are replacing an item with a revised version, save the new version first and delete the old id only after that save succeeded — deleting first loses the original.

delete

Use this when the user wants a whole uploaded file gone rather than one item — e.g. "delete that PDF I uploaded" or "get rid of the whole report, not just this piece". It takes the group label the parts of an upload share, which search, get, changes and the opened lists return on any item that came from one, and removes every part carrying that exact label. Removal is permanent and cannot be undone, and it is all of the file at once rather than the part the user was looking at. Items saved directly, and parts of other uploads, carry different labels and are left alone.

delete_group

Use this when you need the full text of a saved item you found via search — to quote it, or when the user wants to change something they already saved. Pass the id from a prior search result. Returns the item's full content. Search results are only summaries, so this is the only way to read the full text — when revising, call it first to get the whole note, otherwise the rest is lost.

get

Use this when the user asks about the whole uploaded file an item came from rather than about a topic — e.g. "show me the rest of that report" or "how much of that upload is ready?". A file uploaded to Contextick is stored as numbered parts that share one group label, and search, get, changes and the opened lists hand that label back on any item that came from an upload. This lists every part of that file, in order, with the state of each. The title is shared, so it is given once for the whole file and the parts come back as ids and states — a part's text comes from get, by its id. It is a listing rather than a read: nothing is opened by being listed here.

get_group

Use this when the user wants to review what they have saved by how much use it has had — e.g. "what have I saved and never looked at?" or "which notes am I not using?". It is a ranking over everything saved, not a feed: items are ordered by how many times their full text has been opened, fewest first, and n takes the head of that ranking. It sorts rather than filters, so every saved item is somewhere in the ordering; the header states how much of the whole store is in view. There are no pages — the same call returns the same items. most_opened is the same ranking read from the other end, so the two overlap rather than divide the items between them.

least_opened

Use this when the user wants to see which of their saved items they keep coming back to — e.g. "what do I reference the most?" or "which notes have I actually leaned on?". It is a ranking over everything saved, not a feed: items are ordered by how many times their full text has been opened, most first, and n takes the head of that ranking. It sorts rather than filters, so every saved item is somewhere in the ordering; the header states how much of the whole store is in view. There are no pages — the same call returns the same items. least_opened is the same ranking read from the other end, so the two overlap rather than divide the items between them.

most_opened

Use this when the user wants to keep something worth coming back to — a code snippet, an idea, a design or decision, a report, or research notes ("save this", "remember these findings"). Before saving, shape it into a clear title, a self-contained note, and a short summary. Keep the content faithful — don't summarize or drop parts to make it fit. Content is capped at 16,000 characters per call; if it runs longer, split it into coherent parts and call save once per part so nothing is lost. When saving a revised version of something already stored, first call get to read the original in full, then save the entire updated note — the whole thing with the change applied, not just the changed part — because search results are summaries, not the full text, and revising from them loses the rest. Adds it to the user's knowledge so you can pull it back later with search.

save

Use this when you need something the user saved earlier — they mention a past note, decision, idea, or piece of research, or you need that context before answering; e.g. "what did we decide about the pricing page?" or "pull up my notes on that coffee idea". Give what to recall in natural language: a topic, a question, or a few keywords. Returns the saved items closest in meaning, ranked by how close. It matches on meaning, so it finds items that share no word with the request; for what was saved recently rather than what it is about, use changes. When the user points to their own past context, call this before answering. Each item comes back as its summary, not the full text — call get with an id to read the full text when you need to quote or revise it.

search

Use this when the user asks how much they've saved or how much space their knowledge is using — returns the total number of saved items and their total size in bytes.

usage