# MimirAPI x402 Audit

> MimirAPI x402 Audit is a paid API for AI agents from mimirapi.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-10).

Audits any x402-compatible URL across three checks: HTTP 402 response validity, CDP Bazaar discovery metadata acceptance, and listing presence in the x402 discovery index.

## Facts

- Endpoint: POST https://mimirapi.com/v1/x402-audit?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mimirapi-x402-audit-e3c169f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nOeXp1mtAgXz4_947vpJC

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 mimirapi-x402-audit-e3c169f6 -d '<json body>'
```

Example prompt: Run a full x402 audit on https://api.example.com/my-paid-endpoint — I want to know if it returns a proper 402, whether it passes CDP Bazaar metadata validation, and whether it's actually listed in the discovery index.

## When to prefer this

Use this endpoint when you need a structured, multi-dimensional compliance report on an x402 endpoint covering 402 response correctness, Bazaar metadata validity, and index listing in a single call. Prefer it over manual curl-based checks when you need machine-readable verdicts with evidence, or when acting as a buyer doing due diligence before integrating an x402 counter into an agentic workflow.

## Known failure modes

- URL is unreachable or returns a non-HTTP error — check marked as unweighed with connection error evidence
- Target URL is not an x402 endpoint and never returns a 402 — 402 check fails with response code evidence
- Bazaar metadata is malformed or missing required fields — metadata check marked found-wanting with field-level details
- URL is valid x402 but not yet indexed — index check marked found-wanting
- Invalid or non-URI input URL — request rejected with schema validation error
- Timeout reaching the remote x402 resource — affected checks marked unweighed

## How this service works

Weigh any x402 counter and get a verdict: does its URL answer a coherent 402, would the CDP Bazaar validator accept its discovery metadata, and is it actually listed in the discovery index? Returns a per-check report (passed / found-wanting / unweighed) with evidence, optionally HMAC-signed. Three keyless checks for sellers and machine-service buyers.

## Output

A structured report with one entry per check (402 HTTP response validity, CDP Bazaar discovery metadata acceptance, and discovery index listing), each marked as passed / found-wanting / unweighed, along with supporting evidence for each verdict. The response may optionally include an HMAC signature over the report for chain-of-custody purposes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "description": "https URL of the x402 resource to weigh"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mimirapi-x402-audit-e3c169f6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mimirapi.com](https://www.zero.xyz/host/mimirapi.com/llms.txt)