Skip to content

China Intelligence API

China platform intelligence APIs for agents and developer workflows

Get real-time RED trends, KOL data, and China market signals via simple HTTP requests. No accounts. No API keys. Pay per request with x402.

Read the Docs View Pricing

Capability layer

Start with bundled capabilities, then drop into raw route detail as needed

Agents frames the job and workflow. Developers shows the route contract underneath. The wrapper routes below are the shortest path when the caller wants one capability-level response.

$0.63 orchestrated

Brand Visibility Snapshot

/v1/visibility/snapshot

Generate a China brand visibility snapshot with summary assessment, scored strengths and gaps, and priority actions.

Typical wait: about 45s.

Underlying routes: /v1/china/trends, /v1/china/sentiment, /v1/signals/brands/:brand_slug/snapshot

Open capability docs See MCP packaging View agent framing
$0.20 orchestrated

Destination Demand Snapshot

/v1/destination-demand/snapshot

Generate a China outbound destination demand snapshot with demand direction, notable signals, risk framing, and priority actions.

Typical wait: about 15s.

Underlying routes: /v1/market-data/flights/summary, /v1/market-data/spend/trends

Open capability docs See MCP packaging View agent framing
$0.45 direct

KOL Shortlist

/v1/kol/shortlist

Generate a decision-ready China KOL shortlist with creator candidates, selection rationale, risk flags, and next steps.

Typical wait: about 35s.

Underlying routes: /v1/china/kols

Open capability docs See MCP packaging View agent framing

Quickstart

Get data in 30 seconds

Make a paid request by attaching an x402 payment proof in the request header.

  1. 1 Generate a payment proof
  2. 2 Attach it as x402-payment
  3. 3 Parse the standard JSON envelope

Paid Request

bash

curl "https://api.chinamarketing.ai/v1/china/trends?keyword=outbound%20travel&platform=red&timeframe=30d" \
  -H "x402-payment: <payment_proof>"

Paid Response

json

{
  "success": true,
  "data": {
    "keyword": "outbound travel",
    "platform": "red",
    "summary": {
      "momentum": "rising",
      "confidence": 0.74,
      "themes": ["visa-free travel", "short-haul luxury", "Japan itineraries"]
    }
  },
  "meta": {
    "request_id": "req_demo",
    "generated_at": "2026-04-10T12:00:00Z",
    "pipeline_version": "v1"
  },
  "pricing": {
    "amount_usd": "0.08",
    "payment_status": "paid"
  }
}

Try It Now

Try a cached example

Switch between three preloaded routes, adjust a couple of parameters, and copy the curl request. The output shown here is a cached example response so the browser experience stays static-first.

$0.10 /v1/market-data/spend/summary

Country-level spend snapshots for market sizing and monthly planning.

View route docs

Request Curl

bash

curl "https://api.chinamarketing.ai/v1/market-data/spend/summary?country=Japan&month=2026-02" \
  -H "x402-payment: <payment_proof>"

Cached Response

json

{
  "success": true,
  "data": {
    "country": "Japan",
    "source_month": "2026-02",
    "summary": {
      "total_cards": 18422,
      "estimated_average_luxury_spend_cny": 6421.5,
      "estimated_average_accommodation_spend_cny": 3180.2,
      "top_source_city": "Shanghai"
    }
  },
  "meta": {
    "request_id": "req_demo_spend_jp_202602",
    "generated_at": "2026-04-10T12:00:00Z",
    "pipeline_version": "v1",
    "cache_status": "hit"
  },
  "pricing": {
    "amount_usd": "0.10",
    "payment_status": "paid"
  }
}

Payment

How payment works

Each request must include a valid x402 payment proof. If a request is unpaid, the API returns HTTP 402 with machine-readable payment requirements.

Paid request

  • Attach x402-payment: <proof>
  • Receive structured JSON on success

Unpaid request

  • Receive HTTP 402
  • Parse payment requirements and retry

Unpaid Response

json

{
  "success": false,
  "error": {
    "code": "payment_required",
    "message": "Payment is required before this resource can be accessed."
  },
  "meta": {
    "request_id": "req_demo"
  }
}

Context

Why this API exists

China platforms such as RED, Douyin, and WeChat are difficult to access through reliable public APIs, general web search, or standard LLM browsing alone. This API provides structured, normalized outputs for repeated programmatic use, while exposing evidence strength and payment status in a machine-readable way.

Closed-platform intelligence, exposed as stable JSON

Route-specific outputs keep downstream integrations consistent even when retrieval lanes differ behind the scenes.

Curated outputs instead of raw noisy source dumps

The contract compresses scattered evidence into usable summaries, rankings, and weekly snapshots.

Designed for agent loops, automation, and internal tooling

Payment state, request IDs, and envelope structure are meant to fit repeated programmatic use.

API Groups

Start with product families, not a flat endpoint dump

The API catalog is organized by the job a developer is trying to do first: China intelligence, weekly snapshots, destination spend, and flight arrivals.

If Agents frames the capability, the sections below expose the raw routes, request shape, and implementation-level primitives behind it.

Docs + Full Catalog

Go deeper when you need route details, anchors, and full examples

The docs page groups every route by product family, shows the success and unpaid flows near the top, and provides deep links for individual endpoints.

Read the Docs View Pricing

Working Principles

Designed to fit structured agent loops without hiding the commercial layer

Agent-first contracts

Every endpoint returns one envelope style, one pricing object, and one predictable error shape so agents do not need route-specific parsing logic.

Curated signals, not raw dumps

The API compresses scattered China platform signals into decision-ready outputs instead of mirroring noisy source feeds directly.

Paid access with machine-readable controls

Routes are built for payment verification, logging, retries, and later expansion without rewriting the surface area.

Transparent evidence posture

Platform parameters guide retrieval, but evidence quality still governs the output. RED requests currently behave as RED-proxy reads unless stronger native evidence is available.