Requesting decisions

Requesting a decision is simply how you ask DelegateZero to act on your behalf. A decision request represents a moment where you would normally pause, evaluate context, and decide how to proceed - whether that means approving something, responding to a message, drafting content, or escalating for review.

Every request follows the same basic pattern:

1. You submit a request describing what needs to be decided
2. DZ evaluates the request against your stored context
3. A decision is returned along with a response, confidence score, and audit trail

You can submit requests from any system using the API or webhooks. The same decision logic applies regardless of where the request originates.

Async vs. sync

DelegateZero supports two modes:

• Async (default) - The API returns immediately with a pending status. You poll GET /api/v1/decisions/{id} until the decision is ready. Use this for most workflows - it gives DZ time to consult your full context library and pull live data from any connected sources.
• Sync - Add "mode": "sync" to your request. The API runs the pipeline and returns the complete decision in a single response. Faster to integrate, but DZ consults fewer context entries and does not pull live source data. Best for simpler decisions or when your workflow cannot handle async responses.

For best results, we recommend async mode. If using sync mode, expect lower-quality results.

See the Audit logs section for full async polling examples.