Skip to main content
Compare creators you already know by sending their Instagram handles directly to campaign matching. This recipe makes one match request and does not run a discovery search or a separate profile lookup.

Set up

Install the TypeScript SDK in a Node.js 22+ project and set INFLUSHIP_API_KEY in your environment. The quickstart walks through key creation and your first request. Save this code as compare-creators.ts:
Run the script with real usernames you want to compare:
Replace the two uppercase placeholders. The input list is capped at ten to keep this example’s request bounded. A failed request exits the script; it is not automatically retried. See Error Handling to add recovery for your application.

Read the comparison

This output uses synthetic example data:
The decisions are good, neutral, and avoid. Keep neutral results available for manual review. The score reflects this brief, not a creator’s overall quality or expected campaign performance. Match reasons are objects with a text field, unlike search reasons, which are strings. Preserve the provenance label when presenting reasons. post_evidence includes a supporting post reference; profile_fact rests on a profile fact; inferred is an inference. See Match Reasons.

Cost and unresolved creators

Matching costs one credit ($0.01) per creator scored. Comparing ten scored creators costs ten credits ($0.10). Read the actual charge from X-Credits-Charged rather than assuming every input was scored. See Pricing. Use handles that resolve to creators in the Influship index. Do not invent a score for a missing creator or treat a failed request as a weak match. If you need to inspect which handles resolve first, use Score Campaign Fit for an Existing List. For credential, billing, rate-limit, and temporary failures, follow Error Handling. The script disables automatic retries; check the failure and the request budget before running it again. Browse the cookbook for discovery and export workflows.