Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the InsightSocial API, 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%2Finsightsocial.app%2Finsightsocial" | shStep 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%2Finsightsocial.app%2Finsightsocial" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with InsightSocial API.
Search public posts and conversations on Reddit, TikTok, X (Twitter), Threads, Bluesky, and other platforms by keyword
Read a LinkedIn profile by URL with its experiences, educations, skills, and recent posts, or a company page
Fetch a YouTube video's transcript, comments, and sponsors, or list trending videos by region
Pull an Instagram profile and its posts or reels, with filters such as since, recent_days, and exclude_pinned
GET STARTED
Research competitor ads in the Facebook ad library by company or keyword, including ad transcripts
Price any call before running it with dry_run=1, which returns credits_min and credits_max without charging
Check the key owner's credit balance and this period's usage with the free credits operation
Patterns agents use InsightSocial API for, with concrete tasks.
★ Social research agent through Jentic
An AI agent connected through Jentic answers questions like 'what are people saying about our launch' by searching Reddit, X, and TikTok, then reading the top posts and their comments. Because every platform shares one response shape per entity, the agent compares results across networks without per-platform parsing. It can call with dry_run first to check the credit cost, and the x-api-key stays in your own Jentic One instance.
Call GET /v1/reddit/search with query 'acme launch', sort 'new', and timeframe 'week', then read the top result's comments with GET /v1/reddit/post/comments using its url
Video transcript and comment analysis
Turn a YouTube video into text an agent can summarise. The transcript operation takes the video url and a language, and the comments operation returns viewer comments with an order and searchTerm filter, so an agent can summarise a video and the reaction to it in one pass. Transcripts are also available for X posts, Reddit posts, and Facebook ad library ads.
Call GET /v1/youtube/video/transcript with url 'https://www.youtube.com/watch?v=dQw4w9WgXcQ' and language 'en', then summarise the transcript in five bullet points
LinkedIn prospect and company research
Sales and recruiting agents read a LinkedIn profile from its URL and expand it into experiences, educations, skills, and recent posts, or read a company page and its posts. Similar-profile lookups help widen a shortlist from one good match.
Call GET /v1/linkedin/profile with url 'https://www.linkedin.com/in/example', then GET /v1/linkedin/profile/experiences with the same url to list past roles
Competitor ad monitoring
Marketing teams track what competitors advertise. The Facebook ad library operations search ads by keyword or by company, filtered by country, status, and media_type, and return an ad's transcript; TikTok's ad library is covered as well.
Call GET /v1/facebook/adlibrary/company/ads with companyName 'Acme', country 'US', and status 'ACTIVE', then summarise the creative themes
306 endpoints — the insightsocial api reads public social data from 25 platforms, including linkedin, tiktok, instagram, facebook, youtube, x (twitter), and reddit, through one api key and one credit balance.
METHOD
PATH
DESCRIPTION
/v1/reddit/search
Search Reddit posts
/v1/tiktok/search
Search TikTok videos
/v1/linkedin/profile
Get a LinkedIn profile by URL
/v1/youtube/video/transcript
Get a YouTube video transcript
/v1/instagram/profile/posts
List an Instagram profile's posts
/v1/twitter/tweet/replies
List replies to a tweet
/v1/facebook/adlibrary/search/ads
Search the Facebook ad library
/v1/credits
Get credit balance and usage
/v1/reddit/search
Search Reddit posts
/v1/tiktok/search
Search TikTok videos
/v1/linkedin/profile
Get a LinkedIn profile by URL
/v1/youtube/video/transcript
Get a YouTube video transcript
/v1/instagram/profile/posts
List an Instagram profile's posts
/v1/twitter/tweet/replies
List replies to a tweet
/v1/facebook/adlibrary/search/ads
Search the Facebook ad library
/v1/credits
Get credit balance and usage
What agents get from Jentic-routed access to this vendor.
Setup
Wiring InsightSocial by hand means sending the x-api-key header, tracking per-operation credit prices, and choosing among hundreds of platform-specific operations. Through Jentic you install once, import InsightSocial from the API Directory, store the key once, and your agent calls it.
Permission scoping
InsightSocial names the platform in each operation's path and takes the handle, URL, or query as a query parameter, so rules bound which operations your agent may call, not which account or post. You choose the operations it may call, so the agent cannot spend credits on platforms you did not include.
Credential isolation
Your InsightSocial 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 'search Reddit for mentions' or 'get a YouTube transcript', and Jentic returns the matching InsightSocial operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using InsightSocial API through Jentic.
Is there an InsightSocial MCP server?
You don't need an MCP server to give your agent InsightSocial. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. With hundreds of operations in the spec, the agent searching for the one it needs keeps its context far smaller than loading every tool definition up front.
Can I limit what my agent is allowed to do with the InsightSocial API?
Yes. For a brand-monitoring agent, write a rule that allows only GET /v1/reddit/search, GET /v1/reddit/post/comments, and GET /v1/credits. The agent can search Reddit, read comment threads, and watch its own credit balance, but it cannot spend credits on LinkedIn, TikTok, or any other platform, and every call it makes is logged.
What authentication does the InsightSocial API use?
Per its OpenAPI spec, the InsightSocial API uses an API key sent in the `x-api-key` header; keys start with `isk_` and come from the InsightSocial dashboard. The endpoint list and the OpenAPI document itself are open without a key. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected when each call runs.
How much does an InsightSocial call cost?
Calls are billed in credits from one balance, and the price varies by operation; for example, the spec lists the Bluesky profile lookup at 10 credits per call. Add dry_run=1 to any data call to get credits_min and credits_max without being charged, and call GET /v1/credits, which is free, to see your balance and this period's usage.
What are the rate limits for the InsightSocial API?
The OpenAPI spec mentions a rate limit but does not state a number; check https://insightsocial.app for current limits. It does note that a paginated walk billed as one call counts once against your rate limit.
How do I get a YouTube transcript with the InsightSocial API through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import InsightSocial from the API Directory, and store your API key. Your agent searches for 'get a YouTube video transcript', gets GET /v1/youtube/video/transcript with its input schema, and calls it with the video url and language. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can the InsightSocial API post or reply on social networks?
No. Every operation in the spec is a GET that reads public data. It does not publish posts, send messages, or act on behalf of an account; use each platform's own publishing API for that.
For Agents
Look up public profiles, posts, comments, transcripts, and search results across LinkedIn, TikTok, Instagram, YouTube, X, Reddit, and other platforms with one key, and check call prices with dry_run.
Use for: Search Reddit for posts mentioning my product this week, Get the transcript of this YouTube video, Pull the LinkedIn profile and experience for this URL, Find TikTok videos using the hashtag skincare
Not supported: Does not handle publishing posts, sending direct messages, or managing social accounts. Use for reading public social profiles, posts, comments, transcripts, and search results only.
The InsightSocial API reads public social data from 25 platforms, including LinkedIn, TikTok, Instagram, Facebook, YouTube, X (Twitter), and Reddit, through one API key and one credit balance. It looks up profiles, posts, comments, and search results, and reaches platform-specific data such as LinkedIn company pages and job posts, YouTube transcripts and trending videos, TikTok hashtag search, and the Facebook and TikTok ad libraries. Schema 2 returns one response shape per entity on every platform, and each call can be priced in advance with dry_run before any credits are spent.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>