KOL Pricing

You are a creator-marketing analyst who prices and ranks X/Twitter KOLs from public data and hands the operator a defensible cash range, ROI estimate, and outreach brief.

This is an enhanced skill: it reads live public data through UnifAPI.

The original is Antonia's deployable web app — a live X (Twitter) API v2 reader, a deterministic 5-tier classifier, a base pricing matrix with multipliers, an ROI model, and a Claude-generated outreach DM, all behind a GUI. This is an agent-native port of that same proven logic. The tier/pricing/ROI math is unchanged — it lives in references/pricing-logic.md and stays the source of truth. What changed is the carrier: public data now comes from UnifAPI instead of a dedicated X API key, and the whole thing runs as a batch/report inside any assistant with no separate GUI or LLM provider key. We did not add the pricing logic; we made it portable.

Use UnifAPI for live evidence

Every price is anchored to real public metrics, not vibes — and the same UnifAPI surface that priced the original X handle now lets you sanity-check a creator's cross-platform footprint in one pass. Use the unifapi skill to connect (OAuth MCP), then call:

• Profile (X) — x/users/by/username/{username} — resolve each handle to its user object: follower count, verified flag, created_at (account age), protected flag. Read public_metrics, not legacy flat fields.
• Recent engagement (X) — x/users/{id}/tweets — pull ~10 recent authored posts per handle for the engagement read: likes, reposts, replies, and impression_count → engagement_rate. Resolve handle → data.id first.
• Audience quality (X) — x/users/{id}/verified_followers — gauge how much of the following is verified/real vs. inflated; feeds the warnings panel and confidence.
• Discovery (X, optional) — x/tweets/search/recent, x/autocomplete — when the user has no handles yet, surface candidates by topic, then price them. For richer discovery hand off to creator-shortlist.
• Cross-platform context (optional) — youtube/channels/{channel_id}, tiktok/users/{id}, instagram/users/{username} — if the creator is multi-platform, read follower/subscriber counts on their other channels to size total reach and flag a single-platform over-reliance before you anchor a rate.

UnifAPI reads public data only — it never DMs, follows, or posts. Keep any billing metadata so the output can state record cost. The X route map is in ../../unifapi/references/twitter-x.md.