Dismiss a proposed action
Decline a proposal. Nothing runs, and the card records who said no.
Request
- Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
- URL: https://api.getoneprofile.ai/assistant/actions/{proposal_id}/dismiss/
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Path parameters
Response
Successful Response
The verb's or tool's own record of what it made; null until applied. A tool card carries content (what the assistant read back), link (an app path to the thing), link_label (its name), entity_id, opens (whether the page should go to the link when this lands) and made (what was created, for the AI-made mark), plus any facts the tool added.
What the Approve button says: "Approve", or with the most it spends, "Approve · up to 8 credits", or with a flat price, "Approve · 8 credits", or per day, "Approve · up to 145 credits a day".
Cards the assistant raised together in one reply share this, so they can be shown and approved as a group. Null for a card raised on its own.
What the run this card started was charged, in credits, once it finished. Null until then, and for every card that starts no run.
Whether approving this removes something. A destructive card is drawn apart from the safe ones, is never offered a standing grant, and is listed on its own in the confirm an Approve all opens.
Why an approval failed to apply, in plain words; null otherwise.
What the run usually costs, in credits, read from what the same kind of cell has been charged before; equal to price_credits for a flat price, which the card then says as one figure. Null for a card whose price is the whole story.
Whether the card may offer Approve and allow in this conversation: only a pending proposal of a verb that is not a send.
How an approved card is carried out.
VERB is F-15's eight hand-written workspace verbs: each has a spec in the registry with its own apply, because applying one is real work rather than a single request.
TOOL is any route the assistant may call. An approval re-issues the request the model asked for, through the same executor an MCP client would use, so there is nothing to write per route and nothing to keep in step.
What approving a destructive card takes away, and whether it comes back, in one sentence; null when nothing is removed.
Which surface raised a proposal.
Kept as its own enum rather than reusing the thread-store origins: a scheduled search proposes with no conversation behind it at all, and the activity feed needs to say so.
What a waiting card says beside its Approve button, when the button does not say it all: "usually about 24", "Free", "Free to build · sending about 45 credits". Null when the button says everything.
The published price of the operation when it was proposed, in credits; null when free.
What the card says it costs: "Free", or the most it can spend, "Up to 16.5 credits"; for a run charged by use, "Up to 65 credits · usually about 24"; for a flat price (a run of enrichments that each have one price), the one figure, "2,800 credits"; once that run has ended, "Charged 23.8 credits"; and for a card priced per day, "Up to 145 credits a day", before and after it is approved.
What a card's price is the price of: one call, or each day of what the call starts.
CALL is nearly every card: the most approving it may spend, once. DAY is a card that starts (or re-arms) a standing buy that goes on spending by itself, adding rows every day: its price is the most one day may cost, said "up to 145 credits a day", and Approve all keeps it out of the one-off total it adds up. No tool starts one today.
The column approving this card runs, while the card waits: the one it added, or one already on the table that it names. Lets the column's own panel approve this card instead of starting a second run. Null for a card that runs no column, and once the card is decided.
The agent column whose run raised the card; null for every other origin. What puts a card on its table's page when its arguments name a sequence or a destination instead of the table.
The row the agent was working on when it raised the card; null otherwise.
Where one proposed action stands.
PROPOSED waits on a person. APPLIED happened. DISMISSED is a person saying no. FAILED is an approval whose apply raised; the error stays with the row so the card can say why instead of vanishing.
UNDONE is HISTORY ONLY. Nothing reaches it any more: undo was taken out while the assistant moved from eight hand-written verbs to any route it may call, because reversing an arbitrary write is per-route work nobody has done yet. The member stays because rows in this state were written before that, and a status the code cannot read is an activity feed that raises instead of loading.
What the card proposes: one of the eight workspace verbs, or the name of an API operation the assistant asked to call. kind says which.
Changes
No recorded changes to this operation across all 1 revision of this API.