Let agents propose.Make actions deliberate.
Separate recommendations from live changes with explicit permissions.
Separate recommendations from live changes with explicit permissions.
Separate capabilities
A reporting tool does not need budget-editing permission. A draft tool does not need publishing permission. Our proposed pattern separates these capabilities so a reporting mistake cannot directly become a live action. Begin with one bounded workflow whose output a person can inspect.
Approve an exact change
Show the account, resource, current value, proposed value, currency, and execution time. Include evidence and reasoning. A goal such as campaign optimization is not an exact approval. If the proposal or resource state changes after review, recheck conditions and obtain approval for the revised action.
Handle uncertain outcomes
A timeout might mean failure or a lost acknowledgement. Give requests identifiers and check recorded outcomes before retrying. Log the proposal, reviewer decision, execution attempt, and confirmed result separately. Test rejection, expiry, missing data, and recovery as well as success.
Sources and further reading
The references below support the definitions and methods discussed. Implementation examples and recommendations reflect Atakan AI’s perspective.
Ads Agent API
Explore the product direction and join for launch and early access updates.