# Agent Seller Ops x402 Audit

> Agent Seller Ops x402 Audit is a paid API for AI agents from agent-seller-ops.inboxtzdjqv.workers.dev, paid per call via x402, $0.009/call, status unknown (last checked 2026-10-18).

Validates whether an agent tool endpoint is x402 payment-compatible and has a correct agent tool schema before publishing.

## Facts

- Endpoint: POST https://agent-seller-ops.inboxtzdjqv.workers.dev/v1/x402-audit?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-seller-ops-x402-audit-331a3557
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sWADJu9Kf3_zpefybTPUi

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-seller-ops-x402-audit-331a3557 -d '<json body>'
```

Example prompt: Can you run an x402 audit on my agent tool at https://seller.example/v1/tool using a POST request to make sure it's payment-compatible and the schema is correct before I publish it?

## When to prefer this

Use this endpoint when you are an autonomous agent seller preparing to publish a tool endpoint and need a deterministic, paid, objective audit of x402 payment compatibility and tool schema correctness. Prefer this over manual testing when you need a scored, structured report that can be programmatically consumed, and especially before listing on agent marketplaces or facilitators that require x402 compliance.

## Known failure modes

- Target URL is unreachable or returns unexpected non-402 status — audit may report incompatible with failed checks
- Malformed input URL causes validation error before reaching the target
- Target endpoint does not implement x402 at all — score of 0 and compatible:false returned
- Network timeout reaching the target endpoint — request may fail or return partial results
- Invalid method enum value in request body causes schema rejection

## How this service works

Deterministic paid checks for autonomous-agent sellers to validate x402 payment compatibility and agent tool schemas before publishing.

## Output

Returns a JSON object with a numeric compatibility score (0-100), a list of individual audit checks performed, the target URL, the x402 challenge object, a boolean indicating full x402 compatibility, the HTTP status code observed (e.g. 402), and the detected x402 protocol version.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri"
  },
  "body": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "score": 100,
  "checks": [],
  "target": "https://seller.example/v1/tool",
  "challenge": {},
  "compatible": true,
  "httpStatus": 402,
  "x402Version": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-seller-ops-x402-audit-331a3557/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-seller-ops.inboxtzdjqv.workers.dev](https://www.zero.xyz/host/agent-seller-ops.inboxtzdjqv.workers.dev/llms.txt)