Digital Footprint checks Kickstarter from an username as part of every lookup, alongside 885+ other platforms, breach history and public web mentions - one request, one shape of answer. A hit means an account exists for that input; account contents are never collected.
Standard tier - checked on every full lookup
Kickstarter is checked from a username. The response says whether that handle exists on Kickstarter - registered: true or registered: false - with the moment that was established in checkedAt. An email address on its own cannot reach Kickstarter; if you only have an email, its local part is tried as a handle and any hit is labelled as derived, never counted as a confirmed match.
Kickstarter is checked on every full lookup (?wait=true or streaming), alongside every other platform. It is not in the sub-second instant subset, which is reserved for the highest-value platforms for each input type.
If Kickstarter blocks the check, times out, or answers ambiguously, it is omitted from results[] entirely rather than returned as registered: false. Absence from the response means "unconfirmed", never "no account".
Payment and crowdfunding accounts are checked most often in KYC, AML and payout onboarding. Peer-to-peer payment and creator-support accounts show that an email or phone number has been used for real money movement before - useful context when a new customer is about to receive or send funds.
More on this: Mule account detection.
curl -X POST "https://api.digifootprint.dev/v2/lookup?wait=true" \
-H "Authorization: Bearer dfp_your_key" \
-H "Content-Type: application/json" \
-d '{"query": "someuser"}'{
"platform": "kickstarter",
"registered": true,
"checkedAt": "2026-10-15T09:53:18.071Z",
"identity": "username"
}The full response shape - breaches, web mentions, matches versus socialMatches, and what method means - is in running a lookup.
Every one of these is checked in the same request as Kickstarter.
Free to start, no card. Then pay as you go, or pick a plan when your volume grows.