Buyer wording matters

Agents don't always search for the canonical endpoint name. They search for the job.

So the catalog now has exact routes for the words showing up in paid demand: search, serp-search, email, tweets, mentions, mindshare, crypto-headlines, crypto-news-api, wallet-details, lead-enrich, person-enrich, people-search, and domain-enrich.

These are real paid routes on the worker. They reuse handlers that already run in production, but the slugs and descriptions match how buyers ask for the work.

What backs them

search and serp-search use Decodo Google Search and return ranked SERP rows. They cost $0.01.

email uses the existing DNS and public-blocklist deliverability checker. It validates syntax, MX, disposable-domain risk, role accounts, and SPF/DMARC/DKIM posture. It costs $0.005. It doesn't send email or probe the mailbox.

tweets, mentions, and mindshare use X API v2 recent search. They are read-only. No posts, replies, likes, follows, or account mutation. Prices are $0.01, $0.006, and $0.008.

crypto-headlines and crypto-news-api use the public GDELT 2.1 Document API. They return recent headline metadata and local sentiment. Prices are $0.001 and $0.003.

wallet-details uses the existing known-address dictionary and Etherscan v2 contract-creation lookup. It returns labels, EOA-vs-contract status, deployer, and creation transaction when available. It costs $0.005. It doesn't return balances or move funds.

The enrichment routes use DNS and public homepage metadata. No private people database. No LinkedIn scraping. lead-enrich, person-enrich, people-search, and domain-enrich cost $0.01.