Mosaic reference
Every Mosaic operation, from the registry
3 operations wired in the registry, 3 of them proven by real traffic.
Choose a Mosaic operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Other operations
- Cross-platform search — Cross-platform search as a pipeline: query intent detection, per-source entity resolution (handles are verified before account legs run), fan-out to live sources only, cross-source deduplication, relevance scoring with a floor, and per-source receipts (latency, cost, kept/dropped). A search with nothing relevant returns NO_USEFUL_SIGNAL and charges 0; partial source failures prorate the price. Set estimate=true for a free plan + max-cost preview.
- Creator search — Cross-platform creator discovery over TikTok, Instagram and Threads: unified creator cards with reach, verification and per-card evidence (Threads creators are derived from matching posts and cite them). Every leg is metered, so the flagship fair-use ceiling applies; no creators found charges 0 and failed legs prorate.
- Forum search — Fused forum search across Reddit and Hacker News, merged into one tagged result list. Naver is listed in sources_unavailable pending a keyed official API.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/search to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Mosaic
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Mosaic
3 operationsElsewhere
The same registry, other shapes
- Mosaic overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=search— the same rows to your code at runtime, for 0 credits.