Apify API
Search Apify Store actors, start actor runs, and fetch results over x402 and MPP.
SearchLiveeip155:8453Exactvia cdp
Actors
Calls · 30d
2→ 0%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 14 snapshots so far.
$9.49
Verified settled volume
631 settlements proven x402 by their on-chain EIP-3009 marker.
$0.010
Listed price
As published in the catalog. Always read the live 402 before paying.
2
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-08-07 22:02Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x23d931f95831cee50b5f5edf4d0e88270f6c8411The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Provider
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.
0.01USDC≈ $0.01 USD
on Base · exact scheme
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": [
"listingType",
"extractionMethod",
"sort"
],
"properties": {
"bbox": {
"type": "object",
"required": [
"west",
"east",
"south",
"north"
],
"properties": {
"east": {
"type": "number",
"maximum": 180,
"minimum": -180
},
"west": {
"type": "number",
"maximum": 180,
"minimum": -180
},
"north": {
"type": "number",
"maximum": 90,
"minimum": -90
},
"south": {
"type": "number",
"maximum": 90,
"minimum": -90
}
},
"description": "Map bounding box. Server builds the searchQueryState URL.",
"additionalProperties": false
},
"sort": {
"type": "string",
"default": "globalrelevanceex",
"minLength": 1,
"description": "filterState.sort.value (e.g. globalrelevanceex, days, priorityscore)."
},
"maxItems": {
"type": "integer",
"maximum": 100000,
"minimum": 1,
"description": "Lifted into options.maxItems."
},
"searchUrls": {
"type": "array",
"items": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri"
}
},
"additionalProperties": false
},
"description": "Native Apify input. If provided, takes precedence over bbox/listingType. URLs MUST contain a `?searchQueryState=...` query param."
},
"listingType": {
"enum": [
"for_sale",
"for_rent",
"sold"
],
"type": "string",
"default": "for_sale",
"description": "Listing category to filter for."
},
"extraFilterState": {
"type": "object",
"description": "Extra filterState entries merged into the searchQueryState. Use for price/beds/etc.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"extractionMethod": {
"enum": [
"PAGINATION_WITH_ZOOM_IN",
"PAGINATION",
"MAP_MARKERS"
],
"type": "string",
"default": "MAP_MARKERS",
"description": "MAP_MARKERS is fastest for bbox searches (single request, capped at ~500 markers). PAGINATION variants walk the result pages."
}
},
"description": "Normalized actor input. See field descriptions for the simplified shape; native Apify input also accepted (passed through).",
"additionalProperties": false
},
"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-08-07 22:02Z
- Last indexed by Roundhouse
- 2026-09-06 21:50Z
- Last enriched (probe, favicon, geo)
- 2026-09-12 09:45Z
- 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
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 14 snapshots so far. 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/maxcopell/zillow-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.