Instagram scraper API with no login, no proxies, no account: pay $0.01 per post

Search for an Instagram scraper and you land in one of two places: a GitHub repo that stopped working when Instagram last changed its internals, or a scraper marketplace where the data sits behind an account, a credit card, a credit balance, an actor picker, and a proxy configuration screen. Both routes get you the same thing in the end, a JSON object with view and like counts, after very different amounts of suffering. This post is about the third route: an Instagram scraper API where the entire onboarding flow is "send one cent and a URL."

The two flows, side by side

Here is what actually stands between you and an Instagram view count on a marketplace platform like Apify, which is a capable product with a genuinely large catalog, versus the x402 route. The comparison is about flow, not quality:

Marketplace platforms earn their complexity when you need arbitrary structured data: full comment threads, follower lists, hashtag crawls, custom fields. If that is your job, an actor marketplace is the right tool. But the overwhelmingly common case, "here is a post URL, give me its numbers," does not need a platform. It needs one HTTP request.

The one-request version

No login, because there is nothing to log into. No proxies, because you are not scraping; our data infrastructure does that work server-side and you buy the answer. Payment happens inline over HTTP via the x402 protocol:

import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm";
import { privateKeyToAccount } from "viem/accounts";

const payFetch = wrapFetchWithPaymentFromConfig(fetch, {
  schemes: [{
    network: "eip155:8453",
    client: new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_PRIVATE_KEY)),
  }],
});

const res = await payFetch(
  "https://x402.findclout.com/api/v1/instagram/post?url=" +
    encodeURIComponent("https://www.instagram.com/reel/DLmR4kXtQ2a/")
);
console.log(await res.json());

{
  "success": true,
  "platform": "instagram",
  "fetchedAt": "2026-07-19T14:03:27.000Z",
  "url": "https://www.instagram.com/reel/DLmR4kXtQ2a/",
  "username": "houseofhighlights",
  "views": 2841903,
  "likes": 193412,
  "comments": 2874,
  "shares": 0
}

The wallet needs USDC on Base and nothing else: no ETH for gas, no account balance page, no credits expiring at month end. Fund it with five dollars and you have 500 lookups. The quickstart shows the raw 402 payment challenge if you want to see exactly what your client is paying and why.

What this Instagram data scraper returns without login

Two endpoints cover the Instagram surface. GET /api/v1/instagram/post takes any public post, reel, or IGTV URL (or a bare shortcode via ?code=) and returns views, likes, comments, and the author handle. Reels and videos carry real play counts; photos return views: null because Instagram does not expose photo views to anyone, no matter what a scraper listing promises. GET /api/v1/instagram/user takes a username and returns the full public profile: followers, following, post count, verification, privacy flag, bio. Both are documented with full field semantics in the x402 Instagram API reference.

Because you never log in and never present cookies, there is no account of yours to flag, ban, or checkpoint. The entire category of "my scraping session got my automation account disabled" stops existing on your side of the API boundary.

Pricing that fits how lookups actually happen

Scraper marketplace billing is designed for platforms: monthly plans, prepaid credits, per-compute-unit metering that is hard to predict before a run. Real Instagram lookup demand is bursty. You verify a campaign this week and nothing for a fortnight. You check 40 posts at launch and 40 more at wrap. Per-request pricing fits that shape exactly:

• 1 post: $0.01
• A 50 post campaign audit: $0.50
• Daily tracking of 100 posts for a month: $30
• The month you run nothing: $0.00

And the failure economics are honest: 4xx responses are never charged, a deleted or private post returns a paid but explicit not_found, and upstream failures come back as unpaid 502s. There is no such thing as paying for a run that silently produced an empty dataset.

Built for agents as much as for scripts

The no-account property is not just convenience; it is what makes this an Instagram scraper for AI agents. An autonomous agent cannot complete a marketplace signup, store platform credentials, or size a monthly plan, but it can hold a wallet and sign a one cent USDC payment. Give an agent this endpoint as a tool and it can decide mid-task that it needs a post's numbers, buy exactly that answer, and continue, with its total spend hard-capped by its wallet balance. The agent wallet tutorial has drop-in tool definitions for Claude and LangChain, and llms.txt describes the whole API in plaintext so agents can discover it unaided.

The Apify alternative question, answered directly

People find this page searching for an Apify alternative for Instagram, so here is the honest scorecard. Choose a marketplace platform when you need custom extraction logic, bulk crawls with complex traversal, or data types beyond stats. Choose this API when your need is post or profile stats by URL or handle, when your caller is an AI agent that cannot do signups, or when your volume is too irregular to justify a subscription. The two are not really competitors; one is a workshop, the other is a vending machine. Most stats use cases just need the vending machine.

The same one-request model covers TikTok and X/Twitter, and the universal /api/v1/post endpoint auto-detects the platform from any URL, which makes it the single tool to hand an agent (wiring guide in the agent wallet tutorial). For the deeper story on why no proxies appear anywhere in this architecture, read why your scraper stack needs proxies and an x402 API does not.