Getting started
Build the first useful baseline
Use the pilot workflow to turn a recurring research question into an agreed market definition and reviewed table.
Documentation
Build on a market that can show its work.
Learn how a Live Market is scoped, how evidence stays attached to every accepted value and how the current view is delivered to your team.
Start here
From a research question to a maintained market.
The useful unit is not a scrape or a list of links. It is an agreed table whose populated values can be inspected, corrected and refreshed.
01
Define the market
Write down what belongs, what does not, which fields matter and what decision the market should support.
02
Review the baseline
Inspect the first rows, tighten the scope and agree the table your team will treat as the accepted view.
03
Check the evidence
Open the source, excerpt and observation time behind a populated value before using it in a decision.
04
Use the updates
Review material changes and export the current table. Automation can be scoped with design partners.
The Live Market model
Evidence is part of the data model, not a footnote.
Each layer answers a different question: what belongs, where an answer came from, how strongly it is supported and what changed after the baseline was accepted.
Brief
An explicit market definition
The inclusion rule, entity shape and requested fields are agreed before collection starts.
Sources
Public evidence with a locator
A source record points to the exact page, excerpt or timestamp and records when it was observed.
Claims
Supported, inferred or conflicting
Values stay connected to their supporting claims. Inference and disagreement remain visible.
Market
A current view with history
Accepted rows form the live table; material before-and-after events explain what moved.
Market brief
Define usefulness before collecting rows.
- An inclusion rule that says what belongs
- An entity shape: company, person or claim
- The fields needed for a real decision
- Sources and exclusions that need special handling
Evidence record
supported{
"field": "enterprise_price",
"value": "£2,600/month",
"claim_ids": ["clm_0388"],
"observed_at": "2026-08-05T08:47:00Z",
"confidence": "high",
"inferred": false,
"status": "current"
}The supporting claim carries its exact source locator and excerpt. A field without support remains empty.
Explore the documentation
The operating guide for a trustworthy market.
Evidence and quality
Know what every value rests on
Understand citations, observation time, confidence, inference, conflicts and the correction trail.
Delivery
Use the market where work happens
The standard pilot delivery is a reviewed live table, change briefs and a clean CSV export.
Quality rules
What the table must never hide.
No unsupported cells
Every populated value points to at least one supporting claim.
Identity is not inferred
Core identity fields come from evidence, not model guesswork.
Conflicts stay visible
Credible disagreement is preserved and marked for review.
Corrections keep history
New evidence supersedes an old claim without erasing what was observed.
For builders and agents
Design-partner capabilitiesBring cited market context into an existing workflow.
Standard pilots ship a live table, change briefs and CSV. API, MCP and webhook access are currently scoped with design partners whose workflows help define the production contract.
API access
A query or export surface for a customer-specific Live Market can be scoped with design partners. The resources, fields and access model are agreed as part of that engagement.
MCP for agents
Design partners can help shape an MCP surface for reading current, cited market context. It is not presented as a standard self-serve capability of every pilot.
Change webhooks
Event delivery for agreed material changes can be designed with partners whose workflow needs it. Payload and delivery guarantees are confirmed before use.
Delivery today
A useful surface before a larger integration.
Live table
The accepted current view, with evidence available for review.
Change briefs
Two concise updates during the pilot on material movements.
CSV export
A clean copy of the current table that your team can keep.
Documentation questions
The precise version.
What is included today?+
The guided pilot includes an agreed market definition, reviewed source-backed rows, customer-specific fields, two change briefs and a clean CSV export over 14 days.
Is this documentation an API contract?+
No. The Live Market model on this page explains how the product is structured. API, MCP and webhook contracts are currently agreed with individual design partners before implementation or production use.
What counts as evidence?+
A populated value should point to a supporting claim, and that claim should carry an exact source locator, a supporting excerpt and the time it was observed. Unsupported fields stay empty.
How are corrections handled?+
A correction should preserve what was previously observed and add the replacement evidence. Conflicts and inference remain labelled rather than being silently rewritten as fact.
Need a market-specific answer?
Bring us the brief your team keeps rebuilding.
We will help define the scope, return reviewed source-backed rows and document exactly what the first Live Market includes.