Cultural-Data APIs vs. AI Panels vs. Causal Experiments: Which Research Tool Fits Your Decision
A CMO or VP of insights choosing how to justify a launch, message, or positioning decision usually has three kinds of tools on the table, and they answer three different questions. A taste and preference data API tells you what correlates with what. An AI panel tool lets you interview simulated stakeholders and hear what they might say. A causal experimentation platform tells you what happens to real behavior if you take a specific action. Mixing these up is the expensive mistake: treating a correlation or a simulated opinion as proof that a message or launch will move the outcome, then finding out only after the spend is gone.
What a cultural-data API answers
Qloo positions itself as a cultural intelligence layer for AI products. According to its API product page, the platform connects taste and preference signals across categories such as music, film, dining, travel, and brands, and makes that data available through APIs, reports, and data feeds for integration into recommendation engines, personalization systems, and language models. This kind of tool answers "what tends to go with what" for a given audience. It is strongest as an input to a product or model, not as a way to test whether a specific message or launch action will change what someone actually does.
What an AI panel tool answers
A separate category of research tool builds interactive AI-generated stakeholder panels: you interview them, run them through surveys, or convene a group discussion to explore reactions to a concept. These tools are useful for early, open-ended exploration, fast directional feedback, and surfacing objections before a message or concept is fully formed. What they cannot do is establish that a specific action caused a specific outcome: a plausible-sounding answer from an AI panel is still "what might someone say," not evidence of what a market will do under a controlled alternative.
Where a causal experimentation platform fits
Subconscious.ai sits in a third category. It runs randomized experiments on a simulated population to estimate which action drives an outcome for a defined decision, such as a message, a price, a product change, or a launch: if we take this action, what changes, and how confident are we.
The platform can run controlled studies against a person-level audience graph covering 800 million real people, a scale question that is distinct from a recruitable panel. Our best configuration reaches 87% of the measured human ceiling on one study: 0.832 rank correlation against the published human result, where two independent samples of real humans reach 0.959. Across all 43 studies that pass design filters the mean is 0.73. It is a validation result, not a guarantee for a new market; read the methodology at the causal fidelity paper. When a decision needs it, Subconscious can also test or validate a study with real human participants, moving from a simulated experiment to real-human validation without changing the underlying causal question. Details on how a study is scoped and run live at /how-we-work, and published methodology and results live at /research.
Comparing the three categories
| Cultural-data API | AI panel tool | Subconscious | |
|---|---|---|---|
| Core question answered | What correlates with what | What might someone say | Which action changes the outcome |
| Primary output | Taste and preference signals for integration | Simulated interviews, surveys, panel discussion | Causal effect estimate with uncertainty, where supported |
| Best fit | Personalization and recommendation systems | Early-stage, open-ended concept exploration | A defined decision with a specific action to test against an alternative |
| Delivery | API, data feed, or report | Interactive research session | Designed experiment on a simulated market |
| Weak fit | Testing whether a specific message or launch will move behavior | Proving a market-level outcome | Broad, undirected cultural or taste mapping |
Limitations to plan around
Subconscious does not license cultural taste or preference data for personalization or recommendation systems, and it is not a substitute for a preference-data API feeding a model or a recommender. It is also not an interactive interview or panel product built for open-ended qualitative exploration. A causal study needs a defined decision and specific actions to compare against each other, so it is not the right tool for broad, undirected cultural or taste mapping. Confidence intervals, segment breakdowns, and other statistical outputs should only be expected where the specific study design supports them.
Choosing among the three
If the job is enriching a product or model with cultural context, a preference-data API is the right layer. If the job is fast, open-ended exploration of a concept before it is fully formed, an AI panel tool has a place. If the job is deciding whether a specific message, price, or launch action will change real behavior before committing budget to it, that is a causal experiment. Teams that need to make that last call can see how a study gets scoped and run at /demo, or read more about the company at /about.
