Install Jentic One Beta

Connect the Core API Concepts to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Core API Concepts, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finfluencers.club%2Finfluencers" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Finfluencers.club%2Finfluencers" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Core API Concepts API.

Enrich a creator by handle and platform with full, profile, analytics, or raw data, optionally with include_audience_data and include_lookalikes

Look up creator profiles from an email address via /public/v1/creators/enrich/email/

Submit a batch enrichment file in raw, full, or basic enrichment_mode, then poll its status and download the results as CSV

Search for creators with the discovery endpoint and find similar creators to a known profile

GET STARTED

Start building with Core API Concepts API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Core API Concepts API for, with concrete tasks.

★ Creator research agent through Jentic

An AI agent connected through Jentic builds a shortlist of creators for a brand. It searches the discovery endpoint for candidates, enriches the promising ones by handle to read profile and audience data, and checks audience overlap so the brand does not pay twice to reach the same followers. The Influencers.club key stays in your own Jentic One instance rather than in the agent's context.

Call POST /public/v1/creators/enrich/handle/full/ with handle 'natgeo', platform 'instagram', and include_audience_data true, then summarise the follower count and top audience locations

Bulk creator list enrichment

Enrich a spreadsheet of creator handles without calling the API row by row. Upload the file to the batch enrichment endpoint with an enrichment_mode of raw, full, or basic, poll the batch status until it completes, then download the results as CSV. A stopped batch can be resumed by its batch_id.

Call POST /public/v1/enrichment/batch/ with the handles file, platform 'tiktok', and enrichment_mode 'basic', then poll GET /public/v1/enrichment/batch/{batch_id}/status/ and fetch GET /public/v1/enrichment/batch/{batch_id}/download/ when it finishes

Campaign content tracking

Follow what hired creators actually publish during a sponsorship. Create a social listening campaign with a name, platforms, content_types, start_date, and end_date, add the creators, then list the campaign content and overview as posts come in. The AI report operation summarises the campaign once it has run.

Call POST /public/v1/social/listening/campaign/ with name 'Spring launch', platforms ['instagram'], content_types ['post'], start_date '2026-03-01', and end_date '2026-03-31', then add creators via POST /public/v1/social/listening/campaign/{campaign_id}/creators/

Lookalike creator discovery

Expand a roster from creators that already perform well. The similar creators operation returns lookalike profiles, and exclusion lists keep handles you have already contacted out of discovery results so outreach does not repeat.

Call POST /public/v1/discovery/creators/similar/ for a known creator, then add the handles already contacted to the default exclusion list via POST /public/v1/discovery/exclusion-lists/default/{platform}/entries/

Key Endpoints

73 endpoints — the influencers.

METHOD

PATH

DESCRIPTION

POST

/public/v1/creators/enrich/handle/full/

Enrich a creator by handle with full data

POST

/public/v1/creators/enrich/email/

Enrich creators by email

POST

/public/v1/discovery/

Search for creators

POST

/public/v1/discovery/creators/similar/

Find similar creators

POST

/public/v1/creators/audience/overlap/

Measure audience overlap

POST

/public/v1/enrichment/batch/

Create a batch enrichment job

GET

/public/v1/enrichment/batch/{batch_id}/download/

Download batch results as CSV

POST

/public/v1/social/listening/campaign/

Create a social listening campaign

POST

/public/v1/creators/enrich/handle/full/

Enrich a creator by handle with full data

POST

/public/v1/creators/enrich/email/

Enrich creators by email

POST

/public/v1/discovery/

Search for creators

POST

/public/v1/discovery/creators/similar/

Find similar creators

POST

/public/v1/creators/audience/overlap/

Measure audience overlap

POST

/public/v1/enrichment/batch/

Create a batch enrichment job

GET

/public/v1/enrichment/batch/{batch_id}/download/

Download batch results as CSV

POST

/public/v1/social/listening/campaign/

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Influencers.club by hand means handling its bearer key, polling and resuming asynchronous batch jobs, and keeping platform enums straight across many enrichment operations. Through Jentic you install once, import Influencers.club from the API Directory, store the key once, and your agent calls it.

