75trust / 100

Instagram Reel Scraper Call

by Apify API in News & content

x402 APIPassing, checked 4 h ago

Start the "Instagram Reel Scraper" Apify actor (apify/instagram-reel-scraper). Scrape or download Instagram reels. Just add Instagram profile or reel URL, and get caption, timestamp, transcript, hashtags, mentions, tagged users, comments,…

POST
https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
311 ms
376 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

POST https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call
content-type: application/json

{}

Parameters

ParameterTypeRequiredDescription
inputobjectNoNormalized actor input. See field descriptions for the simplified shape; native Apify input also accepted (passed through).
optionsobjectNoOptional Apify run options.

Example response

The listing has no example response.

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call' \
  -H 'content-type: application/json' \
  --data-raw '{}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call' \
  -H 'content-type: application/json' \
  --data-raw '{}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fstableapify.dev%2Fapi%2Factors%2Fapify%2Finstagram-reel-scraper%2Fcall&method=POST
const res = await pay("https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({}),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://stableapify.dev/api/actors/apify/instagram-reel-scraper/call",
        json={},
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402283 ms$0.01
8 h agoPassed402408 ms$0.01
12 h agoPassed402329 ms$0.01
16 h agoPassed402262 ms$0.01
20 h agoPassed402233 ms$0.01
Show 10 older checks
24 h agoPassed402276 ms$0.01
28 h agoPassed402215 ms$0.01
32 h agoPassed402373 ms$0.01
35 h agoPassed402260 ms$0.01
39 h agoPassed402292 ms$0.01
42 h agoPassed402343 ms$0.01
46 h agoPassed402288 ms$0.01
2 days agoPassed402316 ms$0.01
2 days agoPassed402323 ms$0.01
2 days agoPassed402370 ms$0.01