AI Agent Integration

Your agent is one install away from the creator economy.

Give Claude, Cursor, or any MCP-compatible agent structured access to creator search, campaign scoring, and audience intelligence. As a native tool call.

mcp-config.json
{
  "mcpServers": {
    "influship": {
      "command": "npx",
      "args": ["@influship/mcp-server"]
    }
  }
}

Building an agentic product instead? Use our API directly

Get API KeyGet API Key

what agents can do

From brief to shortlist in one conversation

Your agent uses Influship as a tool โ€” searching creators, evaluating fit, and building recommendations with structured data at every step.

1Search

โ€œFind sustainable fashion creators in NYC for our eco campaignโ€

Tool Call

influship.searchCreators({
  query: "sustainable fashion NYC",
  min_followers: 50000
})

Result

12 creators found@ecoella ยท 94% match@stylemaven ยท 91% match
2Evaluate

โ€œCheck brand safety and audience alignment for the top candidatesโ€

Tool Call

influship.enrichCreator({
  id: "cr_8x7kd9",
  include: ["audience", "safety"]
})

Result

94% authentic engagement42% NYC audienceBrand safe โœ“
3Recommend

โ€œBuild a final shortlist with rationale for each pickโ€

Tool Call

โ†’ Structured output with
  creator rankings

Result

3 creators recommendedEach with fit score, rationale, and projected reach

What a scraper gives your agent

<div class="profile-card">
  <span class="name">@ecoella</span>
  <span class="cat">Fashion</span>
  <span>142,300 followers</span>
</div>

What Influship gives your agent

match_score: 0.94
decision: "good"
reasons:

"Content deeply aligned with sustainable fashion..."

"Strong engagement consistency signals authentic audience"

ai_summary: "NYC-based sustainable fashion creator..."

Agents reason with structure. We give them structure.

An agent with a web scraper gets unstructured HTML it has to parse and hope for the best. Not enough to make a real decision.

An agent with Influship gets scored results with AI-generated match reasons, campaign fit decisions, and content analysis. The agent can reason about why a creator fits โ€” not just whether they match a keyword.

<200ms

Per tool call

3

Native tools

0

Wrapper code

MCP or API. Same intelligence, different integration.

Choose the integration that fits your architecture. Both return the same structured, scored data.

$ npm i @influship/mcp-server

{
  "mcpServers": {
    "influship": {
      "command": "npx",
      "args": ["@influship/mcp-server"]
    }
  }
}

MCP Server

Auto-discovered tools for Claude, Cursor, and any MCP client. Your agent calls search_creators and score_campaign_fit as native tools. One install, zero wrapper code.

Auto-discovered tools
One-line install
Works with any MCP client
POST /v1/creators/search
Authorization: Bearer sk_live_...

{
  "query": "sustainable fashion NYC"
}

REST API

Building creator intelligence into your own agentic product? Same data, same search โ€” via REST or the TypeScript SDK. Define tool schemas from our OpenAPI spec.

TypeScript SDK available
OpenAPI spec for tool generation
Standard Bearer token auth

Agents without API keys can use x402 micropayments for account-less access.

Your agent's next tool call.

Free sandbox. MCP server or API. Set up in under five minutes.