Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Direct, 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%2Fapidirect.io%2Fapidirect" | 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%2Fapidirect.io%2Fapidirect" | 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 API Direct API.
Search public posts across Twitter, LinkedIn, Reddit, Instagram, TikTok, and Bluesky from one key
Pull a person's or company's LinkedIn profile along with their recent posts and jobs
Read Instagram, YouTube, and TikTok user profiles, posts, followers, and comments
Run Google web search and AI Mode queries and read the results
Look up Google Places details, reviews, and photos for a business
GET STARTED
Search Amazon products and read seller profiles, best sellers, and reviews
Read Trustpilot company reviews and browse category rankings
Patterns agents use API Direct API for, with concrete tasks.
★ Cross-Platform Brand Monitoring
An agent watches how a brand is discussed in public by searching posts across Twitter, Reddit, Instagram, and TikTok, then pulling the Trustpilot reviews for the company. API Direct returns each platform's results through one key, so the agent gathers mentions from many sources without wiring a separate scraper for each.
Call GET /v1/twitter/posts and GET /v1/reddit/posts for a brand term, then GET /v1/trustpilot/company/reviews to pull its review sentiment
Lead and Company Research
A research workflow enriches a target account by reading its LinkedIn company profile and recent posts, then searching for the people who work there. Because API Direct covers LinkedIn person and company endpoints behind the same key, the agent builds a company snapshot in a single pass.
Call GET /v1/linkedin/company for a company, then GET /v1/linkedin/company/posts to read its recent activity
Local Business Intelligence
An agent assembles a profile of a local business by searching Google Places, reading its place details and reviews, and pulling its Facebook page reviews. API Direct returns places and social data from the same interface, so the agent compiles ratings and recent feedback without stitching together multiple vendors.
Call GET /v1/places/search for a business, then GET /v1/places/reviews to read its recent ratings
AI Agent Integration via Jentic
An AI agent reaches API Direct through Jentic without holding the API key itself. It searches by intent, receives the matching platform operation with its input schema, and executes the call with the credential injected at run time, so public-data lookups slot into a larger agent workflow.
Search Jentic for 'search twitter posts', load the GET /v1/twitter/posts schema, and execute it with Jentic-managed credentials
104 endpoints — the api direct api returns real-time public data from linkedin, twitter/x, reddit, youtube, instagram, tiktok, facebook, threads, bluesky, and truth social, plus google search, google maps places, news sites, forums, amazon, and trustpilot, all behind one rest interface and one api key.
METHOD
PATH
DESCRIPTION
/v1/twitter/posts
Search Twitter posts
/v1/linkedin/person
LinkedIn person profile
/v1/instagram/user/posts
Instagram user posts
/v1/reddit/posts
Search Reddit posts
/v1/web/search
Google web search
/v1/places/search
Search Google Places
/v1/amazon/products
Search Amazon products
/v1/trustpilot/company/reviews
Trustpilot company reviews
/v1/twitter/posts
Search Twitter posts
/v1/linkedin/person
LinkedIn person profile
/v1/instagram/user/posts
Instagram user posts
/v1/reddit/posts
Search Reddit posts
/v1/web/search
Google web search
/v1/places/search
Search Google Places
/v1/amazon/products
Search Amazon products
/v1/trustpilot/company/reviews
Trustpilot company reviews
What agents get from Jentic-routed access to this vendor.
Setup
Wiring API Direct by hand means managing one X-API-Key across more than a dozen platform namespaces and handling per-endpoint pricing yourself. Through Jentic you install once, import API Direct from the API Directory, store the key once, and your agent calls it.
Permission scoping
API Direct carries the platform, handle, and search term inside each request, so a rule bounds which operations your agent may call rather than which account it reads. You choose the operations it may use, such as the Twitter and Reddit search endpoints, so marketplace or places lookups are not included unless you add them.
Credential isolation
Your API Direct 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 twitter posts' or 'read a linkedin company profile', and Jentic returns the matching API Direct 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 API Direct API through Jentic.
What authentication does the API Direct API use?
The API Direct API authenticates with an API key sent in the X-API-Key header on every request, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I search posts across multiple social platforms with the API Direct API?
Yes. Each platform has its own search endpoint, such as GET /v1/twitter/posts, GET /v1/reddit/posts, and GET /v1/instagram/posts, and they all use the same key. A batch endpoint groups several lookups into one request when you need results from more than one platform at once.
What are the rate limits for the API Direct API?
API Direct is priced per request with a monthly free tier on every endpoint rather than a fixed rate ceiling, and the OpenAPI spec does not state request limits. Watch for HTTP 429 responses and check the API Direct pricing documentation for the per-endpoint allowances that apply to your plan.
How do I search Twitter posts with the API Direct API through Jentic?
Search Jentic for 'search twitter posts', and it returns the API Direct operation with its input schema. Load the schema and execute GET /v1/twitter/posts with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an API Direct MCP server?
You don't need an MCP server to give your agent API Direct. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the platform operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.
Can I limit what my agent is allowed to do with the API Direct API?
Yes. API Direct carries the platform and query inside the request, so a rule bounds which operations your agent may call rather than which handle it reads. Allow only the lookups the task needs, such as the Twitter and Reddit search operations, and every call runs through your own instance where it is logged for review.
For Agents
Fetch public social, search, places, and marketplace data across more than a dozen platforms from one key: search posts and profiles, read user and post details, and pull reviews and comments. Reads are GET with query parameters authenticated by an X-API-Key header.
Use for: Search for recent Twitter posts about a product launch, Get a LinkedIn company profile and its latest posts, List the comments on an Instagram post, Find YouTube channels that match a topic
Not supported: Does not post content, run ads, or manage social accounts. Use for reading public social, search, places, and marketplace data only.
The API Direct API returns real-time public data from LinkedIn, Twitter/X, Reddit, YouTube, Instagram, TikTok, Facebook, Threads, Bluesky, and Truth Social, plus Google Search, Google Maps places, news sites, forums, Amazon, and Trustpilot, all behind one REST interface and one API key. It exposes search endpoints for posts, users, and companies on each platform alongside detail endpoints for individual profiles, posts, comments, and reviews. A single batch endpoint groups several lookups into one request.
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>