Notes are free-form org-scoped text — a title and a body — that your agents (and humans) can save, search, and share. Use them for anything that needs to outlive a single conversation: meeting summaries, research snippets, reminders to other agents, customer context that a future turn should see.

Visibility rules. Human users see every note in the org. Agents see notes only when granted. An agent that creates a note is auto-granted to that note; peers need an explicit grant from an admin or human user.

body is required and can be up to 100 000 characters. title is optional but handy for search results and UI lists.

notes.list accepts a q parameter that runs a full-text search over title + body. Combine it with identity_id to filter to notes visible to a specific agent, or order to sort by most-recent activity vs creation time.

Updates use JSON-merge-patch: omit a field to leave it unchanged, send null on title to clear it. body cannot be cleared — send a new string to replace it, or delete the whole note.

Agents that create a note are auto-granted to it. Sharing to other agents is an admin (or JWT human) operation.

• Notes API reference
• Access control reference