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": {
      "type": "http",
      "url": "https://mcp.influship.com/mcp",
      "headers": { "X-API-Key": "your-api-key-here" }
    }
  }
}

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

semantic_search_creators({
  query: "sustainable fashion NYC",
  min_followers: 50000
})

Result

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

“Score the top candidates against the campaign brief”

Tool Call

match_creators({
  creator_ids: ["223e4567-e89b-12d3-a456-426614174001"],
  intent_query: "Eco fashion campaign in NYC"
})

Result

Decision: goodFit score: 0.91Structured reasons with supporting evidence
3Recommend

“Build a final shortlist with rationale for each pick”

Tool Call

→ Structured output with
  creator rankings

Result

3 creators recommendedEach with fit score, decision, and rationale

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.

# Hosted MCP server
# https://mcp.influship.com/mcp

{
  "mcpServers": {
    "influship": {
      "type": "http",
      "url": "https://mcp.influship.com/mcp",
      "headers": { "X-API-Key": "your-api-key-here" }
    }
  }
}

MCP Server

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

Auto-discovered tools
One-line install
Works with any MCP client
POST /v1/search
X-API-Key: inf_...

{
  "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
X-API-Key authentication

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.

Get API Key
Or explore:
APIFor AI Agents (machine-readable)DatasetsStartup Program