# Synthex Forge Compliance Check

> Synthex Forge Compliance Check is a paid API for AI agents from x402.synthexforge.com, paid per call via x402, $1/call, status unknown (last checked 2026-10-23).

Performs a paid AI/data governance compliance check against a named entity, returning a signed verification attestation for the described use case.

## Facts

- Endpoint: POST https://x402.synthexforge.com/v1/compliance/check?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthex-forge-compliance-check-66dbf066
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UDbUC671w3rG6zjlOu9zF

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 synthex-forge-compliance-check-66dbf066 -d '<json body>'
```

Example prompt: Run a compliance check on our AI analytics provider 'DataVault Inc' — we're in the financial services sector, our purpose is credit risk modeling, the category is AI/ML, users are internal risk analysts, and the data types involved are transaction records and credit scores.

## When to prefer this

Choose this endpoint when you need a cryptographically signed compliance attestation (Ed25519 + SHA-256) for AI, data, or software governance purposes — especially in regulated sectors like fintech or healthcare. Prefer it over generic compliance checkers when you need a payment-gated, immutable audit record on Base mainnet rather than a simple rules-based flag.

## Known failure modes

- HTTP 402 returned if USDC payment on Base mainnet (chain ID 8453) is not provided or fails — no result returned until payment is settled
- Missing required fields (name, sector, purpose) may result in a 400 bad request or incomplete attestation
- Invalid or unsupported sector/category combinations may return a negative compliance result
- Payment transaction not yet confirmed on-chain may cause a timeout or pending state
- Network or service downtime may result in a 503 error with no attestation issued

## How this service works

Synthex Forge x402 Receive: 41 paid verification, attestation and governance endpoints (Ed25519 + SHA-256 signed artifacts) plus free verify/public-key/standard sibling routes. Paid routes answer HTTP 402 with an x402 v2 `payment-required` envelope (atomic USDC on Base mainnet, chain ID 8453). Free routes are declared with `security: []` per the x402scan discovery spec.

## Output

Returns a JSON object with an 'ok' boolean status indicating whether the compliance check passed, potentially accompanied by Ed25519 and SHA-256 signed attestation artifacts confirming the verification result for audit and governance records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string"
  },
  "users": {
   "type": "string"
  },
  "sector": {
   "type": "string"
  },
  "purpose": {
   "type": "string"
  },
  "category": {
   "type": "string"
  },
  "provider": {
   "type": "string"
  },
  "data_types": {
   "type": "string"
  },
  "description": {
   "type": "string"
  },
  "custom_details": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthex-forge-compliance-check-66dbf066/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.synthexforge.com](https://www.zero.xyz/host/x402.synthexforge.com/llms.txt)