Join the founding beta
Tell us who owns the workflow, what FetchSet should resolve, and the expected lookup volume.
How FetchSet works
One signal in. A useful record out.
Resolve business identities inside Clay, Claude, Codex, or your own agent workflow. Every result carries the evidence and cost needed for the next decision.
REST + MCPfreshness visible0 tokens on missesbuilt for agents
Get started
From application to first record in three moves.
No dashboard choreography. Apply for access, confirm the right cost boundary, and call FetchSet from the place where the work already happens.
Start with guided access
Clear-fit workflows receive a direct invite. Custom or high-volume workflows begin with a short founder conversation.
Call it from your workflow
Connect through REST, MCP, Clay, Claude, Codex, or an internal agent. The response contract remains the same.
The data path
Start with what you know. Resolve only what you need.
FetchSet keeps the lookup path narrow and the returned record explainable.
Known signal
- Email address
- LinkedIn URL
- Name + company
- Company domain or IP
FetchSetresolution surface
- 01
Normalize
Clean and validate the identifier.
- 02
Check policy
Suppression, freshness, and cost boundaries.
- 03
Resolve
Fresh cache first; verified waterfall when needed.
- 04
Return
Value, evidence, provenance, and charge.
Useful record
- Clay or your waterfall
- Claude or Codex
- CRM and data warehouse
- Your own agent or product
Inside one lookup
The fast path stays fast. The expensive path stays visible.
A fresh licensed cache record can return without an external provider call. When a record is missing or stale, FetchSet enters a bounded waterfall and stops at the first result that meets validation policy.
read the resolution contract →POST /v1/tools/linkedin_to_best_email200 · 184 ms
1
Input acceptedlinkedin.com/in/avery-lin
2
Fresh cache hitvalidated 8 days ago
✓
Record returnedexternal tokens: 0
avery@northstar.devValid · 98.4% confidence · fresh cache
tokens_charged: 0 Popular workflows
Small primitives that compose into real work.
Add a verified business-email step to a Clay waterfall
view workflows →Resolve people while Claude or Codex builds an account list
view prospecting →Turn LinkedIn URLs into records without losing misses
view the starter skill →Map an email address back to the right business profile
view resolution →Find the right contacts at a list of target companies
view prospecting →Recheck stale CRM records before they enter a sequence
view data quality →Why FetchSet
Trust belongs in the response.
FetchSet is designed as inspectable data infrastructure, not a black box that returns a field and hides the decision.
Freshness is a date
Validation time travels with the email, so each workflow can apply its own policy.
A miss costs zero
Empty, suppressed, or not-found responses report an explicit zero token charge.
Every hit is explainable
Risk, confidence, provenance class, and cost remain attached to the returned record.