Product
One configured run over some or all rows of one uploaded file. Which workflow you choose depends on whether you want the answer, the evidence, or a cheap look first.
Workflows
The outcome path. Everything runs, and you get a file back.
Processes all applicable rows, attempts the cached TikTok Shop seller chain first, follows a non-generic seller website for contact details, falls back to keyword website lookup where needed, merges what it found, and downloads a CSV.
For judging coverage and investigating a bad match.
Runs the providers you select over the same rows and shows their normalized responses side by side, so you can see which source found what rather than reading one merged answer.
For spending nothing until you know it works.
The comparison flow limited to a single row. Combine it with a name filter or a row cap to sample a workbook before committing the whole thing to paid lookups.
What you upload
No domains, no identifiers, no pre-cleaning. The recognized name column is found for you.
What comes back
Depending on provider coverage and what the business publishes. No field is guaranteed to exist for any given prospect.
Matching discipline
Generic marketplace, aggregator, and social-root domains are rejected as a seller’s owned website. Returning a marketplace’s support address as your prospect’s contact is worse than returning nothing.
Name matching is designed to avoid taking the first loosely related seller result. A near-match is reported as a near-match rather than promoted to a match.
Provider results are cached and fallbacks run selectively, so a row that already resolved does not get re-billed and a paid provider does not run on every row by default.
Not included
AnyProspect ends at enrichment and export.