# Agent Outbound Action Pre-Validation

> Agent Outbound Action Pre-Validation is a paid API for AI agents from agent-outbound-action-ljoeb.ondigitalocean.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Validates an outbound HTTP action (POST/PUT/PATCH) before it is executed, returning VERIFIED or FAILED with structured violation details.

## Facts

- Endpoint: POST https://agent-outbound-action-ljoeb.ondigitalocean.app/verify
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-outbound-action-pre-validation-14ebe836
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_a3Gzjs3D9Stt82Y_Izlr4

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 agent-outbound-action-pre-validation-14ebe836 -d '<json body>'
```

Example prompt: Before my agent sends this POST request with a JSON body to install a package and request file-system permissions, run it through pre-action validation to check for any violations and confirm it's safe to execute.

## When to prefer this

Use this endpoint when an AI agent needs a safety gate before executing any state-changing outbound HTTP action (POST, PUT, PATCH) — especially for actions involving payments, installs, or elevated permissions. Prefer this over ad-hoc permission checks when you need structured violation reporting and a clear VERIFIED/FAILED signal that can gate downstream execution in an agentic workflow.

## Known failure modes

- Missing required 'input' object returns schema validation error
- Invalid method (e.g. GET instead of POST/PUT/PATCH) causes rejection
- Malformed bodyType enum value returns error
- Requested permissions flagged as policy violations return FAILED with violations[]
- Payment not included when required — service instructs to pay 0.1 USDC via Base and resubmit with proof
- Empty or null body causes validation failure

## How this service works

outbound_action_v1 — pre-action validation before post/send/install/pay. VERIFIED or FAILED with structured violations[]. Pay Base USDC then resubmit with payment proof.

## Output

Returns a VERIFIED status if the outbound action passes all checks, or FAILED with a structured violations[] array detailing each specific policy or permission issue found, allowing the agent to correct and resubmit.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "context": {
   "type": "object"
  },
  "skill_md": {
   "type": "string"
  },
  "requested_permissions": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-outbound-action-pre-validation-14ebe836/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-outbound-action-ljoeb.ondigitalocean.app](https://www.zero.xyz/host/agent-outbound-action-ljoeb.ondigitalocean.app/llms.txt)