NomiCheck pricing
Every price with its why. This page is generated from the same constant the paywall charges with: it cannot state one price and charge another. The machine version is https://nomicheck.ynt.codes/api/batch/pricing (JSON, nomicheck-pricing/v2).
The rule that orders the whole table: The price is the same with one finding or with twenty. We NEVER charge based on what we find: the pre-check tells you for free whether there is anything, and the report costs the same either way.
Validation is never charged: A malformed body is rejected with 400 BEFORE the payment settles. In x402 the payment is final, so charging for a client's typo would be keeping money for an error that never even cost us compute.
How payment works
x402: the endpoint answers 402 with the exact requirements, the client signs an EIP-3009 authorization and retries with the X-PAYMENT header. No account, no API key, no sign-up. The payment is immediate and final. Currency: USDC. Networks: base and avalanche.
What is free, and why
/api/batch/verificar/prechequeo— free — THE PROMISE THIS SERVICE CANNOT BREAK: if your payslip is clean, you find out for free and never pay. It runs the same engine as the report and says how many payslips carry something and how much it weighs — never which line or which norm. Charging to discover whether there is a problem would make the verifier someone interested in there being one./api/batch/health— free — A monitor cannot pay to find out whether the service is alive. And it is the answer most needed exactly when something is wrong./api/batch/pricing— free — Charging for the price list would make finding out what something costs cost something./api/batch/quickstart— free — It is the door: what this is, what is free, how payment works and what it does NOT do. Nobody walks through a door with a toll./api/batch/openapi.json— free — The contract is the manual, not the product. An API whose documentation costs money gets integrated by no one./api/batch/schema/v1.json— free — Same rule as the OpenAPI: the input contract is the manual, and a manual behind a toll gets read by no one./api/batch/ejemplo— free — A real input with its exact output, so a client can test itself against something before spending. Without this, the first purchase is blind./api/batch/publickey— free — The key that verifies EVERYTHING we emit. Charging for it would be charging for the ability to audit us, which is exactly the opposite of what this service claims to be./api/batch/parametros— free — The statutory values in force are public: the State publishes them, not us. Charging to repeat them would be charging for someone else's data.
What is paid, and why it costs what it costs
/api/batch/liquidar(POST) — 0.02 USDC per call — Full payroll settlement per batch. It charges for compute, not for findings./api/batch/retencion(POST) — 0.02 USDC per call — Withholding tax (retención en la fuente): the statutory base adjustment, bracket table and UVT in force, per employee./api/batch/verificar(POST) — 0.02 USDC per call — It independently recomputes every statutory line of the payslip and checks it against the norm that governs it. That is the work, and that is what is charged — at a flat price: NEVER based on what we find. A verifier that earns more when it finds more is not a verifier, it is someone with an incentive./api/batch/pago-onchain(POST) — 0.02 USDC per call — Converts COP amounts to USDC at a frozen rate and builds a non-custodial payout batch the payer signs; the server never signs or moves funds. It charges for compute, not custody./api/batch/comprobante(POST) — 0.05 USDC per call — Payment receipt: cross-checks the settlement, the frozen FX snapshot and the on-chain transfer. It costs more than the rest because it crosses three layers and makes an RPC call to the chain — the price follows the real cost, not what the data is worth to the caller.