LurkAPI
API for collecting structured public social posts, ad creatives and landing pages across multiple platforms.
Who it suits Marketers and business owners planning search campaigns who want evidence of search demand and competition before choosing termsPricing Free + paidLast verified
What it does
LurkAPI is an API for PPC specialists, agencies and researchers who need structured copies of public social posts, ad creatives and landing pages across social platforms and public web pages. Platform coverage LurkAPI documents roughly 70 endpoints spanning about 15 public platforms, including Meta (Facebook & Instagram) Ad Library, Google Ads Transparency, LinkedIn and TikTok ad libraries, Reddit, YouTube, X/twitter and others. Endpoints target ad libraries, public posts, videos, transcripts, comments and profile data so you can gather the public signals you need for competitive or keyword research. Structured output and export formats Responses are returned as machine-friendly JSON with named fields and exportable CSV pages for spreadsheet workflows. The API emphasizes “one request, clean data” to simplify downstream parsing, analysis and ingestion into scripts or dashboards. Developer integrations and LLM connector LurkAPI exposes a REST API (api.lurkapi.com) with x-api-key auth, an OpenAPI spec and client SDKs (including a published Python package). It also provides an MCP connector/intended MCP server example so LLMs like Claude can query live public social data during a chat session. Web rendering and scraping endpoints Beyond social endpoints, the product documents browser-render options and scraping endpoints that can render pages, handle common bot protections and extract structured content from public web pages. Changelog notes indicate optional residential IP or captcha handling for more complex renders. Pricing model and operational notes LurkAPI uses a pay-per-request credit model with free credit allowances for new accounts and a free-tools page that offers limited daily queries without an account. Many endpoints cost a single credit while heavier operations (renders, captcha or residential IP calls) can cost more; check endpoint-level docs for exact credit costs. The service is explicitly for public data only.


