Skip to main content
Resolve Instagram handles into profile records, then score their distinct creators against a campaign brief. Use this workflow when you need profile data as well as campaign scores. Compare Creators accepts handles directly and skips the separate lookup when you only need scores.

​
Run the complete program

Download the MIT-licensed workflow source or browse it on GitHub. Requires Node.js 22+, pnpm 10.32.1, and an API key.
Replace the handles with your candidates. The program accepts up to ten, ignoring duplicate handles and a leading @. The quickstart covers key setup. Keep keys in the environment. See the TypeScript SDK for client details.

​
Resolution and scoring

The first request resolves your supplied handles:
The complete program is in workflows.ts. It keeps lookup records in the output, deduplicates non-null creator IDs, then sends one campaign-match request. If no handles resolve, it stops before matching. It does not invent scores for unresolved creators. Automatic retries are disabled. Campaign results are sorted by fit score, with good, neutral, and avoid decisions available for manual review. Structured reasons retain their provenance and supporting evidence. See Match Reasons; a score describes this brief, not a creator’s overall quality or likely campaign ROI.

​
Read the output

This abbreviated output uses synthetic example data:
Keep unknown metrics as unknown. Inspect which handles resolved using the profile records rather than assuming one result per input.

​
Maximum intended cost

The program reads actual charges from X-Credits-Charged on each response. Missing headers produce an unknown total. Fewer resolved profiles and deduplicated creators reduce usage. See Pricing.

​
Verification and recovery

Tests use the published SDK with synthetic HTTP responses and make no live calls. Verify access, returned profiles, campaign reasons, and actual charges separately with a budgeted real request. A failure ends the program; the CLI reports status, request ID and Retry-After when supplied. Follow Error Handling before running it again. The command does not automatically retry or hide a failed lookup as a successful empty list.