canonical: https://jentic.com/apis/hproxy.com/hproxy # HProxy API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - Search the LinkedIn, Google, and Facebook ad libraries for a company's ads - Price and order a proxy plan from the wallet, then generate proxy lines filtered by country, city, isp, or asn - Check proxies in bulk as a job and look up the location and network of an IP address ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Scraper** — Profiles, posts, comments, transcripts, searches, and ad libraries across social and creator platforms, plus call history - **Products and orders** — List and price proxy products, create orders from the wallet, and read orders - **Plans and proxies** — Plan stats, IP whitelist, sticky sessions, password rotation, and proxy line generation - **Free tools** — Live proxy list, proxy checker, bulk check jobs, and IP location lookup - **Account and partners** — Wallet, webhooks, announcements, customers, deposits, credit, and bandwidth usage ## AI readiness 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. - **Score:** 54 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 39 / 100 - Agent Usability: 62 / 100 - Security: 50 / 100 - AI Discoverability: 66 / 100 - **View full report:** https://jentic.com/apis/hproxy.com/hproxy/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Bright Data** — Proxy networks and web data collection - **Oxylabs** — Proxies and web scraping APIs - **Apify** — Platform for running web scraping actors and storing results ## FAQ ### 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.