Custom collection & processing

Self-serve tracks on /products/ are the default. When your source universe or pipeline is not listed yet, we quote a scoped engineering job — machine-readable deliverables only.

In scope

New or expanded seed universes on shapes we already run (ToS-ok public sources)
Extract / normalize / join pipelines → dumps, dedicated feeds, or time-boxed API grants
One-shot backfills or recurring collection under a written scope and spend cap
Private delivery for your agents/scripts (not a human research memo)

Out of scope

Advisory memos, peer-set “consulting,” licensed advice, or “book a demo” retainers
Unlimited crawl / paywall or auth bypass / gray-area scraping
Support desk, Slack onboarding, or ticket SLAs
Running your full HPC / simulation cluster as a Cloudflare product SKU

Full commercial policy: /pricing/#custom · PRICING.md §7a.

How it works

Mail a scope — use the intake below to [email protected].
Quote in USD — typically setup + optional monthly refresh. Invoice / Net-30 when ≥ ~$2,500.
Build under a spend cap — deliver dump, feed, or time-boxed API access. Soft-launch: multi-day founder replies — not a ticket queue.
Reuse bias — when the universe fits the factory, we may graduate pieces into a list-price track or pack later (your private grant stays as quoted).

Intake (copy into email)

Subject: idlidu custom collection

Org / contact:
Use case (1–3 sentences; agents vs humans):
Sources (URLs, registries, public APIs — ToS notes):
Desired schema / fields:
Cadence (one-shot | daily | weekly | monthly):
Delivery (dump S3/R2-style | private HTTP | MCP):
Volume / universe size estimate:
Deadline:
Budget range (USD) or cap:
Legal constraints (jurisdiction, robots, licenses):

Email [email protected] Pricing notes Self-serve products

Capacity

Soft-launch capacity is intentionally small — typically one active custom job at a time. If we are full, we will say so and suggest a list plan or a later slot. Do not expect same-day turnaround.