Founding beta for agent-native enrichment

Turn a prospect signal into a
verified contact.

Resolve people and companies from LinkedIn URLs, emails, names, and IPs through REST or MCP. Founding members get capped beta access now and lock in unlimited database lookups at GA.

join founding beta explore the tools
validated < 30 daysREST + MCPmisses cost zero
live resolution
Request
POST /v1/tools/linkedin_to_best_email
1Cache
2Verify
✓Resolve
Matched person

Avery Lin

Resolved
Best email
avery@northstar.dev
Type
business
Validated
8 days ago
Confidence
98.4%
Company
Northstar Labs
Tokens
0 · cache hit
api.fetchset.dev 184 ms · status 200
One resolution layer for the tools your GTM stack already speaks.
REST
MCP
Clay
Claude
Codex

Why FetchSet

Useful data, without the guesswork.

A clear contract for every lookup: what was found, how fresh it is, how confident we are, and what it cost.

01 / Fresh

Validated before return

Emails carry a recent validation date and risk status. Stale records are rechecked before they enter your workflow.

02 / Fair

Only pay for a hit

An empty result is always a zero-token result. Expensive external lookups are bounded, explicit, and charged only on success.

03 / Native

Built to be called

Use the same resolution tools through REST, MCP, Clay, or your own agent. No dashboard choreography required.

The resolution surface

One identifier in. A useful record out.

Start with the signal you already have.

this example resolves from cache · 0 external tokens

Response / 200 OKVerified
AL

Avery Lin

VP Revenue Operations · Northstar Labs

best_email"avery@northstar.dev"email_type"business"risk"valid"validated_at"2026-07-09"tokens_charged0confidence0.984

How it works

From partial signal to verified answer.

The resolution engine takes the shortest reliable path and leaves the billing logic visible.

01 / Signal

Normalize the input

Clean and validate the email, URL, name, hash, or IP before a lookup begins.

02 / Cache

Check what we know

Fresh cached records return quickly and use no external tokens.

03 / Waterfall

Find the best hit

On a miss, approved providers are queried in order and stop at the first verified result.

04 / Return

Deliver with context

Receive the record, validation, confidence, provenance class, and exact token charge.

Pricing

Start small. Keep the useful part unlimited.

Beta access is capped. Founding members lock in unlimited database lookups at GA.
External-token allowances remain visible on every plan.

Explore

Free

$0
  • 1,000 lifetime internal credits
  • 100 lifetime external tokens
  • REST and MCP access
  • Charge on success
join founding beta
Most useful

Starter

$27 / month
  • Unlimited database lookups at GA
  • 100 external tokens monthly
  • 1,000 results per day
  • Email freshness guarantee
join founding beta
Scale workflows

Growth

$97 / month
  • Unlimited database lookups at GA
  • 500 external tokens monthly
  • 15,000 results per day
  • Higher agent throughput
join founding beta
Planning for more external lookups? Planned top-ups begin at $5. Final availability and terms will be confirmed before GA. see token costs

Trust is a product feature

Contact data should arrive with context, controls, and a clear cost.

Provenance carried forward

Persisted records retain source, acquisition date, and redistribution basis.

Suppression checked first

Suppressed subjects return no personal data, including on cache hits.

Freshness made visible

Validation date and deliverability risk travel with every returned email.

Billing you can audit

Every response reports what was charged. A miss always charges zero.

FAQ

Before your first call.

The short version of what builders usually ask.

A cache-miss email find or real-time mobile lookup uses external providers and consumes external tokens only when a verified result is found. Fresh cache hits do not.

No. Charge-on-success is enforced at the billing layer. Processed requests with an empty result report tokens_charged: 0.

Each returned email includes a recent validation date and deliverability risk. Records older than the freshness window are revalidated or withheld.

Yes. The same resolution surface is exposed through REST and MCP, so agents can call it inside Claude, Codex, Clay, or a custom workflow.

The planned launch surface covers business and personal email, mobile, person and company search, reverse lookup, email–LinkedIn resolution, and IP-to-company. Availability may roll out in phases.

Give your agent a better next step.

join founding beta read the docs