Which actions need approval
An action needs approval when it grants or removes access to an account, creates an account or another commercial commitment, or cannot be undone. Routine and reversible work, such as reading, drafting and edits you can undo, runs straight away on the authority you gave the agent. The page for each action says whether it needs approval. These actions need it today:- Creating a Buyer child account through MCP
- Accepting or switching an IU plan through
save_billing. Only a direct administrator of the billing organization can approve it: an administrator of a parent organization who is not a direct member cannot. - Choosing the payment terms sellers are asked for through
save_billing. The same direct administrators approve it. - Ending the plan at term end, or keeping it renewing, through
save_billing. The same direct administrators approve it. - Removing a saved card through
save_billing. The same direct administrators approve it. - Paying a failed payment now through
save_billing. The same direct administrators approve it. - Changing where a Seller is paid (payout bank details) from the Plan & Billing Page or an API call. The same direct administrators ask for it and approve it. A person typing them into the Apostra web app’s own Plan & Billing screen is already signed in on Apostra, so that save stays direct. The approval page shows the account number and bank identifier only as their last four characters.
- Setting up a card payment method through
request_payment_authority. The same people can ask for it and approve it. The hosted card page that follows needs no sign-in, so the cardholder can be someone other than the administrator who approved.
Why the approval happens on our site
When an agent calls Apostra through MCP or the API, Apostra cannot tell whether a person is behind that particular call or the agent chose to make it. An agent’s client could also show a convincing “Approve?” button that the agent controls. So for these actions the approval happens somewhere the agent and its client are not involved: a page on the Apostra site, opened in your own browser and signed in with your own login. This follows the approach the MCP specification recommends for interactions that must not pass through the model or the client.What the agent receives
The action does not fail. The agent receives anapproval_required result
with:
- a link to the approval page,
https://<your Apostra site>/approve/<approval id> - the approval’s state
- when it expires
Who can approve
Only a person who:- is signed in to the Apostra site in their own browser, and
- holds the role the action requires on the account, usually administrator.
What the page shows
The approval page shows what will happen, which account it applies to, who asked for it and how they authenticated (for example, “a personal API key”), which client the request came through, and the deadline for deciding. The client is recorded from the requester’s own connection, never from what the request says about itself: an MCP client the connection identified (for example “Claude over MCP”), “An MCP client” when it did not identify itself, or “The REST API”. If you do not recognise the client, reject the request.What happens next
Once a request is final, Apostra deletes the detailed request data it kept for
running the action, and keeps only the outcome and an audit record of the
decision.
See what is waiting
An agent or a person can list everything waiting on an account, so a request nobody was watching is not missed. In the Apostra web app, Approvals in the Account group of the left rail lists the approvals waiting on the account you are in: what kind of request each one is, what will happen, whether it is still waiting for a decision or approved and still running, and when it expires. Open takes you to that request’s approval page, where an administrator approves or rejects it. The list itself changes nothing. In Murph, Claude and other assistants connected to Apostra, an agent opens the same list as a page with theopen_pending_approvals tool, in any kind of
account. In ChatGPT it arrives once OpenAI’s automatic review of our tools
approves it, usually within days. Each row links to its approval page, which
opens on the Apostra site; the page approves and rejects nothing.
Agents read the same list through the API:
searchwithkind: "approval"lists the approvals waiting on the account the call runs in, newest first: those still waiting for a decision, and those approved and still running. It returns up to 25 by default (limit, at most 50) and says when there are more.getwithkind: "approval"and an approvalidreads one approval in any state, including its outcome once it is final.
When the action makes a secret
Some actions make a secret for the person who approved them, such as a credential or a one-time link. The secret never goes to the agent. Once the action has completed, the approval page offers Show the secret to the person who approved it, and to nobody else.- It is shown once. Showing it deletes the stored copy in the same step, so copy it straight away and store it securely. Do not paste it into a chat with an agent.
- It can expire. If nobody shows it within the window the action sets, the stored copy is deleted and the page says it is no longer available.
- A lost secret is not recoverable. If the page closed before you copied it, ask the agent to make the request again.