timzinin-com Apify Niche Demand Radar API
The Apify Niche Demand Radar API from timzinin-com — 1 operation(s) for apify niche demand radar.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-apify-niche-demand-radar-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Zinin M2M Hub Apify Niche Demand Radar API
description: Pay-per-call data & tool APIs
version: 1.0.0
x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Apify Niche Demand Radar
paths:
/api/apify-niche-demand-radar:
post:
summary: Apify Niche Demand Radar
description: Produce a current demand-direction snapshot for one declared niche using observed public Apify Store user metrics. Public Store API only, no LLM.
operationId: call_apify_niche_demand_radar
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.050000'
protocols:
- x402: {}
network: eip155:8453
payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
requestBody:
required: true
content:
application/json:
schema:
title: Apify Niche Demand Radar input
type: object
schemaVersion: 1
additionalProperties: false
properties:
schemaVersion:
title: Schema version
type: string
description: Contract version.
default: '1.0'
prefill: '1.0'
enum:
- '1.0'
requestId:
title: Request ID
type: string
description: Idempotency key.
editor: textfield
prefill: radar-daily-prefill-001
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,127}$
maxResults:
title: Max results
type: integer
description: Maximum nested results.
default: 10
prefill: 10
minimum: 1
maximum: 100
freshnessMinutes:
title: Freshness minutes
type: integer
description: Maximum cache age.
default: 60
prefill: 60
minimum: 0
maximum: 10080
detailLevel:
title: Detail level
type: string
description: Output detail mode.
default: compact
prefill: compact
enum:
- compact
- evidence
niche:
title: Niche
type: string
pattern: ^(?!.*[\u0000-\u001F\u007F])(?!.*[A-Za-z][A-Za-z0-9+.-]{1,31}:(//|[^\s]+)).*$
description: Declared niche to analyze.
editor: textfield
prefill: store analytics
minLength: 2
maxLength: 120
keywords:
title: Keywords
description: Unique terms for Store matching.
type: array
minItems: 1
maxItems: 10
uniqueItems: true
items:
type: string
pattern: ^(?!.*[\u0000-\u001F\u007F])(?!.*[A-Za-z][A-Za-z0-9+.-]{1,31}:(//|[^\s]+)).*$
minLength: 1
maxLength: 80
editor: stringList
prefill:
- store
- analytics
comparisonWindow:
title: Comparison window
type: string
description: Observed user-metric comparison window.
default: 7d_vs_30d
prefill: 7d_vs_30d
enum:
- 7d_vs_30d
- 30d_vs_90d
required:
- schemaVersion
- requestId
- niche
- keywords
responses:
'200':
description: Actor run succeeded and payment settled
content:
application/json:
schema:
type: object
properties:
results:
type: array
items:
type: object
description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
meta:
type: object
properties:
run_ms:
type: integer
description: Actor run duration in milliseconds
item_count:
type: integer
description: len(results)
settled:
type: boolean
description: Whether the x402 payment was confirmed settled by the facilitator
transaction:
type:
- string
- 'null'
description: On-chain settlement transaction hash, null if unsettled
required:
- run_ms
- item_count
- settled
- transaction
required:
- results
- meta
'400':
description: Malformed PAYMENT-SIGNATURE header or request body
'402':
description: Payment required or invalid — see PAYMENT-REQUIRED header
'409':
description: Payment payload already used
'502':
description: Actor run failed
'504':
description: Actor run timed out
tags:
- Apify Niche Demand Radar