Match Reasons
Every scored result includes human-readable reasons explaining why a creator was returned. These reasons help you validate results, build trustworthy UIs, and debug queries that aren’t landing.Where Reasons Appear
| Endpoint | Field | What it explains |
|---|---|---|
POST /v1/search | data[].match.reasons | Why the creator matches your query |
POST /v1/creators/lookalike | data[].similarity.shared_traits | Why the creator is similar to the |
POST /v1/creators/match | data[].match.reasons | Why the creator is a good, neutral, or poor fit for the campaign |
Search Reasons
Search results include a score and a list of reasons:- content relevance to the query
- audience quality signals
- posting consistency
- niche depth and focus
Lookalike Reasons
Lookalike results explain shared traits between the seed creator and the match:Campaign Match Reasons
POST /v1/creators/match returns structured campaign-fit output with a and supporting reasons:
| Decision | Meaning |
|---|---|
good | Strong fit for the campaign |
neutral | Could work — review manually |
avoid | Weak fit, likely not worth pursuing |
How to Use Reasons
- Surface them in your UI. Reasons make AI-driven results feel transparent. Showing “Strong sustainable fashion focus” next to a creator helps your users trust the ranking.
- Validate your queries. If the reasons don’t match your intent, the query needs refining — tighten the language or add filters.
- Compare across results. Reasons help you understand why one creator ranked higher than another, beyond just the numeric score.
- Debug broad searches. When results feel off, the reasons usually reveal whether the query was too vague or the filters too loose.