Become a sample partner
Flashpoint.AI buys sample on behalf of research teams running studies across consumer, B2B and international markets. If you operate a panel, a router, an exchange, or a community you recruit from, this section covers how to connect.
There are two ways in, and the right one depends on how much traffic we expect to run together — not on how sophisticated your API is.
Which path is yours
| Send us traffic | Integrate your API | |
|---|---|---|
| Time to first respondent | Under an hour | 2–4 weeks |
| Who builds | Nobody — it's configuration | Our engineering team |
| What you provide | Five return URLs | API docs, credentials, a staging environment |
| How a buyer targets you | Agreed per project, off-platform | Directly, from our targeting UI |
| Quota enforcement | Ours, and yours if you have it | Ours, pushed to you where your API supports it |
| Pricing | Agreed per project | Quoted or offered in-app, per your model |
| How buyers see you | A named sample source on their study | A provider in the panel picker |
| Best for | Most partners. Pilots, regional panels, client communities, anything bespoke | Panels we expect to field continuously, at volume |
Start with "send us traffic" unless we've already agreed otherwise. It is live the same day, it proves the commercial fit, and nothing about it blocks a deeper integration later.
→ Send us traffic — the link contract, start to finish → Integrate your API — what we need, and how the project runs
What we do on our side
Whichever path you take, the same things are true:
We screen before your respondent starts. Every entrant passes fraud and duplicate detection (Research Defender) before they reach a question. A blocked respondent is returned to you immediately on a dedicated leg, not silently dropped — so you can replace them, and you aren't billed for traffic we were never going to accept.
We report five outcomes, not two. Complete, screen-out, over-quota, quality and security each get their own return leg. Over-quota in particular never collapses into screen-out: they are commercially different events, and merging them corrupts incidence on both sides of the trade.
We don't invent quality flags. A quality or security return means we hold an actual signal. Our ordinary terminates come back as ordinary terminates, because a wrongly-flagged panelist carries a reputation cost we're not entitled to impose.
Respondents get a real survey. Studies are checked before they field — logic, routing, mobile layout, length — so your panelists aren't the ones discovering a broken page.
How a partnership starts
- Email developers@flashpoint.ai with your coverage: markets, approximate panel size, categories you can reach, and anything distinctive. If you have API documentation, send it.
- We reply within two working days — either with a commercial conversation, or with a specific gap analysis against the API requirements if you're on that path.
- Commercial terms and a DPA before any live traffic.
- Configuration or build, per the path above.
- Certification — a joint walk-through on a test study before anything goes live.
Next steps
- Send us traffic — the fastest path, live today
- Integrate your API — the full integration
- Data quality — what we screen for, and how