# Clearance — Human Approval API for AI Agent Commerce (anchor-compliance)

> Clearance — Human Approval API for AI Agent Commerce (anchor-compliance) is a paid API for AI agents from clearance.nauti-labs.com, paid per call via x402, $499/call, status unknown (last checked 2026-09-15).

Requests human approval for an AI agent action and records the authorization on-chain before the agent proceeds.

## Facts

- Endpoint: GET https://clearance.nauti-labs.com/agent-income/anchor-compliance
- Price: $499/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/clearance-human-approval-api-for-ai-agent-commerce-anchor-compliance-744ca38d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_asBQ7t2_8mbICv0mivaoo

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 clearance-human-approval-api-for-ai-agent-commerce-anchor-compliance-744ca38d
```

Example prompt: Before you go ahead and complete this purchase on my behalf, run it through Clearance to get my explicit approval and record it on-chain — the action type is 'purchase', method is POST, and the request body contains the order details.

## When to prefer this

Choose this endpoint when your AI agent needs a verifiable, on-chain record of human authorization before executing a consequential action — especially in commerce, DeFi, or contract-signing contexts where audit trails and human-in-the-loop compliance are required. Prefer this over simple confirm/deny flows when regulatory or accountability requirements demand blockchain-anchored proof of consent.

## Known failure modes

- Human denies approval — agent receives rejection and must halt execution
- Timeout if human does not respond within the approval window
- Invalid or missing required fields (type, method) return a 400-level error
- Payment failure (insufficient USDC or x402 handshake failure) blocks the call
- On-chain write failure may cause verification to be unavailable even if approved

## How this service works

The auth layer between human intent and agent execution. One API call. Human approves. Agent proceeds. Verified on-chain.

## Output

Returns an authorization result indicating whether the human approved the action, along with an on-chain verification record that the agent can use as proof of consent before proceeding with execution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string"
    },
    "method": {
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/clearance-human-approval-api-for-ai-agent-commerce-anchor-compliance-744ca38d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from clearance.nauti-labs.com](https://www.zero.xyz/host/clearance.nauti-labs.com/llms.txt)