Check restriction evidence API

Compare supplied evidence with the evidence kinds the caller marks as required, and with the restrictions in the export. A missing document is not invented, and a restriction is not lifted.

The Check restriction evidence operation is part of the Marketplace Account Health API on BRAINIAC.software. Compare supplied evidence with the evidence kinds the caller marks as required, and with the restrictions in the export. A missing document is not invented, and a restriction is not lifted. It is exposed as POST /api/v1/marketplace-health/account-restriction-evidence-check and priced at $0.05 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Notices, metrics, and policies supplied in the request. Limitations: Records are copied only from labeled fields in the request. A notice is matched only to policy text supplied in the request. A draft does not predict an appeal result or a payout release. No seller account is accessed and no marketplace is contacted. A missing field means it was not in the supplied documents. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Extract marketplace notices, Analyze seller performance metrics, Diagnose a stated payout hold, Classify a notice against supplied policies. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.05 USDC
/api/v1/marketplace-health/account-restriction-evidence-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/marketplace-health/account-restriction-evidence-check" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "restrictions": [
    {
      "id": "X-1",
      "noticeId": "N-100",
      "kind": "listing",
      "since": "2026-11-01",
      "detail": "listing mismatch"
    }
  ],
  "requirements": [
    {
      "name": "invoices"
    }
  ],
  "evidence": [
    {
      "id": "E-1",
      "noticeId": "N-100",
      "kind": "photos",
      "date": "2026-11-02",
      "text": "product photos"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Marketplace Account Health APIFull docsHow it works