Built for the AI agent doing the searching.

The wedge

Every other web3 job board is a list of links. The same Greenhouse and Lever feeds, re-skinned. We started there too — but the opening isn't another aggregator. It's being the source an AI agent chooses when someone asks it "what AI × crypto founding engineer roles exist this week?"

That means we are not optimizing for SEO traffic against Web3.career. We are optimizing for being the cleanest, deepest, most-citeable index at the intersection of AI and crypto engineering. A different game.

What that looks like

• MCP server (built-in). Connect Claude, Cursor, or any MCP-compatible agent to /mcp — your agent searches our database with two tools, no scraping.
• llms.txt + per-role markdown. Every job is fetchable as plain markdown at /llms/<slug>.md. No HTML parsing.
• JSON-LD on every job. schema.org JobPosting, pre-computed. Google JobSearch and any downstream parser get the same canonical view as your eyes do.
• AI matching by GitHub or CV. Drop a GitHub profile or resume — we extract your skill graph and rank roles by actual fit.
• Salary-transparent, no exceptions. Min and max in USD. "Competitive" is a refusal to quote, not a number.

Who's building this

A solo founder who also runs an AEO (Answer Engine Optimization) SaaS. ChainWork is partly the personal dogfood for that work — every architectural choice (MCP, llms.txt, JSON-LD, structured everything) is a live experiment in how to be cited by ChatGPT, Claude, Perplexity, and Gemini.

That's the operator's edge here: the person designing the agent-native surface ships AI-search optimization as a day job.

Today's scope

We ingest from Greenhouse, Lever, and Ashby across dozens of crypto and AI-adjacent companies, growing daily. Engineering only — Sales / Marketing / Ops / Design / PM are filtered out at ingest. The AI × crypto wedge sharpens over time; broader web3 engineering is welcome today.

Hiring at one of these companies and not seeing your roles? Post one or email us to add your ATS slug.