Developers

Add an action decision to the tools you build.

Start with the local demo, choose your integration and test one real executor before broadening coverage.

Where the action needs a decision

An agent’s model response is not the final tool call. Put policy where the final arguments are available and the application can still stop the side effect.

01

Try the local simulation

Compare blocked and allowed fixed inputs without an account, API key or running framework.

02

Attach your integration

Use the SDK, plugin or forwarding wrapper appropriate to the application’s actual execution boundary.

03

Verify your application

Exercise allowed, denied and unavailable responses, check sanitised arguments and confirm that alternate paths cannot bypass the intended decision.

Build a testable deployment.

Keep credentials out of browser code, connect to the assigned runtime endpoint and use the integration documentation for version compatibility. Review generated integration changes before applying them.

See the decision before the action.

Try a local scenario, then bring your workflow to a deployment review. Start with one agent and one tool, and see exactly where the action can be stopped.