Agents can act. Without knowing who's who, they act blind.

The case for an enrichment primitive · by the LeadShark team

Every useful go-to-market motion starts with the same question: who is this person? A name and a profile link aren't an answer. The answer is structure — current role, company, location, and, when the moment calls for it, a verified way to reach them. Humans build that picture by clicking around for five minutes. Agents can't click around. They need the answer as data, in one call.

The problem with how enrichment works today

Most enrichment either rides on your own account — burning the daily quota and the standing of the exact account you operate your business from — or hides behind all-you-can-eat pricing that quietly charges you for dead ends. Both models punish the wrong thing. Your account shouldn't take risk for a lookup, and a miss shouldn't cost the same as a find.

What a primitive should look like

Accountless. The lookup runs on our side. No session, no cookies, nothing riding on the account you actually use. Enrichment is read-infrastructure — it should never touch the thing you can't afford to lose.

Priced per verified find. A profile costs one credit — about a cent. A verified work email costs ten. A miss costs zero, at every tier. When the meter only runs on results, the incentives finally point the right way: we get paid for answers, not attempts.

Cached honestly. The same person asked twice shouldn't bill twice. Repeat lookups return instantly and cost less — and every response tells you where it came from: source, fetched_at, stale_after. No mystery freshness.

Agent-native. The same primitive ships two ways: an API for your stack, and an MCP endpoint so enrich() becomes a tool your assistant calls mid-conversation. You shouldn't need glue code for your agent to know who's who.

Proven inside first

Person Enrich isn't a demo looking for a use case. It's the enrichment layer behind Apex — the governed LinkedIn MCP — where Loadouts like Doorman, Scout, Connector, and Closer lean on it to qualify inbound, rank prospects, and pick up conversations with context. Apex is customer number one; the primitive earns its coverage on real traffic before it asks for yours.

The LeadShark family, in one line each

LeadShark captures demand. Apex acts on it — governed, approval-gated, logged. Person Enrich knows who's who, so both of them (and your own agents) act with eyes open.