One price. One company.

You get outcome `board_not_found`, and you are not charged. It is a first-class answer, deliberately distinct from “no open roles”, because collapsing those two would be the most damaging thing this product could do — a sales team acting on a fabricated zero is worse off than one with no data. Discovery finds about half of companies from their careers page alone and about four in five once we also guess the board name from the domain. It is never 100%.

Because those three are the only ones that answer honestly. Each returns 200 for a real board and a clean 404 for a token that does not exist, which is the single property that lets us tell “not on this platform” apart from “not hiring”. SmartRecruiters, Workable, Recruitee, Workday were all tested and dropped — SmartRecruiters is the sharpest case: a nonsense company id returns HTTP 200 with totalFound:0, byte-identical to a real company with nothing open.

The one with the most roles — never the one that answered first. Airtable and Mercury both return 200 on Greenhouse and on Ashby; their Ashby boards are empty shells while the real 16 and 55 roles sit on Greenhouse. A first-match design would report zero for both companies, confidently. So we probe all three in parallel and pick the fullest board, and every candidate we ruled out comes back in the response.

Because a single snapshot is just a careers page you could have read yourself. What tells you something is the second derivative: a function that did not exist last month, a team that doubled, a req that was quietly pulled. Every scan writes a snapshot of that board, so the next scan of the same company returns opened, closed, netChange and newFunctions. The first scan of a board has no delta — and we say so rather than printing zeros.

Because Greenhouse does not publish a remote flag — its location is free text like “Remote - US” or “San Francisco, CA • New York, NY”. Lever and Ashby do publish a real flag, so their roles carry true or false. We could parse the Greenhouse string and be right most of the time, but “most of the time” is not a field you can filter on, so we return null and tell you which platform you are reading. A uniform remote filter across all three is not possible and we do not pretend otherwise.

On Ashby only, and only when you ask for role descriptions. Greenhouse and Lever publish no compensation at all. Some Ashby boards return the compensation object with every field null, so the key’s presence is not data — in that case we return null rather than an empty shell that reads like a measurement. Every scan carries a capabilities block saying exactly which fields that platform can populate.

6 Ounie credits — $0.06 in plain money, from the same wallet as every other Ounie app. Role descriptions add 1 credit per role, and only when you ask for them. No subscription, no minimum. Re-reading and listing scans you have already paid for is free forever.

Yes, and that is one of the most valuable readings here. An active board with nothing on it means the freeze is real, and knowing that is worth six credits. What is never charged is a scan where we could not reach a board at all — that taught you nothing, so it refunds in full.

Yes. The x402 endpoint takes USDC on Base with no account and no key. Because the job boards are free for us to read, discovery runs before the quote: if there is no reachable board you get a 400 with no price in it, so you never sign a payment for work that cannot be delivered. And the 402 carries the exact final amount, including descriptions, rather than a ceiling.

No. All three platforms publish a documented public JSON job-board API and we read those, keylessly, with an identifying user agent. We also fetch a company’s own careers page to find which board they use — the same request a browser makes. There is no Apify actor, no headless browser and no login anywhere in this product.