Install Jentic One Beta

Connect the LurkAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LurkAPI, 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%2Flurkapi.com%2Flurkapi" | 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%2Flurkapi.com%2Flurkapi" | 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 LurkAPI API.

Get a YouTube, TikTok, or Instagram video transcript as timed segments and one block of text, with an optional language

Search Meta's Ad Library by keyword with country, status, media_type, and date filters via GET /v1/facebook/adLibrary/search/ads

Read public profiles, posts, and comments from TikTok, Instagram, X, Threads, Bluesky, Telegram, and Truth Social by handle or URL

Search Reddit with sort and timeframe, and read subreddit posts and post comments

GET STARTED

Start building with LurkAPI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LurkAPI API for, with concrete tasks.

★ Research agent through Jentic

A research agent gathers public conversation about a brand across platforms without a scraper per site. It searches Jentic for 'search Reddit posts', receives GET /v1/reddit/search with its query, sort, and timeframe parameters, then runs the TikTok hashtag and YouTube search operations, and summarises what people are saying with links to sources.

Call GET /v1/reddit/search with query 'acme headphones' and timeframe week, GET /v1/tiktok/search/hashtag with hashtag 'acmeheadphones', and GET /v1/youtube/search with the brand name, then summarise the top themes

Competitor ad monitoring

See how a market advertises by reading public ad libraries. GET /v1/facebook/adLibrary/search/ads finds ads by keyword with their copy, media, landing page, and run dates, and the TikTok, Google, and LinkedIn ad library operations cover the same ground on those networks. Stopped ads are included unless status=active is passed.

Call GET /v1/facebook/adLibrary/search/ads with query 'meal kit', country US, and status active, and list the advertisers with the most running ads

Video to text

Turn videos into text for summaries, search, or repurposing. GET /v1/youtube/video/transcript reads a video's captions, either the creator's or YouTube's auto-generated ones, flagged by isGenerated, and returns timed segments and one block of text; TikTok and Instagram transcript operations work the same way for their videos.

Call GET /v1/youtube/video/transcript with the video url and language es, and return a five-bullet summary of the transcript

Local reputation tracking

Watch what customers say about physical locations. GET /v1/google/maps/search finds places, GET /v1/google/maps/place returns details, and GET /v1/google/maps/reviews returns reviews by place_id, cid, or url with sort and language options, so a business can track new reviews across its branches.

Call GET /v1/google/maps/reviews with the place_id for each branch and sort newest, then flag reviews with low ratings from the past month

Key Endpoints

89 endpoints — the lurkapi api returns public social media data as clean json with one get request per call, covering profiles, posts, comments, and search across tiktok, instagram, youtube, facebook, reddit, linkedin, x (twitter), threads, bluesky, telegram, truth social, and snapchat.

METHOD

PATH

DESCRIPTION

GET

/v1/youtube/video/transcript

YouTube video transcript

GET

/v1/facebook/adLibrary/search/ads

Search Meta Ad Library ads

GET

/v1/reddit/search

Search Reddit

GET

/v1/tiktok/search/hashtag

TikTok hashtag videos

GET

/v1/instagram/profile

Instagram profile

GET

/v1/google/maps/reviews

Google Maps reviews

GET

/v1/web/scrape

Scrape a public page

GET

/v1/account/credit-balance

Credit balance

GET

/v1/youtube/video/transcript

YouTube video transcript

GET

/v1/facebook/adLibrary/search/ads

Search Meta Ad Library ads

GET

/v1/reddit/search

Search Reddit

GET

/v1/tiktok/search/hashtag

TikTok hashtag videos

GET

/v1/instagram/profile

Instagram profile

GET

/v1/google/maps/reviews

Google Maps reviews

GET

/v1/web/scrape

Scrape a public page

GET

/v1/account/credit-balance

Credit balance

Why Jentic?

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

Setup

