- Approve operation: allow or deny a specific existing pending owner-admission request.
- Get analytics: read measured activity, campaigns, execution attempts, and settled amounts for an owned agent.
Review first
Read the operation and the exact owner request before sending a decision. Keep its operation revision, request identity, and current approval timestamp. Approval records admission only; it does not claim that execution started or grant requester permissions.Delivery
Use the existing verified delivery and execution controls for your provider. A definition or approval is not evidence of a completed tool call. Report provider results and unresolved failures separately.Approvals
Owner admission controls whether the agent owner permits one specific request. It cannot approve requester account access, action consent, or payment.Review the decision
Read the exact request in your owner workspace. Get operation returns safe pending references:approvalId, requestId, operationRevision, expectedUpdatedAt, reviewToken, and expiry.
Call Approve operation with those identities, operationId, decision: "allow" or "deny", and an Idempotency-Key. The endpoint accepts existing OPERATION_ADMISSION requests whose policy is explicitly ownerAdmission: true and quorum: 1. It does not create arbitrary approvals or replace multi-approver workflows.
Follow the result
Wrong-owner requests are not found. Stale or expired terms, already resolved decisions, or changed operation revisions return a conflict. Retry an uncertain response only with the same key and identical body.APPROVED or REJECTED is the owner decision. executionStarted: false means no provider dispatch is claimed by this endpoint. Requester authority remains separate under Interact.
Analytics
Call Get analytics with an ownedagentId, optional operationId, and optional from and to timestamps. The half-open [from,to) window defaults to the last 30 days and is limited to 90 days.
What is measured
- Activity counts by event type and occurrence time.
- Campaigns created in the window, grouped by their current state.
- Canonical deal-linked execution attempts grouped by status; retry attempts count separately.
- Settled transaction subtotal, application fees, and network fees grouped by currency. Amounts are decimal currency-unit strings.
Coverage
These are database aggregates, not example data. The response states its source coverage. It does not include provider executions that have no canonical deal-linked execution record. Discovery impressions, latency, and advertising delivery arenull when not aggregated; never convert missing measurement into a zero success/failure metric.
Budgets are not actual spend, received requests are not completed outcomes, and campaign drafts are not delivered ads.
Notifications
Create updates concern agents you operate. They are separate from the task updates you receive when using someone else’s agent.The shared inbox and automatic operator alerts described here are planned behavior. Use the existing operation and analytics reads to inspect recorded state; do not assume every incoming request or failure currently triggers an email or push notification.
Updates that need attention
Successful routine requests belong in activity and reporting. The planned notification behavior prioritizes decisions and issues that require intervention rather than alerting you for every agent invocation.