Apify API
Search Apify Store actors, start actor runs, and fetch results over x402 and MPP.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.01 USDC on Base to 0x23d9…c8411. The signed payment is good for 5 minutes.
- Paid to
- 0x23d9…c8411
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 10000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x23d931f95831cee50b5f5edf4d0e88270f6c8411",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"type": "object",
"required": [
"resultsType",
"searchType",
"addParentData"
],
"properties": {
"search": {
"type": "string",
"description": "Search for Instagram hashtags, profiles, or places. Use `#` for hashtags, e.g. `#travel`."
},
"directUrls": {
"type": "array",
"items": {
"type": "string"
},
"description": "Add one or more Instagram URLs to scrape. URL format must match your content type: /p/ for posts and comments /reel/ for reels /username/ for profile details Leave blank if using the search query instead."
},
"searchType": {
"enum": [
"hashtag",
"profile",
"place",
"user"
],
"type": "string",
"default": "hashtag",
"description": "Hashtag search returns posts tagged with that term. Profile search returns matching accounts. Place search returns matching locations."
},
"resultsType": {
"enum": [
"posts",
"details",
"comments",
"reels",
"mentions",
"stories"
],
"type": "string",
"default": "posts",
"description": "**Posts** returns a feed of content. **Profile, hashtag, or place details** returns metadata about the page: follower count, bio, post count, and profile picture. Comments only work with post URLs, e.g. `instagram.com/p/ABC123xyz/` not `instagram.com/username/`."
},
"searchLimit": {
"type": "integer",
"maximum": 250,
"minimum": 1,
"description": "Set how many profiles, places, or hashtags to find. To limit posts per result, use Results limit per URL. Higher values increase compute usage and cost."
},
"resultsLimit": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Set how many posts or comments to scrape per Instagram URL. Higher values increase compute usage and cost. Maximum 50 comments per post. Instagram may return fewer than 15 comments on some posts. Use `1` to retrieve a single post per page."
},
"addParentData": {
"type": "boolean",
"default": false,
"description": "This applies only to feed items. Adds a dataSource field to each result: profile posts are labeled `profile`, and tag posts are labeled `hashtag`."
},
"onlyPostsNewerThan": {
"type": "string",
"pattern": "^(\\d{4})-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])(T[0-2]\\d:[0-5]\\d(:[0-5]\\d)?(\\.\\d+)?Z?)?$|^(\\d+)\\s*(minute|hour|day|week|month|year)s?$",
"description": "Limit how far back to scrape. Enter a date in `YYYY-MM-DD`, ISO format, or as a relative value, e.g. `1 day`, `2 months`, `3 years`. Times are in UTC, not local time. New York is UTC-5 in winter, UTC-4 in summer. Pinned posts may still appear even with this filter set."
}
},
"description": "Normalized actor input. See field descriptions for the simplified shape; native Apify input also accepted (passed through).",
"additionalProperties": {}
},
"options": {
"type": "object",
"properties": {
"build": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"memory": {
"type": "integer",
"maximum": 32768,
"minimum": 128
},
"maxItems": {
"type": "integer",
"maximum": 100000,
"minimum": 1
}
},
"description": "Optional Apify run options.",
"additionalProperties": false
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-07-21 08:16Z
- Last indexed by Roundhouse
- 2026-07-31 06:10Z
- Last enriched (probe, favicon, geo)
- 2026-09-21 11:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 405
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Apify API and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Apify%20API' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://stableapify.dev/api/actors/apify/instagram-scraper/call, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.