Wiring LurkAPI by hand means sending the x-api-key header, picking the right platform operation and version prefix out of many, paging with cursor values, and watching credits_remaining. Through Jentic you install once, import LurkAPI from the API Directory, store the key once, and your agent calls it.

Permission scoping

Each platform sits under its own path prefix, such as /v1/reddit/ or /v1/web/, so a rule can limit your agent to the platforms and operations a task needs. You choose the operations it may call, so credit-heavy ones like residential rendering or custom scraping are not included unless you add them.

Credential isolation

Your LurkAPI 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 'get a YouTube transcript' or 'search Meta ads', and Jentic returns the matching LurkAPI operation with its input schema, out of 89, so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LurkAPI API through Jentic.

What authentication does LurkAPI use?

Per its OpenAPI spec, LurkAPI uses an apiKey sent in the x-api-key header. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

How is LurkAPI usage billed?

Calls cost credits, and responses carry credits_remaining. GET /v1/account/credit-balance is free and shows your balance and daily top-up: once a day (UTC), if your balance is below 25 credits, your first call tops it up to 25. Web scraping through GET /v1/web/scrape costs 1-24 credits depending on the step needed, and max_credits caps a call.

What are the rate limits for LurkAPI?

The OpenAPI spec does not specify rate limits; usage is metered in credits. Check https://lurkapi.com/docs for current limits.

How do I get a YouTube transcript with LurkAPI through Jentic?

Install Jentic One, add LurkAPI from the Jentic directory, and store your x-api-key. Your agent searches for 'get a YouTube video transcript', receives GET /v1/youtube/video/transcript with its url and language parameters, and returns the timed segments or full text. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which platforms does LurkAPI cover?

The spec covers TikTok, Instagram, YouTube, Facebook, Reddit, LinkedIn, X (Twitter), Threads, Bluesky, Telegram, Truth Social, and Snapchat, plus ad libraries from Meta, TikTok, Google, and LinkedIn, Google Maps and News, eBay, TikTok Shop, Linktree, and general web pages.

Is there a LurkAPI MCP server?

You don't need an MCP server to give your agent LurkAPI. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent finds the platform operation it needs by intent instead of loading all of them into its context.

Can I limit what my agent is allowed to do with LurkAPI?

Yes. For a transcript summariser, allow only GET /v1/youtube/video/transcript and GET /v1/account/credit-balance, so the agent cannot spend credits on web scraping or other platforms. The agent's calls are logged for review.

LurkAPI

AI ReadinessAI-Aware (A-)70/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial ListeningapiKey (x-api-key header)89 EndpointsREST

For Agents

Pull public posts, profiles, comments, transcripts, and ad library entries from TikTok, Instagram, YouTube, Reddit, LinkedIn, X, and more, plus Google Maps reviews and any public web page, through one x-api-key.

Use for: Get the transcript of this YouTube video, Find competitor ads running in Meta's Ad Library for 'protein powder', Search Reddit for posts about our product from the past week, List the latest tweets from this handle

Not supported: Does not post, like, follow, or message on any platform, and does not read private accounts. Use for reading public social media, ad library, maps, and web page data only.

The LurkAPI API returns public social media data as clean JSON with one GET request per call, covering profiles, posts, comments, and search across TikTok, Instagram, YouTube, Facebook, Reddit, LinkedIn, X (Twitter), Threads, Bluesky, Telegram, Truth Social, and Snapchat. It also reads ad libraries from Meta, TikTok, Google, and LinkedIn, Google Maps places and reviews, Google News, eBay listings, TikTok Shop products, and Linktree pages, and returns video transcripts for YouTube, TikTok, and Instagram. A set of web endpoints fetches, renders, or unblocks any public page, and calls are billed in credits with the balance reported on each response.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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.

100%

Example Validity

Percentage of examples that conform to their schemas.

67%

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: C+Signals: 4

82%

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.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

87%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

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: A+Signals: 1

95%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LurkAPI to your agent

Capabilities

Start building with LurkAPI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

LurkAPI

Jentic AI Readiness Score

LurkAPI

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