From the blog · Page 17
How we build, what we learn, what we ship.
Posts about indexing public job postings at scale, salary parsing, and the systems that keep one universal JSON schema feeling small even as the source list keeps growing.
The four Indeed partner APIs, explained
Indeed doesn't ship one API - it ships four, and all of them publish data into Indeed rather than reading it out. Job Sync, Indeed Apply, Disposition Sync, and Sponsored Jobs: what each does, who it's for, how to get access, and the one goal none of them serves.
Indeed API pricing: what it costs, and what's actually free
Indeed's official APIs are free to use and closed to most companies, the enterprise data program has no published price, and the unofficial providers meter you per result. What each path actually costs, why freshness drives the bill more than any per-call rate, and the line items that never make it into a quote.
Indeed API key: why there isn't one, and what to use instead
The Indeed publisher key stopped working in 2023 and was never replaced with a self-serve equivalent. How to recognise the tutorials that predate the shutdown, what credentials Indeed issues today and to whom, and the working path if your goal is reading Indeed job postings.
Unified API platforms: the two kinds, and which one job data needs
The unified API category contains two products that get confused constantly - one reads your customer's systems with their credentials, the other reads public data nobody has to authorize. They solve different problems, fail in different ways, and only one of them can answer 'who is hiring right now'. Which platforms sit where, and how to tell which you actually need.
Job aggregator sites: where each one actually gets its listings
Every aggregator looks the same from the outside and sources its listings completely differently underneath - XML feeds, ATS APIs, scraping, or paid inclusion. Which mechanism each major aggregator uses, why that decides freshness and coverage, and what it means if you are pulling listings programmatically rather than browsing them.
The best MCP servers for real data in 2026
Most MCP server lists are directories of everything. This one covers the servers that give an agent access to data it can't otherwise reach - live web, code, databases, search, filesystems, and job postings - with the honest limits of each. What separates a useful data MCP server from a thin API wrapper, and how to evaluate one before you plug it into an agent.
Build an AI job search agent that actually finds jobs
An agent that searches jobs is three parts: a live postings source, a tool the model can call, and a loop that refines the query when results come back thin. Working code for Claude, the OpenAI Agents SDK, and LangChain - plus the four failure modes that make most job agents useless (stale listings, hallucinated companies, dead apply links, and a model that never widens its filters).
AI web scraping in 2026: what LLM scrapers actually fix
LLM-based scrapers solve exactly one problem - turning messy HTML into structured fields without a hand-written selector. They do not solve blocking, JavaScript rendering, rate limits, pagination, or freshness, which is where scraping projects actually die. An honest breakdown of AI scraping tools, what each one costs per page, and when the extraction layer is the wrong thing to be optimizing.
How AI job matching actually works: filters, embeddings, rerank
AI job matching is not one model. It's a three-stage pipeline - hard filters that cut the corpus, vector recall that finds semantic near-misses keyword search drops, and a cross-encoder or LLM rerank on the shortlist. What each stage costs, why the order matters, and why the whole thing collapses if your posting corpus is stale. With working code for the retrieval half.