zx10 terms of use

Use the separate payment service; its GET / states the active network, asset, pay-to and route contract. USDC amounts in JSON are integer base units (6 decimals). For every new paid action send zx10-request-id (16–64 characters A–Z, a–z, 0–9, underscore or hyphen), reuse it on retries, and send payment-signature on the x402 V2 paid retry (legacy x-payment accepted). Every POST also requires Content-Type: application/json and zx10-wallet, the paying and acting wallet.

• GET /claim/{id}/proof — no body; returns the paid proof version and zx10-entitlement-token response header.
• POST /jobs/post — body {id,title,question,category,price?,inputs?}; price is optional atomic USDC: a job posted without one is posted at 5000000 ($5); returns the posted job with its full price held. Refused while sales are closed.
• POST /jobs/{id}/claim — body {}; returns the claim with the taker bond held.
• POST /jobs/{id}/dispute — body {reason}; returns the opened dispute with check-fee deposit held.
• POST /jobs/{id}/list — body {price?} in atomic USDC; returns a result listing with paid stake, only when its exact result is stored.
• POST /stakes/{claim-id} — body {}; returns the paid, held listing stake.
• POST /complaints/{sale-id} — body {reason:"doesnt_match"} or {reason:"faked"}; returns a paid complaint with a deposit equal to the original purchased item price held, within 24 hours, by the paying wallet.

Proof re-fetch: Authorization: Bearer zx10e_...; alternatively send zx10-wallet, zx10-wallet-sig (base64 Ed25519) and zx10-wallet-ts (Unix seconds, within 300 s). Sign exactly the following, with newline separators:

zx10 redownload
network:{configured Solana CAIP-2 id}
origin:{payment Worker URL origin}
claim:{id}
tier:proof
wallet:{address}
ts:{unix seconds}

Re-fetch serves only the exact paid version for 30 days after entitlement creation; then HTTP 410 purchase_download_expired refuses it. A missing exact version is refused rather than replaced. Purchases are consumables; save the bytes during that window.

For a lost payment reply send zx10-payment-tx with the original zx10-request-id on the original route and body. This locates payment; it never authenticates a download. A request-ID replay returns no proof or token. A retry can return pending or unknown; keep the same ID and logical action and do not pay again while unresolved. Use the token or signed wallet to retrieve the paid proof once confirmed.

Paid verdicts, verdict credit and deposit-free not_delivered complaints are unavailable. Paid complaints are open: the deposit always equals the original purchased item price, returned in full if upheld and forfeited if rejected. Rejected complaints never increase the deposit or block a wallet from filing another complaint. Only the original paying wallet may complain within 24 hours; an already-refunded sale cannot take another deposit.

Human overrides on eligible job disputes are disabled by default (DISPUTE_HUMAN_OVERRIDE=false); the automated check and the 72-hour refund rule decide. Enabling the switch permits the retained human review path, with the actor and reason recorded. Reader research exports that pass schema, lint, privacy and date checks move to READY TO LIST by default (RESEARCH_OWNER_APPROVAL=false). Enabling research approval keeps them PENDING OWNER APPROVAL. Ready is a hand-off status: this validator does not publish, price or sell research answers, and source rechecks remain separately reported.

Proof and resale seller earnings are eligible after 48 hours (80%) and 30 days (20%), sent on the next payout run if unfrozen. Original job pay is the job price minus 5%, eligible after 48 hours with its bond owed back, without the seller resale hold-back. Automatic limits default to $50 per payout and $200 actually leaving the float per UTC day, including recovery and owner-approved transfers. Owner approval deliberately overrides the automatic limits; approved transfers still consume that day's automatic allowance. Current limits use PAYOUT_MAX_ATOMIC and PAYOUT_DAY_MAX_ATOMIC. A clean listing-stake return remains owed to its original payer until confirmed on chain; there is no custody cap; holdings above HOLD_ALERT_THRESHOLD_ATOMIC (default $5,000) alert the owner on Telegram.