# DYOE Guardian — Agent Action Authorization Gate

> DYOE Guardian — Agent Action Authorization Gate is a paid API for AI agents from dyoe-audit-verify.netlify.app, paid per call via x402, $2/call, status unknown (last checked 2026-09-16).

Evaluates whether an AI agent is permitted to take a specific action on behalf of its human, returning approved, needs_human, or denied based on trust and policy rules.

## Facts

- Endpoint: GET https://dyoe-audit-verify.netlify.app/approve
- Price: $2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dyoe-guardian-agent-action-authorization-gate-740edcf0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dkp_3CrypJsjXw4UK9Wp5

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability dyoe-guardian-agent-action-authorization-gate-740edcf0
```

Example prompt: Before you send $250 to counterparty 'acme-payments.io' for the 'purchase_subscription' action, check DYOE Guardian to see if you're approved to do this on my behalf or if I need to sign off first.

## When to prefer this

Use this endpoint when an AI agent needs a policy gate before taking consequential actions — especially financial transactions, interactions with external counterparties, or any irreversible operation. Prefer this over simple allow-lists when you need a dynamic, amount-aware, counterparty-aware trust check that can flag actions requiring explicit human approval rather than binary allow/deny.

## Known failure modes

- Missing required query parameters (action, counterparty, or amount) returns an error
- Unrecognized action type may result in a conservative 'needs_human' or 'denied' response
- Network timeout from Netlify hosting may cause unavailability
- Policy rules may be stale if not updated, leading to incorrect verdicts
- Amount format mismatch may cause parsing errors

## How this service works

DYOE Guardian — should an agent be allowed to take this action for its human? Automated trust + policy gate that returns approved / needs_human / denied (flags actions that need human sign-off). Input: ?action=&counterparty=&amount=

## Output

Returns one of three verdicts: 'approved' (agent may proceed autonomously), 'needs_human' (the action requires explicit human sign-off before proceeding), or 'denied' (agent is not permitted to take this action). This lets an orchestrating agent know whether to proceed, pause and ask the user, or abort.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "action": {
       "type": "string",
       "description": "What the agent wants to do"
      },
      "amount": {
       "type": "number",
       "description": "Amount in USD"
      },
      "counterparty": {
       "type": "string",
       "description": "Domain or wallet on the other side (required)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dyoe-guardian-agent-action-authorization-gate-740edcf0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dyoe-audit-verify.netlify.app](https://www.zero.xyz/host/dyoe-audit-verify.netlify.app/llms.txt)