Install Jentic One Beta

Connect the HProxy API to your agent

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

Pull a public Instagram, TikTok, X, Threads, or Bluesky profile and its recent posts by handle

Search TikTok, YouTube, Reddit, Threads, and Pinterest by keyword or hashtag to track what is being posted

Read comments and replies on TikTok, YouTube, Facebook, and Reddit posts

Fetch video transcripts from YouTube, TikTok, Instagram, X, and Facebook posts

GET STARTED

Start building with HProxy API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HProxy API for, with concrete tasks.

★ Agent social listening briefs

An AI agent preparing a brand mention summary needs fresh public posts from several platforms without a separate integration for each. Through Jentic it searches for the HProxy scrape operations by intent, runs keyword searches on TikTok and Reddit and a hashtag search on YouTube, and reads the top comments, all with one key attached by your own instance.

Call GET /api/v1/scrape/tiktok/search with query set to the brand name, then GET /api/v1/scrape/reddit/search with the same query, and summarise the most discussed posts

Creator vetting for influencer campaigns

Before signing a creator, a marketing team checks their reach and content. The scraper returns profiles and recent posts by handle on Instagram, TikTok, and YouTube, TikTok audience demographics, and Linktree or other link-in-bio pages, so the team sees the creator's footprint across platforms in one pass.

Call GET /api/v1/scrape/instagram/profile with handle set to the creator's handle, then GET /api/v1/scrape/tiktok/audience for the same creator and compare follower counts

Competitor ad research

Growth teams watch what competitors advertise. The ad library endpoints search LinkedIn, Google, and Facebook ads by company or advertiser and return ad details, so an analyst can collect a competitor's live creative across three ad networks.

Call GET /api/v1/scrape/facebook/ad-companies-search for the competitor, then GET /api/v1/scrape/facebook/ad-company with the matched company and list its active ads

Proxy purchasing and health checks

A data team buying proxies wants pricing, ordering, and checks under one key. The product price endpoint quotes a quantity and period in integer cents, an order draws from the prepaid wallet, the generate endpoint produces proxy lines filtered by country, city, isp, or asn with optional stickyMinutes, and a proxy check job tests a large list and returns results to download.

Call GET /api/v1/products/{id}/price with quantity 10 and country DE, then POST /api/v1/orders with product_id and quantity 10, and POST /api/v1/plans/{id}/generate with country DE and count 10

Key Endpoints

161 endpoints — the hproxy api scrapes public profiles, posts, comments, transcripts, and search results from social and creator platforms including instagram, tiktok, youtube, x, linkedin, facebook, reddit, threads, bluesky, and pinterest, and sells proxy plans paid from a prepaid wallet.

METHOD

PATH

DESCRIPTION

GET

/api/v1/scrape/instagram/profile

Instagram profile by handle

GET

/api/v1/scrape/tiktok/search

TikTok keyword search

GET

/api/v1/scrape/youtube/transcript

YouTube video transcript

GET

/api/v1/scrape/facebook/ad-search

Facebook ad library search

POST

/api/v1/orders

Create a proxy order

POST

/api/v1/plans/{id}/generate

Generate proxy lines

GET

/api/proxy-list

Live free proxy list

GET

/api/ip/{ip}

IP location and network lookup

GET

/api/v1/scrape/instagram/profile

Instagram profile by handle

GET

/api/v1/scrape/tiktok/search

TikTok keyword search

GET

/api/v1/scrape/youtube/transcript

YouTube video transcript

GET

/api/v1/scrape/facebook/ad-search

Facebook ad library search

POST

/api/v1/orders

Create a proxy order

POST

/api/v1/plans/{id}/generate

Generate proxy lines

GET

/api/proxy-list

Live free proxy list

GET

/api/ip/{ip}

IP location and network lookup

Why Jentic?

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

Setup

Wiring HProxy by hand means sending the X-API-Key header, passing x-api-key again on scraper calls, keeping money in integer cents, and telling keyed calls apart from the free endpoints. Through Jentic you install once, import HProxy from the API Directory, store the key once, and your agent calls it.

Permission scoping

HProxy puts each scrape target in its own path, such as /api/v1/scrape/instagram/profile, while the handle or query travels as a parameter, so a rule can bound your agent to the platforms and operations you pick, not to one account. You choose the operations it may call, so spending ones like orders or customer credit are not included unless you add them.

Credential isolation

Your HProxy 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 'scrape a tiktok profile' or 'check a proxy list', and Jentic returns the matching HProxy operation out of 161 with its input schema so the agent sends the right handle or url without reading the reference docs.

FAQs

Specific to using HProxy API through Jentic.

What authentication does the HProxy API use?

Per its OpenAPI spec, the HProxy API authenticates with an API key in the `X-API-Key` header, and the scraper operations also declare a required x-api-key query parameter. The free tools, such as the live proxy list, the single and batch proxy checks, and the IP lookup, are declared with no security and ignore a key. Through Jentic the key is stored by your own instance and attached at call time.

Which platforms can the HProxy scraper read?

The spec has scrape operations for Instagram, TikTok, YouTube, X, LinkedIn, Google, Facebook, Reddit, Threads, Bluesky, Truth Social, Pinterest, Twitch, Snapchat, Spotify, SoundCloud, Kick, Amazon shop pages, and link-in-bio pages like Linktree. Each takes a handle, query, or url, and GET /api/v1/scrape/runs returns your call history.

What are the rate limits for the HProxy API?

Limits vary by endpoint per the spec. The free proxy list states a fair-use limit of about 120 requests per minute per IP, and the proxy checkers allow 120 in a burst per IP then 5 a second, with 300,000 proxies checked a day per IP and ten times both with an API key. Over a limit you get a 429 with Retry-After.

Is there an HProxy MCP server?

You don't need an MCP server to give your agent HProxy. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the scrape, proxy, and lookup operations on demand instead of loading a large tool list into its context up front.

How do I get a YouTube transcript through Jentic?

Search Jentic for 'youtube video transcript', load GET /api/v1/scrape/youtube/transcript, and pass the video url with an optional language. Your instance attaches the key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the HProxy API?

Yes. Write a rule that allows only GET operations under /api/v1/scrape/, and a research agent can read profiles, posts, and transcripts but cannot place orders, credit customer balances, or rotate proxy passwords, and every call it makes is logged.

HProxy API

AI ReadinessFoundational (C)54/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial ListeningapiKey161 EndpointsREST

For Agents

Scrape public social media profiles, posts, comments, and transcripts across major platforms, buy and generate proxies from a prepaid wallet, and check proxies or look up IPs.

Use for: Get the public Instagram profile for a creator handle, Search TikTok for videos about a product launch this week, Retrieve the transcript of a YouTube video, List all comments on a Reddit post

Not supported: Does not post content, log in to user accounts, or read private profiles and messages. Use for public social data scraping, proxy purchasing, and proxy and IP checks only.

The HProxy API scrapes public profiles, posts, comments, transcripts, and search results from social and creator platforms including Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Reddit, Threads, Bluesky, and Pinterest, and sells proxy plans paid from a prepaid wallet. Scraper calls take a handle, query, or url and return a consistent envelope, while proxy plans can be priced, ordered, and turned into proxy lines targeted by country, city, ISP, or ASN. A set of free no-key endpoints serves a live proxy list, a proxy checker, and an IP location lookup, and all money values are integer cents.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

92%

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).

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: FSignals: 4

60%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

44%

OperationId Quality

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

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: B-Signals: 1

62%

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: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HProxy API to your agent

Capabilities

Start building with HProxy API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

HProxy API

Jentic AI Readiness Score

HProxy API

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