# CrossCheck Accept

> CrossCheck Accept is a paid API for AI agents from crosscheckapi.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-02).

Validates a deliverable returned by another AI agent against the original task requirements, returning an accept/reject verdict with a signed receipt binding task, deliverable, and payment hashes.

## Facts

- Endpoint: POST https://crosscheckapi.com/v1/accept?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/crosscheck-accept-129d4513
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vsh6HrSB9uVKoCbUIUCpo

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 crosscheck-accept-129d4513 -d '<json body>'
```

Example prompt: Before I release payment to that translation agent, run CrossCheck Accept on it — the task was 'translate this legal contract from English to Spanish preserving all formatting', and the deliverable is what came back. Bind it to payment tx 0x3f2a1b...c9d4 on Base.

## When to prefer this

Use CrossCheck Accept when your AI agent pipeline receives output from an untrusted or external agent and you need an objective, code-verified verdict before releasing escrow, payment, or passing work downstream. It is especially valuable when deliverables must satisfy structural constraints (JSON schema, item counts, numeric sums), when prompt injection is a concern, or when you need a signed, auditable receipt binding task and deliverable for compliance or dispute resolution. Prefer this over manual review or LLM self-evaluation when tamper-resistance and verifiability matter.

## Known failure modes

- Deliverable contains prompt injection or self-certification — automatically rejected regardless of content quality
- Payment transaction hash does not match on-chain data — receipt generation fails
- Task description is ambiguous or requirements cannot be parsed — may produce incomplete requirement judgments
- Deliverable does not satisfy counted or summed constraints (e.g. wrong number of items) — rejected with specific failing requirements listed
- Network unavailability or timeout from crosscheckapi.com — call fails with 5xx error
- Malformed payment_tx hash (not matching 0x[64 hex chars] pattern) — request rejected with validation error

## How this service works

Verify output and validate work another AI agent hands back, before you pay, release escrow, or pass it on. An acceptance test and quality check: send the task and the deliverable, get accept or reject with every requirement judged. Counts, required JSON fields, and sums are checked in code. Deliverables that certify themselves or inject instructions never pass. Signed receipt binding task, deliverable, and payment hashes. $0.03.

## Output

Returns an accept or reject verdict with each individual requirement from the task judged as pass or fail. Structural checks (required JSON fields, counts, numeric sums) are verified in code. Deliverables attempting self-certification or instruction injection automatically fail. On acceptance, a cryptographically signed receipt is returned binding the task hash, deliverable hash, and (if provided) payment transaction hash, suitable for audit or escrow release.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ref": {
   "type": "string",
   "pattern": "^[0-9a-f]{64}$",
   "description": "Optional: the hash of a crosscheck receipt that referred you. Its wallet earns check credits from your first 90 days of spend."
  },
  "task": {
   "type": "string",
   "minLength": 1,
   "description": "The task you gave the other agent or service, including every requirement"
  },
  "reference": {
   "type": "string",
   "maxLength": 200,
   "description": "Optional order id or transaction hash to record on the receipt"
  },
  "payment_tx": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "Optional: the transaction you paid the other agent with; verified on-chain and bound to the receipt"
  },
  "deliverable": {
   "type": "string",
   "minLength": 1,
   "description": "What came back, exactly as received"
  },
  "payment_network": {
   "type": "string",
   "description": "CAIP-2 network of payment_tx, default eip155:8453"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "job_id": "chk_8d0c3f1e2b7a4c5d9e6f0a1b2c3d4e5f",
  "status": "done",
  "receipt": {
   "sig": "...",
   "body": {
    "seq": 2,
    "kind": "accept"
   },
   "hash": "..."
  },
  "verdict": {
   "accept": false,
   "summary": "Rejected: 1 of 3 requirements not met. First: List 5 competitors (partly).",
   "requirements": [
    {
     "met": "partly",
     "blocking": true,
     "evidence": "The array has 3 entries, not 5.",
     "subjective": false,
     "requirement": "List 5 competitors of Acme Robotics"
    },
    {
     "met": "yes",
     "blocking": false,
     "evidence": "Every entry has hq and founded.",
     "subjective": false,
     "requirement": "Each with headquarters city and founding year"
    },
    {
     "met": "yes",
     "blocking": false,
     "evidence": "The deliverable is a valid JSON array.",
     "subjective": false,
     "requirement": "As a JSON array"
    }
   ],
   "injection_suspected": false
  },
  "result_url": "https://crosscheckapi.com/v1/checks/chk_8d0c3f1e2b7a4c5d9e6f0a1b2c3d4e5f",
  "result_token": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/crosscheck-accept-129d4513/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from crosscheckapi.com](https://www.zero.xyz/host/crosscheckapi.com/llms.txt)