{
  "x402Version": 2,
  "service": {
    "name": "10x402",
    "description": "x402 conformance linting, sold per call over x402",
    "url": "https://10x402.com",
    "tags": [
      "x402",
      "lint",
      "conformance",
      "developer-tools"
    ],
    "contact": "support@10x402.com",
    "related": [
      {
        "name": "Parallax",
        "url": "https://parallax402.com",
        "relation": "sibling: settlement-graph analytics (evidence layer); 10x402 is the vetting layer"
      }
    ],
    "origin_marker": {
      "header": "x-origin-marker",
      "description": "Set by the origin on every response from this service, and reproduced by nothing on the path. A non-2xx from this host that does NOT carry this header was minted by an intermediary — a bot wall, a WAF, a cache or a CDN error page — and is not this service answering. The value is not a secret and nothing routes on it: presence is the whole signal."
    }
  },
  "resources": [
    {
      "url": "https://10x402.com/lint",
      "method": "POST",
      "description": "Find conformance blockers to x402 indexing and payment on a live endpoint",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "100000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "100000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.1",
          "amount_atomic": "100000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/lint/one",
      "method": "POST",
      "description": "Run ONE named check against a live endpoint",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "15000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "15000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.015",
          "amount_atomic": "15000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/presence",
      "method": "POST",
      "description": "Where a live x402 resource stands with the registries — Bazaar, x402scan, and on-chain",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "60000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "60000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.06",
          "amount_atomic": "60000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/monitor/verdict",
      "method": "POST",
      "description": "The latest stored reading for a host: three rating instruments plus what it answered when asked — dated, never live, and it says how old it is",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "5000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "5000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.005",
          "amount_atomic": "5000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/monitor/history",
      "method": "POST",
      "description": "Every day this wing has held for one host — instrument readings and probes",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "30000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "30000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.03",
          "amount_atomic": "30000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/monitor/receipt",
      "method": "POST",
      "description": "The dispute pack: the series, the contradiction stated, a SHA-256 digest and an attestation",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "120000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "120000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.12",
          "amount_atomic": "120000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/lint/envelope",
      "method": "POST",
      "description": "Check a captured x402 402 for indexing and payment blockers — no fetch",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "40000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "40000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.04",
          "amount_atomic": "40000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    },
    {
      "url": "https://10x402.com/lint/envelope/one",
      "method": "POST",
      "description": "Run ONE named check against a response you paste",
      "mimeType": "application/json",
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "4000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0x885E7BEF433eb78F5976b28A7c10739c98DB11E5"
        },
        {
          "scheme": "exact",
          "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
          "amount": "4000",
          "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
          "payTo": "6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP"
        }
      ],
      "billing_terms": {
        "billable_unit": {
          "unit": "one served report",
          "price_usd": "0.004",
          "amount_atomic": "4000",
          "metered": false,
          "note": "One served report. A single signed authorization buys exactly one response at the listed price; the amount settled is that whole price, and there is no partial, metered or per-check billing. Settlement is queued only after the report exists, and only for a payment the facilitator verified — a report served while the facilitator was unreachable settles nothing at all."
        },
        "hold": {
          "held": false,
          "note": "None. Verification is a read at the facilitator, so nothing is reserved, escrowed or held: the signed authorization moves no funds until it is submitted at settle, which runs after the response has already been sent. An authorization that never reaches settle simply goes unused."
        },
        "idempotency": {
          "key": "sha256(payment header, as presented)",
          "headers": [
            "PAYMENT-SIGNATURE",
            "X-PAYMENT"
          ],
          "idempotency_key_header": null,
          "replay": {
            "status": 402,
            "error": "payment_already_used"
          },
          "note": "There is no idempotency-key header. The key is the SHA-256 of the payment header exactly as presented — `X-PAYMENT` for x402 v1, `PAYMENT-SIGNATURE` for x402 v2, and PAYMENT-SIGNATURE is the one read when a request carries both — claimed single-use between verification and the work. A retry carrying the same authorization — concurrently, or an hour later — is answered 402 with invalidReason `payment_already_used` and the live terms attached; it runs no work, serves no second report and settles nothing. Sign a fresh authorization to buy another report."
        },
        "post_payment_error": {
          "settles": false,
          "on_4xx": "authorization released",
          "on_5xx": "authorization not released — sign a fresh one",
          "note": "Nothing is ever settled unless a report was served. Every 4xx after payment — an empty or malformed body, a missing or unknown field, an unknown check id, a refused or unreachable target — releases the single-use claim, so the very same authorization can be presented again. The one 5xx, a 503 raised when the store or the metering path is unavailable, also settles nothing, but does not release the claim: retry with a freshly signed authorization."
        },
        "refund": {
          "path": "none",
          "dispute": "none",
          "contact": "support@10x402.com",
          "note": "None. There is no refund, credit or dispute endpoint, and no reversal of a settled payment. The mechanism is non-charge rather than refund: an authorization for a report that was not served is never submitted, so no funds move. A settlement that fails after a report was served is recorded and not retried — the caller keeps the report. Anything else is support@10x402.com and a conversation, not a guaranteed remedy."
        }
      }
    }
  ],
  "free": [
    {
      "url": "https://10x402.com/check",
      "method": "GET",
      "description": "Start here: service info, the full check catalogue with sources, prices and grades. Free."
    }
  ],
  "human_delivered": [
    {
      "url": "https://10x402.com/audit",
      "price_usd": 50,
      "payment": "manual",
      "description": "Purchase-path audit, delivered by a person: one paid endpoint, its discovery chain and two agreed client environments; real-client reproduction, diagnosis, one budget-capped canary and one retest within seven days. $50 USDC upfront to the payTo the 402 advertises, then email support@10x402.com. Not an x402 route: no 402, no automated settlement, not discoverable."
    }
  ],
  "note": "The authoritative terms are in the 402 each resource answers with. This document is generated by the build and completed when it is served: every accepts entry carries the payTo the live 402 advertises for that same network, substituted from the running deployment rather than baked in, and the key is absent — never empty — on a deployment with no receiving address. Which rails are offered is a runtime fact too, so a second accepts entry for USDC on Solana appears here, after the Base one and at the same price, exactly when the 402 carries one. GET /check for the live catalogue."
}