Mutations require stable idempotency keys. Updates and decisions bind the reviewed revision or pending request. Owner/admin membership, user identity, API key scopes, and resource ownership are checked server-side. Application service accounts cannot act as an owner.
The canonical wire resources are
agent and operation, with agentId and operationId. The existing v2 Host routes remain compatibility endpoints; v3 clients use the new routes and fields directly.
Publishing never bypasses executable-route verification. Owner admission never grants requester consent. Campaign submission persists a review request without claiming paid delivery or charging funds. See Campaigns and Analytics for measured coverage.