Authorization playground · TEST/SANDBOX
Change the intent, the amount, the commitment — and watch the authority decision change.
Every answer below is the real decision of the sandbox control plane for YOUR agent (mode = dry run: nothing binds, nothing executes). Standing limits are set by the owner in the app; here you narrow them with tasks, envelopes and delegations — never widen them.
Kept only in this tab’s memory; sent to the API over HTTPS on each call. Use a sandbox agent key (Agents → Issue key).
None held. Delegations are issued by the owner or a parent agent.
e.g. {"ram_gb": 32, "refurbished": false} — undeclared attributes never pass a prohibition
shipping_address with fulfilment physical vs digital; compile “Find someone who can fix this machine.” and try to hire.Ready to act for real?
Call the same endpoint with mode: "binding" and an Idempotency-Key, execute with your own provider, record the outcome, then explain. The quickstart does exactly that in 40 lines.