# Compliance Evidence Mapper

> Compliance Evidence Mapper is a paid API for AI agents from x402-hono-api.inraby.workers.dev, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-14).

Maps compliance audit email requests to evidence items, owners, systems, and follow-up questions organized by compliance framework (SOC2, ISO 27001, HIPAA, PCI, or general).

## Facts

- Endpoint: POST https://x402-hono-api.inraby.workers.dev/api/v1/compliance-evidence-mapper
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/compliance-evidence-mapper-9c4a12fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1oSZYIbNrVWeMjs0auisw

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 compliance-evidence-mapper-9c4a12fd -d '<json body>'
```

Example prompt: I just got an audit email from our SOC2 assessor asking for access control evidence and user provisioning records — can you map this to specific evidence items, the owners responsible, relevant systems, and follow-up questions I should ask? Subject: 'SOC2 Type II Evidence Request - Access Management', body: 'Please provide evidence of user access reviews conducted in the last 12 months, including provisioning and deprovisioning logs, and access control policies.'

## When to prefer this

Use this endpoint when you have received an actual compliance audit email and need to quickly decompose it into actionable evidence items, identify owners, and surface follow-up questions — specifically when you know the compliance framework in scope (SOC2, ISO 27001, HIPAA, PCI). Prefer this over generic email summarizers when you need framework-aware, compliance-specific structure rather than a plain-language summary.

## Known failure modes

- Missing required 'framework' enum value returns validation error
- Empty or very short email body may produce low-quality or incomplete evidence mappings
- Framework mismatch (e.g. providing a PCI email but specifying soc2) may yield misaligned evidence items
- Non-English email body may degrade extraction quality
- Payment failure or insufficient USDC balance prevents API access (x402 payment required)

## How this service works

Map compliance audit email requests to evidence items, owners, systems, and follow-up questions by framework.

## Output

A structured mapping of the compliance audit email to: specific evidence items that must be collected, the owners responsible for each item, the systems where evidence lives, and clarifying follow-up questions — all organized according to the specified compliance framework (SOC2, ISO 27001, HIPAA, PCI, or general).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string"
  },
  "subject": {
   "type": "string"
  },
  "framework": {
   "enum": [
    "soc2",
    "iso27001",
    "hipaa",
    "pci",
    "general"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/compliance-evidence-mapper-9c4a12fd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-hono-api.inraby.workers.dev](https://www.zero.xyz/host/x402-hono-api.inraby.workers.dev/llms.txt)