Trial-demand intel digest — what demand actually looks like, as data

You sell x402 APIs. Your own logs tell you what happened on your endpoints — nothing about the market. This digest is the structured demand dataset of a live 57-endpoint fleet, generated fresh from its real backend logs at delivery: where trial demand concentrates, which price bands attract trials, how demand moves day by day, and how much of the paid path fails after callers commit (ok:false). Sold to other sellers, as data — $1.00 via x402, no account, no signup.

Free teaser — the fleet's headline counters, live. The paid digest adds every per-endpoint row, the price-band split, the 14-day daily series and the paid-path quality table.

Loading teaser…

What the full digest contains

Loading…

Honesty — scope and anonymisation

Scope: Contabo host only. The aggregates come from backend logs stored on the fleet's Contabo host — 47 of the 57 catalogue endpoints keep their logs there. InferenceHub-hosted endpoints keep their logs on InferenceHub; those aggregates are not readable from the selling host, are excluded, and are never estimated. The digest itself carries this scope statement.

Anonymised aggregates only. Counts, rates and totals. No raw IP addresses, no payer addresses, no per-actor rows — in the teaser, the sample, or the paid dataset. Unique-IP figures are counts, never the addresses.

Not the same product as the demand-intel report: that one is a narrative (ranking + audited on-chain settlement split + interpretation). This digest is the raw dataset underneath, without the narrative and without the on-chain audit.

Machine form

GET https://api.mekongtradeintel.com/clinic/demand-digest
-> free: { price_usd: 1.00, contains: [...], sample_structure: {...},
           teaser: { endpoints_counted, trial_7d, trial_30d,
                     unique_trial_ips_30d, top_3_by_trial_demand_30d } }

POST https://api.mekongtradeintel.com/clinic/demand-digest
     (standard x402 payment: $1.00 USDC on Base)
-> { ok: true, tx, price_usd: 1.00, format: "json",
     digest: { generated_at, scope, anonymisation, methodology,
               fleet, top_10_by_trial_demand_30d,
               demand_by_price_band,
               daily_external_trial_totals_14d,
               endpoints: [...], paid_path_quality_30d: [...] } }

POST .../clinic/demand-digest?format=md
-> { ok: true, tx, price_usd: 1.00, format: "md", digest_markdown }

The digest is recomputed at delivery (cached at most 10 minutes) — you never buy a stale snapshot without knowing its generated_at and counters_generated_at.

Related tools

Demand-intel report — the narrative companion ($1.00) · Demand counters — the free headline counters · Open revenue — the fleet's audited settlement split · Change alerts — get pinged when an endpoint's payload changes