What’s New
Fix
Search response type parity
Generated TypeScript types now include the documentedconfidence, low_confidence, and structured evidence fields on search matches. Structured evidence stays in the same order as the plain-text reasons list.Fix
Automatic recovery for raw Instagram requests
Raw Instagram profile, post, and transcript requests now recover automatically from temporary source-platform interruptions. Confirmed missing posts, missing profiles, and private profiles continue to return their documented errors.Batch post and transcript requests now stop queued upstream work when the calling request expires or disconnects. Batch results remain in the same order as the requested shortcodes.Fix
Raw Instagram post & transcript reliability
We resolved an issue where single Instagram post lookups and video transcripts could return errors after a change on the source platform’s side. Individual post lookup, batch post lookup, and the transcript endpoints now return their documented response shapes consistently across the REST API, MCP tools, and no-code actors.We also hardened how transient upstream hiccups surface on these endpoints: a temporary soft-block from the source platform is now returned as a retryable429/503 with Retry-After (matching our other live endpoints) instead of a generic 500. Handle it with the same backoff you use for other live data — see Error Handling.Affected endpoints:GET /v1/raw/instagram/post/{shortcode}POST /v1/raw/instagram/postsGET /v1/raw/instagram/transcript/{shortcode}POST /v1/raw/instagram/transcripts
Feature
Raw Instagram post lookup and transcripts
You can now look up an individual Instagram post by shortcode and fetch video transcripts directly from the raw API. These endpoints return fresh raw post data, including fields that are not guaranteed on cached post-list responses, such as coauthors, paid partnership flags, tagged users, product mentions, display resources, video versions, music attribution, and location data.Available endpoints:GET /v1/raw/instagram/post/{shortcode}for one postPOST /v1/raw/instagram/postsfor up to 20 posts in one requestGET /v1/raw/instagram/transcript/{shortcode}for one video post transcriptPOST /v1/raw/instagram/transcriptsfor up to 10 video post transcripts in one request
post; call the post lookup endpoint separately when you need post metadata alongside a cached transcript.We’ve also added two Apify actors for no-code and workflow use cases:- Instagram Post Lookup
- Instagram Post Transcripts
Feature
MCP Server
The Influship MCP server launched atmcp.influship.com/mcp with eight typed tools. Connect any Model Context Protocol-compatible client, including Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT Connectors, and VS Code. The MCP Server guide lists the current 14-tool surface.Feature
Pay per request with x402 (no API key needed)
Anonymous AI agents can now call supported paid Influship endpoints via the x402 payment protocol. The agent makes a request without anX-API-Key, gets a 402 Payment Required response with a USDC-on-Base price, signs a payment, and retries without signup or billing setup.Feature
Pay with MPP (Stripe cards or USDC on Tempo)
The Machine Payments Protocol — Stripe and Tempo’s open standard for HTTP-native machine-to-machine payments — coexists with x402 on the same endpoints. Pay per request via Stripe SPT (Shared Payment Tokens, USD via card) or USDC on Tempo. Pick whichever rail your client supports; the API accepts both.Feature
Weighted lookalike seeds
Lookalike search now accepts up to 10 seeds with individual weights (0-1). Higher weights make the API lean more heavily on that seed’s characteristics when ranking results.This is particularly useful when you have campaign performance data — weight your best performers higher and the API finds more creators who skew toward that profile.Improvement
Search billing and rate limit alignment
Search billing now cleanly separates the base fee (AI inference cost) from the per-creator delivery fee. Rate limit headers are consistent across all endpoints and accurately reflect credit consumption.Feature
Campaign match endpoint
POST /v1/creators/match scores creators against a campaign brief. Each result includes a decision (good, neutral, or avoid), a numeric score, and human-readable reasoning.The intent.query field (500 chars) describes the campaign. The optional intent.context field (2,000 chars) adds background — target demographics, content format preferences, brand guidelines.See Match Reasons for how to interpret the output.Improvement
Credit-based rate limiting with trust tiers
Rate limits are now enforced using credit budgets instead of simple request counts. Heavier endpoints consume more budget than lighter ones. Trust tiers increase your limits based on lifetime spend — and never downgrade.See Rate Limits & Tiers for the full tier table.Feature
Feature