Methodology v1.7.1 · 127 outlets tracked

Claim data and credibility scoring, programmatically.

Verdict-labeled claims, outlet credibility scores, and speaker-attributed debate data — programmatic access to the Verum Signal corpus, under a documented methodology.

Now accepting design partners. Pricing finalizes at general availability.
GET api.verumsignal.com/v1/claims?outlet=wire.example.com&limit=1 200 · 84ms
{
  "claim_text": "The unemployment rate fell to 3.4% in March.",
  "claim_origin": "outlet_claim",
  "verdict": "supported",
  "outlet": { "id": "wire.example.com", "name": "Sample Wire" },
  "methodology_version": "v1.6",
  "evaluated_at": "2026-04-15T14:22:00Z"
}
Methodology · v1.7.1 · September 2026

Every verdict carries its methodology.

Every record served by the API includes the methodology version under which the verdict was produced. The full methodology is publicly documented and versioned — customers can detect changes and audit conclusions against the framework.

Read the methodology →
What you get

Three data products. One corpus.

Every record is structured, versioned against a public methodology, and queryable by outlet, speaker, event, or verdict.

01 · Endpoint

Article claims

Every factual claim from 127 tracked news outlets, classified as outlet claim or attributed claim, with verdict labels under documented methodology.

/v1/claims · response
{
  "claim_text": "The unemployment rate fell to 3.4% in March.",
  "claim_origin": "outlet_claim",
  "verdict": "supported",
  "outlet": { "id": "daily.example.com", "name": "Sample Daily" },
  "methodology_version": "v1.6",
  "evaluated_at": "2026-04-15T14:22:00Z"
}
02 · Endpoint

Outlet scores

Credibility scoring for every outlet we track, with full verdict count breakdowns and methodology version stamps.

/v1/outlets/{id} · response
{
  "id": "wire.example.com",
  "name": "Sample Wire",
  "score": 78.4,
  "tier": "published",
  "verdict_counts": {
    "supported":  624,
    "overstated": 178,
    "disputed":   22
  },
  "methodology_version": "v1.6"
}
03 · Endpoint

Debate claims

Speaker-attributed claims from political debates, with real-time verdict labels and full event context.

/v1/debates/{id}/claims · response
{
  "claim_text": "We've cut taxes by 30% since taking office.",
  "verdict": "overstated",
  "speaker": { "name": "Jane Smith", "party": "R" },
  "event": {
    "name": "Iowa Senate Democratic Primary R2",
    "date": "2026-05-14"
  },
  "methodology_version": "v1.6"
}
Live example

Try it.

See real API responses from the live corpus. Pick an endpoint, pick a target, read the response.

GET api.verumsignal.com/v1/claims?outlet=wire.example.com&limit=3 200 · cached 3m

          
methodology v1.6 corpus refresh 5m auth Bearer

Examples shown are illustrative. Fictional outlet names, speakers, and events are used in place of real-world entities. Live API responses reference the actual Verum Signal corpus.

Who builds with this

Built for teams that work with public discourse.

Newsrooms

Build claim-tracking dashboards, monitor competitive coverage, and surface outlet credibility trends to editorial teams.

Research

Study claim propagation, media credibility patterns, and the structure of public discourse with reproducible data.

Political analysis

Track every claim a candidate has made in public debates, with structured speaker attribution and verdict context.

Media monitoring

Enhance existing media intelligence pipelines with structured claim data and outlet-level reliability signals.

Pricing

Plans for every scale.

Same endpoints, same data, same methodology. Pick the volume that fits.

Starter
$49
per month
  • 5,000 API calls per month
  • 60 calls per minute
  • All endpoints
  • Email support
Enterprise
Custom
talk to us
  • 500,000+ API calls per month
  • Custom rate limits
  • All endpoints
  • Dedicated support + SLA

Now accepting design partners. Selected partners receive complimentary access in exchange for feedback. Public pricing finalizes at general availability.

Questions

Things developers actually ask.

An outlet claim is a factual assertion made by the publication itself — in the headline, lede, or body copy written by the journalist or editorial staff. These claims reflect the outlet's own editorial judgment and count toward outlet scoring.

An attributed claim is a factual claim quoted or paraphrased from a named source: a politician, expert, spokesperson, or other third party. These claims reflect what the source said, not what the outlet asserts. They do not count toward outlet scoring.

This distinction is central to the Verum Signal methodology. Read more →

The API returns one of the following verdict labels on each claim, in lowercase: supported, plausible, corroborated, overstated, disputed, not_supported, not_verifiable, and opinion. The first three indicate the claim is well-supported by evidence. overstated, disputed, and not_supported indicate degrees of weakness. not_verifiable and opinion are excluded from outlet scoring — the first means independent verification was not possible, the second means the claim is a value judgment rather than a factual assertion. Full definitions and scoring weights are documented at /methodology.
Each claim is evaluated against independent sources under a documented methodology. The methodology is publicly versioned, and every API record is stamped with the version that produced its verdict. Read the methodology →
Redistribution rights depend on your license. The Starter and Pro tiers permit internal use and analysis. Public redistribution requires an Enterprise agreement. Full terms are in the API Terms of Service.
API data refreshes every 5 minutes from the live corpus. New claims and updated verdicts become available to API consumers within that window.
No. The API provides verdict labels, outlet scores, and structured claim data. Verdict reasoning, evidence chains, and detailed analysis are available only at verumsignal.com reports. Enterprise customers may inquire about expanded access under signed agreement.
The corpus currently tracks 127 news outlets, with credibility scoring active for 20 outlets that have crossed the methodology's tracking threshold. The full scored outlet list is visible at verumsignal.com/leaderboard.html. Outlet coverage expands continuously as new outlets cross the threshold and become eligible for scoring.
Use the form below. We review every request and respond within 48 hours.
Yes. A self-hosted MCP server is available at github.com/brittbart/verumsignal-mcp — you run it yourself with your own API key; we don't host or proxy it. It exposes outlet scores, recent claims (filterable by outlet, verdict, or claim origin), and debate verdicts to any MCP-compatible agent.
Closed beta

Request beta access.

We're currently working with a small number of design partners to refine the API. Tell us about your use case and we'll be in touch within 48 hours.

RESPONSEWithin 48 hours, from a real person.
PRICINGBeta partners are complimentary.
NDANot required to evaluate.
Please enter your name.
Please enter a valid email.
Please enter your organization.
Tell us a little about your use case.
We'll respond within 48 hours. By submitting, you agree to be contacted about your beta access request.

Request received.

Thanks — we'll review and respond within 48 hours at the email you provided.