Permission scoping

Influencers.club puts campaign, subscription, and exclusion list ids in the URL path (/public/v1/social/listening/campaign/{campaign_id}/...), so a rule can pin your agent to one campaign and the operations you pick. Creator enrichment carries the handle in the request body, so there rules bound which operations the agent may call, not which creator.

Credential isolation

Your Influencers.club API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'enrich an Instagram creator' or 'find similar creators', and Jentic returns the matching Influencers.club operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Core API Concepts API through Jentic.

Is there an Influencers.club MCP server?

You don't need an MCP server to give your agent Influencers.club. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. The agent finds the enrichment, discovery, or campaign operation it needs on demand instead of loading every tool definition into its context.

Can I limit what my agent is allowed to do with the Influencers.club API?

Yes. The spec notes that every Influencers.club credential is currently issued with full access, so the limit has to come from somewhere else. Write a Jentic rule that allows only GET /public/v1/social/listening/campaign/{campaign_id}/content/ and GET /public/v1/social/listening/campaign/{campaign_id}/overview/ for one campaign id: a reporting agent can read that campaign and nothing more, it cannot create or delete API keys, and every call it makes is logged.

What authentication does the Influencers.club API use?

Per its OpenAPI spec, the Influencers.club API uses HTTP bearer authentication: send an API key in the `Authorization` header as `Bearer <key>`. The OAuth client registration, authorization, and token operations are the exception: they are called without a bearer credential and identify the app by its client_id. Through Jentic, your key is stored encrypted by your own Jentic One instance and injected into the operations that need it.

Can I find a creator's contact email with the Influencers.club API?

The handle enrichment operations accept an email_required field set to must_have or preferred, which controls whether results must include an email. You can also go the other way: POST /public/v1/creators/enrich/email/ takes an email address and returns the matching creator data.

What are the rate limits for the Influencers.club API?

The OpenAPI spec does not specify request rate limits; check https://docs.influencers.club for current limits. Usage is metered in credits, and GET /public/v1/accounts/credits/ returns your current credit balance and usage.

How do I enrich a list of creators with the Influencers.club API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import Influencers.club from the API Directory, and store your API key. Your agent searches for 'batch enrich creator handles', gets POST /public/v1/enrichment/batch/ with its input schema, uploads the file with an enrichment_mode, then polls the status and downloads the CSV. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which platforms does the Influencers.club API cover?

Platform support varies by operation. Handle enrichment accepts platforms including instagram, youtube, tiktok, twitter, snapchat, discord, and pinterest, while analytics enrichment and exclusion lists include twitch. Check the platform enum on the specific operation before calling it.

Influencers Club Core API Concepts

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer73 EndpointsREST

For Agents

Enrich social media creators by handle or email, discover and compare creators, run batch enrichment jobs, and track creator content with social listening campaigns.

Use for: I need to enrich this Instagram handle with audience data, Find the creator profiles linked to an email address, Search for TikTok creators who post about fitness, Find creators similar to a YouTube channel I already work with

Not supported: Does not handle publishing posts, paying creators, or managing ad spend on social platforms. Use for creator discovery, enrichment, and campaign content tracking only.

The Influencers.club API finds and enriches social media creators across platforms such as Instagram, YouTube, TikTok, Twitch, and X (Twitter). It enriches a creator from a handle or an email address, returning profile, analytics, audience, and contact data, and runs batch enrichment jobs from an uploaded file for larger lists. Its discovery operations search for creators by structured criteria, find similar creators, and measure audience overlap, while social listening campaigns and subscriptions track what a set of creators posts and report on it.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

74%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

93%

Example Validity

Percentage of examples that conform to their schemas.

51%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

90%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Core API Concepts to your agent

Capabilities

Start building with Core API Concepts API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Influencers Club Core API Concepts

Jentic AI Readiness Score

Core API Concepts

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness