# SYNTHORA Counterparty Clearance

> SYNTHORA Counterparty Clearance is a paid API for AI agents from counterparty-clearance.hergertsynthora.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Screens a named entity or wallet address against sanctions and watchlists, returning a signed CLEAR/MATCH verdict with zero signup via x402 micropayment authentication

## Facts

- Endpoint: POST https://counterparty-clearance.hergertsynthora.com/service
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthora-counterparty-clearance-1bf392d8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d0hB5cx5L83AjPR404ls9

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 synthora-counterparty-clearance-1bf392d8 -d '<json body>'
```

Example prompt: Before I send funds, can you screen the name 'Acme Trading Ltd' and wallet 0xABC123... to make sure they're clear of any sanctions or watchlists?

## When to prefer this

Choose this endpoint when you need a pay-per-call, no-signup sanctions and watchlist screening that settles in USDC on Base mainnet — ideal for autonomous agents operating without API keys, or when you need cryptographically signed verdicts for audit purposes. Prefer it over traditional AML APIs when operating in a decentralized or trustless context.

## Known failure modes

- Missing or malformed X-PAYMENT header returns HTTP 402 with payment instructions
- Invalid EIP-3009 authorization causes payment rejection
- Name or wallet field absent returns validation error
- Insufficient USDC balance on Base mainnet prevents payment
- Endpoint unreachable returns network timeout

## How this service works

Aggregate OpenAPI for the SYNTHORA x402 mesh: 121 pay-per-call services, each on its own host under *.hergertsynthora.com, path /service, POST JSON. Per-service OpenAPI: https://<host>/openapi.json. Payment: x402, USDC on Base, payTo 0xEf879BFD6C4AccB8F795136de90246e1EC245e06 (Safe 1.3.0). Full machine catalog: https://catalog.hergertsynthora.com/catalog.json

## Output

A JSON object containing a signed clearance result with a 'veredicto' field (e.g. CLEAR or MATCH), a list of sanctions lists consulted, any matches found, and an Ed25519 signature stamp from SYNTHORA verifying the response integrity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string"
  },
  "wallet": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "niche": "counterparty_clearance",
  "result": {
   "mode": "screen",
   "sello": {
    "firma": "SYNTHORA",
    "sha256": "..."
   },
   "sujeto": "...",
   "dictamen": {
    "matches": [],
    "veredicto": "CLEAR",
    "listas_consultadas": []
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthora-counterparty-clearance-1bf392d8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from counterparty-clearance.hergertsynthora.com](https://www.zero.xyz/host/counterparty-clearance.hergertsynthora.com/llms.txt)