# Livecheck > Live status of a specific product page, marketplace listing, or job posting, read from the page itself at call time. Wallet calls need no account. Builders: sign in with GitHub for 200 free checks, no wallet needed: https://livecheck.fly.dev/keys Verify routes are POST /v1/verify, POST /v1/verify/job, and POST /v1/verify/listing. The unpaid 402 offers both x402 (Base USDC) and MPP (Tempo USDC.e). Each charges exactly $0.01. MPP method is tempo/charge: USDC.e on Tempo (chain 4217). Stripe pays Tempo gas. With MPP (Tempo): Paid answers, including the checked link, are kept for 24 hours so retries are safe, then deleted. Check, watch, renew, chain top-up, and confirm stay x402 (Base USDC) only. A free starter key (GitHub sign-in, public profile, no email) can call POST /v1/verify, POST /v1/verify/job, and POST /v1/verify/listing: 200 free checks over 30 days, no wallet needed. Get one at https://livecheck.fly.dev/keys and send Authorization: Bearer lc_live_…. Answers paid with a starter key show "price_usd": 0, "paid_with": "free_credit", and credits_remaining. A real answer spends one check: live, closed, or unknown after the page was read, including a board found only after the fetch. Errors, timeouts, and a robots.txt "can't tell" (the page was never requested, e.g. LinkedIn) do not. A board URL (Greenhouse, Lever, or Ashby with no job id, a bare /careers or /jobs page, or a bare Workday site) is rejected free. When the 200 checks run out, call the same route without the key to pay with a wallet, or reply to get a top-up link. Confirm, Sentinel (/v1/check, /v1/watch), and the free /job page limits are unchanged. Wallet payments stay the same. ## When to use - Before recommending or buying a product: is this listing still available? - Before applying to a job: is this posting still open? - Before scraping or storing a URL: is it still live? - After search results (Google Shopping, job boards, scraped lists): which of these are stale? Livecheck is not a search engine. Bring one specific item URL. ## Endpoints - POST /v1/verify/job ($0.01) — is this specific job posting still open? body {"url", optional "stale_after_days" (default 60, 7–365)} → {status: live|closed|unknown, title, signals[], confidence, age} - POST /v1/verify/listing ($0.01) — is this product listing still available or sold out? body {"url"} → same response - POST /v1/verify ($0.01) — body {"url": "..."} → {status: live|closed|unknown, title, signals[], http_status, canonical_url, checked_at, confidence} - POST /v1/check ($0.02) — one-shot condition on a page: status_change, keyword, text_diff, numeric_threshold (e.g. price below X) - POST /v1/watch ($2.50) — 30-day watcher; signed HMAC webhook when the condition fires (HTTPS callback optional; omit it and pull GET /v1/watch/{id}/events with the owner token) - POST /v1/watch/renew ($2.50) — extend an active watcher; body {"id":"wtc_..."}; owner token required in addition to payment - POST /v1/confirm ($0.10) — did a lead/contact/application form submission land? intent: lead_submit | listing_published. Example input {"url":"https://livecheck.fly.dev/demo/thank-you?ref=ABC123","intent":"lead_submit"} returns confirmed: that page is HTTP 200 and prints Confirmation number ABC123. - POST /v1/confirm/order ($0.25) — does the order exist? intent: order_placed - GET /v1/receipt/{id} (free) — verify any signed receipt ## How to act on Verify - live → proceed - closed → drop it; tell the user it's no longer available - unknown → login wall, JavaScript-only page, or bot block; report as unknown, don't guess ## Limits - Reads HTML and HTTP status; does not run JavaScript - POST /v1/verify, /v1/verify/job, and /v1/verify/listing return 503 with Retry-After when the check queue is full, a queued check waited too long, or the x402 payment processor times out or errors before payment (over_capacity or processor_unavailable). On those 503s, wait for Retry-After and retry. You were not charged. An x402 503 with error payment_status_unknown means the payment took longer than 5 seconds to settle: Payment status unknown. Don't retry for 60 seconds. If you were charged and got no answer, we'll refund it. Retry-After is 60. An MPP 503 with error payment_unconfirmed means the payment could not be confirmed: a possible charge is logged for refund. Retry with the same credential, not a new payment. Do not treat 503 as closed or unknown. For a list of URLs, send up to 8 checks at a time. - POST /v1/verify and POST /v1/verify/job may also consult public job-board APIs for Ashby, Workday, Lever, and Greenhouse (no API key). A posting the API reports missing is closed. A posting the API lists is live when the page is live or a JavaScript-only shell (signal ats_api_listed). If the page looks closed and the API still lists it, the verdict is unknown. One exception: a Greenhouse gh_jid link whose company careers page answers a plain 404 while Greenhouse still lists that job id is live (signal gh_jid_company_page_not_found). A 410, closure copy, or a redirect that dropped the id still counts as closed. Timeouts and HTTP 5xx are not treated as closed. Bot-check pages are never bypassed (no Cloudflare or reCAPTCHA solving). The same rule applies on every job system: a bot check (challenge_page) on a Greenhouse, Lever, Ashby, or Workday posting, or a Greenhouse gh_jid company page, is answered from that system's public API for the job id (listed means live, missing follows the closed rule above), with challenge_page kept in signals. With no posting API (e.g. Workable), or when the API is unreachable, a bot check stays unknown. - Posting age (POST /v1/verify/job, and POST /v1/verify on job postings): age = {posted_at, age_days, age_source, age_precision, age_bucket (0-7, 8-30, 31-60, 61-90, 90+, 30+, unknown), stale_age, stale_after_days}. Sources: Greenhouse first_published or published_at, Ashby publishedAt, Lever createdAt, Workday startDate or the "Posted N Days Ago" text, else the page's JSON-LD datePosted. A last-updated date is never used as the posted date (it may appear as last_updated_at). stale_age is true when age_days >= stale_after_days (default 60, so from day 60 up). No posted date → age_source none, age_days null, stale_age null. A reposted job can look newer than it is, so the true age is at least age_days. Age is context only: it never changes status or confidence. Signal age_conflict means the page's JSON-LD date and the hiring platform's date differ by more than 2 days (the platform date is used). Live answers 30–59 days old carry a neutral age.note; from 60 days up, age.note says the role may already be in final interviews or filled. - LinkedIn isn't supported (its robots.txt blocks automated checks). Use the company's own job link. - Status means availability only, not legitimacy or fraud risk - Never logs in, submits forms, or changes anything on the target site ## Links - OpenAPI: https://livecheck.fly.dev/openapi.json - Stats: https://livecheck.fly.dev/stats (headline counts include internal test traffic; traffic.external omits configured team wallets) - Agent skill: https://github.com/moyecj-snap/livecheck-skills - Install for agentcash: npx agentcash@0.17.1 add https://livecheck.fly.dev