Changing things
Every change is the same press the page makes, through another door: made once, bounded three ways, written to the audit log as made through the API.
One press, three doors
When a person marks a bill handled on the Checkup, the page calls one method. The API calls the same method. So does the MCP tool. There is no second implementation of “handled” for machines, which is why a change through the API does exactly what the page does - closes the item, settles what it settled, recomputes the Checkup - and why the audit row says only which door it came through: page, api or mcp.
That also decides what is in the API: what a person would do with their own paper from a script or an assistant, and nothing the page cannot do. A press that only makes sense in front of the page - cropping a photo by hand, answering the setup cards, saying which of two lookalikes is the copy - stays the app’s own and is not here.
What it takes
A change needs the write scope, an owner or member, and a paid plan; scopes, roles and plans has the walls and which one says no. Every change that could be sent twice takes an Idempotency-Key.
curl -X POST "https://api.thawed.app/v1/documents/019958a0-1c4e-7d3a-9b2f-3f0c2a6e8d11/type" \
-H "Authorization: Bearer $THAW_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"type_id":"019958a0-4f71-706d-8e52-6c3f5d91b044"}'
The answer is the thing as it stands after the change - the document row, the Checkup item, the person or thing - so there is nothing to fetch again.
The changes
On a document (Documents): correct its title, date or summary; file it as something else, or as a type of your own, with “move all” for every document of that type; link and unlink a person or thing with a role; correct a fact; say it looks right, or read it again; share it by link and take the link back.
On the Checkup (Checkup): handle, snooze, dismiss or reopen a dated item, say a bill is paid by hand, set how far ahead an item is raised; say something missing is fine, or ask again; make a reminder.
On the people & things (People & things): rename, correct the details, say what is still yours.
Putting paper in (Documents, Uploads) is its own kind of change: the role and the scope, never the plan, so a Free family’s shortcut can add. Adding documents has the two roads.
When it cannot be made as asked
A change the page would refuse is refused here with the same sentence: a document still being read (409), a quarantined file (403), a bundle guest changing anything (403). It comes as a problem with detail in Thaw’s words - show it.
What a change never does
Nothing here deletes a document; that stays on the page, behind the typed confirmation. Nothing changes who is in a family or what a guest may see; that is Settings. Nothing re-reads a document at the model unless asked with read-again, which counts as a read on the plan the way the page’s does.