Skip to main content
Scored results include reasons you can use to review matches, explain rankings to your users, and refine queries.

Where Reasons Appear

Search Reasons

Search results include a score, a plain-text reasons list, and a structured evidence array that grounds each reason, plus a confidence value and a low_confidence marker:
Use reasons for plain-text explanations and evidence for the same reasons with source details you can display alongside each match.

Provenance

Every entry in evidence carries a provenance label so you can tell a grounded claim from an inference. Strongest first: An evidence_quote contains supporting text copied verbatim from a source post. It is null when a supporting quote is unavailable; source_post_id is still returned when available. Display the quote and provenance together so users can distinguish post evidence, profile facts, and inferred reasons. Source IDs are identifiers, not public post URLs; do not construct a link from the ID.

Review lower-confidence matches

confidence mirrors score (0–1). Use match.ranking_source to interpret it: reranked indicates AI relevance scoring, while retrieval_fallback indicates discovery ranking. See search quality. When low_confidence is true, group the result under a label such as “Additional candidates to review.” This flag labels results without changing which creators are returned.

Lookalike Reasons

Lookalike results explain shared traits between the seed creator and the match:
Shared traits describe content topics, presentation style, and posting or engagement patterns.

Campaign Match Reasons

POST /v1/creators/match returns structured campaign-fit output with a and supporting reasons:
Campaign-match reasons carry the same provenance label as search evidence (post_evidence, profile_fact, inferred). When present, source_post_id identifies the source post and evidence_quote contains a verbatim snippet. Show the quote and provenance to your users. Neither source_post_id nor fact_id is a public URL.

How to Use Reasons

  • Display reasons alongside scores. A reason such as “Publishes sustainable fashion content” gives users a concrete detail to review.
  • 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.

Scores vs Reasons

Treat the score as the summary and the reasons as the explanation. A high score with reasons that don’t match your intent is a signal to refine the query, not to trust the number.