Two names from the strategy doc, now live

MARKET_STRATEGY.md names four flagship offers built around what a buyer segment actually needs, not around which endpoint happened to ship first. Today the first two go from plan to priced product: company-intel-pack for B2B enrichment agents, wallet-intel-pack for wallet and crypto agents.

Both are composites. Same pattern as company-dossier and wallet-dossier: constituents run in-process, in parallel, no HTTP hop between them and no double-billing. One 402, one settlement, one response.

company-intel-pack ($0.08)

A B2B agent doing account research on a company shouldn't have to call seven endpoints and stitch the JSON itself. So this pack runs company-enrich, domain-enrich, whois, ssl-cert-info, tech-stack-detect, dmarc-check, and news-search behind one call, and hands back {profile, domain, registration, security, tech_stack, email_auth, news}.

Give it a domain or a bare company name. Bare names go through the same two-phase resolver as company-dossier: guess a domain, probe it with company-enrich, and only fan out to the rest once MX records or a live homepage confirm the guess. An unresolvable name comes back with just the profile section and the rest marked skipped, not an error.

Two of the seven legs (tech-stack-detect, news-search) are optional. A slow GDELT news query degrades that one field instead of taking down the whole response.

Buy the seven lookups separately and they add up to $0.105. The pack is $0.08.

wallet-intel-pack ($0.08)

Point this at any EVM address and it labels it first: known exchange, router, contract, or plain wallet. That label decides what runs next.

Every address gets label, ens, balance (USDC on Base by default), pnl, and gas in parallel. Five constituents, one call. If the label comes back is_contract: true, three more legs kick in alongside those five: token-risk, token-honeypot, and lp-lock-check, merged into contract_risk. A plain EOA gets contract_risk: null and none of those three ever run. No reason to pay upstream for a risk check on an address that isn't a contract.

Base or Ethereum, both EVM. Solana wallets aren't part of this pack.

Why these two first

Both packs turn constituents the catalog already ships into one workflow at one price, and both map straight to a buyer segment the strategy doc already named. No new upstream integrations, no new failure modes to debug from scratch, just a call an agent would otherwise have to assemble by hand.

Registry, cluster map, Bankr manifest, and MCP package output all carry both slugs. Catalog search and automated probes see the same two endpoints a human does.