2026ShippedTools
Zhilian Client
zhilian-client
Recruiting signals in, structured company leads out.
- Role
- Design & development, solo
- Year
- 2026
- Status
- Shipped
- Stack
- TypeScriptMCPOpenAPISQLite
Recruiting data only gets you halfway. A list of job postings tells you a company is hiring, but not whether the company is real, how big it is, or who runs it. The useful chain is: keyword plus city → jobs → deduplicated companies → business-registration data → all open jobs at that company.
The problem
Doing that chain in a browser is manual data entry. Doing it with scripts requires a session that does not break. Zhaopin splits login across two domains, puts data in page SSR and internal APIs, and guards requests with EdgeOne’s human verification.
What I built
zhilian-client is the second read-only client in the family, and I deliberately copied the architecture of boss-client: one owner process holds the browser and a SQLite cache; CLI, REST and MCP are clients calling the local REST API; OpenAPI, MCP tools and CLI commands are generated from one operation definition.
17 operations cover the full chain: search, paginate by queryId, job detail, deduplicated company list, company detail including registration data, all open jobs at a company, a city registry, cache stats and clearing.
Architecture notes
- Cache: structured fields only — no HTML, cookies or captcha artifacts. Lists default to two hours, details to seven days, with a forced refresh option.
- Login: QR or SMS once; access lasts about seven days and refresh about thirty, renewing automatically.
- Anti-bot: EdgeOne verification is handled by a relay — automatic click, or a screenshot with coordinates handed to a human or agent.
- Full retrieval: a company’s “all jobs” is paginated upstream and easy to truncate. This client actually fetches all of them (21/21 in a real test).
What I learned
The second implementation is what really tests a design. The first client had already drawn the seams — session, adapter layer, cache, contract generation — so swapping the upstream, the pagination and the anti-bot story never touched the architecture. 35 unit tests, 17 MCP tools and 461 cities all grew on that frame.
Read-only and minimal collection are not just compliance notes. They make the tool boring enough to run unattended.