Pryzm Memory

Returns the full content of saved memories by id (up to 20 ids). Meant for results whose excerpt is truncated.

Returns the most important saved memories for one project (decisions, preferences, to-dos, context), sorted by importance. limit caps the results (max 30).

Lists the user's most recently saved memories, newest first, optionally for one project. limit caps the results (max 50).

Returns a compact summary of what the user has saved about themselves: lasting preferences, key facts, working style, active projects and open to-dos. Read-only and deterministic. Returns a structured object and a short text version.

Semantic and keyword search over the user's saved memories. Optional project narrows the search; limit caps the results (max 20). Returns matching memories with id, project, type, date and an excerpt; the full text of a result is available by id. When several memories are versions of the same fact, each carries etat (en_vigueur = in force, remplace = replaced, proposition_non_validee = proposal never agreed, annule = cancelled) and faits summarises them. couverture states how well the results cover the question: non_decide means the point was discussed but never settled, rien_de_fiable means nothing reliable was found.

Searches saved memories with several filters at once: projects, types, minimum importance and a date range (date_from / date_to, ISO dates). An empty query returns the filtered memories sorted by importance. limit caps the results (max 30).

Returns counts about the user's memory: total, active and archived memories, breakdowns by project and by type, and the last activity date per project.

Saves a memory (note, decision, preference, to-do…) in the user's account and returns its id and any close matches.

• content: the text to save (max 20,000 characters).

• type: technical_decision | bug | preference | intention | context | note | todo.

• project: the project it belongs to; tags: optional keywords; importance: 1 to 10.

• on_similar: smart (default) | new | reinforce | skip.

• status: "proposal" for something suggested but not agreed, "decision" for something agreed or final.

• supersedes: ids of saved memories that this one supersedes (for example the previous amount, listed in warnings); they stay visible, marked as replaced. Additive: an exact repeat is reinforced, anything else creates a new memory; close matches are returned in similar, never overwritten (supersedes only marks older memories as replaced, their text is kept). Refused by the server, with nothing saved: content starting with ## (private mode), and content containing a payment card number, an API key or private key, or a password.

Writes a short summary of the memories saved for a project (or the whole memory), with an optional focus. The memories are sent to a third-party language model (Anthropic, United States): only if the user turned on "AI tagging and grouping" in Pryzm Settings, on paid plans, up to 20 summaries per day. Without that setting, the call is refused with an explanation.

Returns the key facts and preferences the user has saved that relate to a topic or project. limit caps the results (max 10). Useful to check the user's stated preferences before making a suggestion or writing something on that topic.

Lists the memories saved during a period, in date order, optionally for one project. period: today | yesterday | this_week | last_week | 7d | 30d | month | year. limit caps the results (max 100).

Returns a snapshot of the user's active projects, open to-dos, recent decisions and intentions, and saved preferences. Useful when the first message of a conversation is about the user's work, clients or projects.

Closes the current step of a plan with its deliverable and one proof per checklist item, in checklist order. The server refuses, and lists exactly what is missing, when the deliverable is empty or a criterion has no proof; it also refuses any step other than the current one. A closed step never changes: to fix it, a correction step can be proposed as an amendment. Each closure is also saved as a memory in the plan's project. A phase completed by this closure waits for the user's validation. Refused by the server, with nothing saved: content containing a payment card number, an API key or private key, or a password.

Creates a step-by-step plan as a draft, attached to one of the user's projects. A plan can be followed from one conversation or assistant to another.

• project: the project the plan belongs to.

• goal: what the plan should achieve.

• phases: ordered phases, each with a title and ordered steps. Each step has a title, an instruction, a checklist of 1 to 6 verifiable criteria that define when it is done, and the expected deliverable. A plan has at most 200 steps; the free offer allows one open plan at a time. The plan stays a draft until the user approves it. Refused by the server, with nothing saved: content containing a payment card number, an API key or private key, or a password.

Returns the working frame of the current step of an active plan: the plan goal, the phase and step numbers, the step instruction, its checklist of done criteria, the expected deliverable, the deliverables of the steps already closed in this phase, and the rule to follow. Only one step is current at a time: the first step not closed in the open phase. When a phase is complete, no step is returned until the user validates the phase.

Lists the user's plans, optionally for one project, newest first, with their status (draft, active, done or abandoned), current version, progress (closed steps out of the steps of the current version) and the number of amendments waiting for the user's decision.

Proposes a change to an active plan, with a justification. Each operation is one of:

• add: a new step in a phase (phase number, optional position, step);

• remove: a step that is not closed (step_id);

• modify: new content for a step that is not closed (step_id, step);

• move: a step that is not closed to another place (step_id, phase, optional position). Closed steps and validated phases cannot change; to correct a closed step, add a correction step. The amendment changes nothing until the user accepts it, in the Pryzm dashboard, or in the conversation when they explicitly agree.

Returns where a plan stands: status, current version, progress, each phase with its steps and their status, the current step, the amendments waiting for the user's decision and the next action.

Records the user's decision on a draft plan, a completed phase or a proposed amendment. confirmed_by_user must be true: it states that the user explicitly accepted or refused in the conversation. The user can also decide in the Pryzm dashboard, and the history records which way each decision came from.

• target: plan | phase | amendment; decision: accept | reject.

• phase: the phase number, for target phase; amendment_id: for target amendment; comment: optional note from the user. Accepting a plan makes it active (version 1) and rejecting it abandons it. Accepting a phase opens the next one; rejecting it keeps it open for correction steps. Accepting an amendment creates the next version of the plan.

Lists the projects the user's memories are organised into, with each project's description and number of memories. Use to pick the right project name before searching or saving.