The public Sender API v2 now focuses on one integration job: run a reviewed plan and reconcile what happened.
There are no external production integrators yet, so this pre-launch change was made directly in v2 instead of introducing a v3 migration nobody needed.
What remains public
- identify the calling key with
GET /me; - upload a run input;
- list, read, and run published plans;
- list and read the resulting correspondence and participants;
- withdraw a run before it reaches anybody;
- read claims and collected responses, including explicitly gated sensitive fields or submitted files; and
- resolve permission state or consume the permission-change feed.
The API-key surface contains 16 operations and seven scopes. Public covenant verification remains unauthenticated and is not an API-key operation.
What moved to Workspace
Plan authoring, one-off composition, team and connection management, billing, API-key lifecycle, webhook configuration, audit and metrics, exports, and operator recovery actions remain available in Keepable Workspace. They are no longer callable by an organisation API key.
Existing public integrations do not require migration because none had been launched. Start with The model and Run a plan.