Run the engine

1Playground

The prefilled example demonstrates the guarantees: four independent origins report the same event (count climbs to CONFIRMED), a repeat from reuters adds nothing (G3), and the single-origin story stays bare (G5). Edit freely — it is the live engine.

2What a call computes

An anonymous call is batch-scoped and stateless: corroboration is computed across the claims you send in that request (titles that describe the same event merge via the dual gate; origins are counted distinct). Nothing is stored between calls — firstSeenAt equals the request time, and no data you send is retained.

That makes the anonymous tier ideal for evaluating the engine and for “given these N reports, what corroborates what?” batch questions. If you need persistent event memory — first-seen timelines that survive across requests — send an API key (§9), or run @sourcedhq/core yourself with a store (one load()/save() pair, any KV; see the spec §3).

3Request schema

POST /api/v1/assess with content-type: application/json (optional Authorization: Bearer sk_src_…):

4Response schema

200 OK, JSON:

5Config keys

Numeric keys only; anything else is ignored. Values are clamped to the ranges below. The defaults are the honesty contract — tighten freely, loosen knowingly (spec §5).

6Errors & limits

• No authentication required, CORS fully open — call it straight from a browser. Anonymous: 60 requests/minute per IP. Keyed: 600/minute.
• /api/v1/… paths are frozen — v1 never breaks. (/api/assess and /api/verify remain as aliases.) Every response carries X-Sourced-Api and X-Sourced-Engine.
• Malformed individual claims never fail the request: they come back as null verdicts (G7). Only a malformed envelope is a 400.
• GET /api/v1/assess returns a machine-readable usage summary; the full contract is OpenAPI 3.1.
• POST /api/v1/verify is also served on this host — verify transparency chains programmatically (schema in the OpenAPI file; human verification with receipts lives at sourced.network).
• Fair use: the anonymous tier is a free evaluation endpoint, not an SLA. High-volume or persistent workloads: an API key, or run the engine yourself.

7Examples

curl -s https://sourced.run/api/v1/assess \
  -H "content-type: application/json" \
  -d '{
    "claims": [
      {"id":"a","title":"Major dam breach reported upstream","origin":"reuters","publishedAt":"2026-07-10T21:00:00Z"},
      {"id":"b","title":"Major dam breach reported upstream","origin":"bbc","publishedAt":"2026-07-10T21:04:00Z"}
    ]
  }'

const res = await fetch("https://sourced.run/api/v1/assess", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({ claims }),
});
const { verdicts } = await res.json();
// verdicts[i] belongs to claims[i]

import requests

r = requests.post(
    "https://sourced.run/api/v1/assess",
    json={"claims": [
        {"id": "a", "title": "Major dam breach reported upstream",
         "origin": "reuters", "publishedAt": "2026-07-10T21:00:00Z"},
        {"id": "b", "title": "Major dam breach reported upstream",
         "origin": "bbc", "publishedAt": "2026-07-10T21:04:00Z"},
    ]},
    timeout=10,
)
verdicts = r.json()["verdicts"]  # verdicts[i] belongs to claims[i]
# verdicts[1] -> {'corroboration': 2, 'corroboratingSources': ['reuters'], 'signal': 'breaking', ...}

8For AI agents (MCP)

Sourced ships as an MCP server — agents get the primitive as native tools: assess (with session memory: corroboration and first-seen accumulate across calls), verify_chain and run_conformance. The server identifies itself as sourced.

# Claude Code
claude mcp add sourced -- npx -y @sourcedhq/mcp

# any MCP client (config JSON)
{ "mcpServers": { "sourced": { "command": "npx", "args": ["-y", "@sourcedhq/mcp"] } } }

Machine-readable summaries of all three surfaces live at /llms.txt on each domain. This endpoint itself is agent-friendly by design: no auth required, CORS open, JSON in/out, GET returns usage.

9API keys — persistent memory

The anonymous endpoint is a calculator: it answers for the batch you send and forgets you. A key gives the same endpoint a memory. Send it on any call:

Authorization: Bearer sk_src_…

What changes — precisely:

The event store keeps derived working state (event keys, counts, first-seen times), retires events after 36 h into nothing — this hosted tier stores no archive of your content. Keys are issued manually while Sourced is young: hello@tickwire.news. Same engine, same guarantees G1–G7 — a key never changes verdict semantics, only how long the engine remembers.

10Chain-as-a-service

Every key owns a hash-chained transparency log — the same construction Tickwire runs in production (proof). Commit anything you want to be held to — e.g. a digest of each verdict batch you publish:

# append (writes need YOUR key)
curl -s -X POST https://sourced.run/api/v1/chain \
  -H "authorization: Bearer sk_src_…" \
  -H "content-type: application/json" \
  -d '{"payload":{"batch":"2026-07-11T21:00Z","digest":"…"}}'

# read (public — that is the point)
curl -s "https://sourced.run/api/v1/chain?chain=<chainId>&full=1"

# directory of all hosted chains
curl -s https://sourced.run/api/v1/chains

Each append returns a LogRecord whose hash commits to the entire history before it. Reads are public and CORS-open so anyone can fetch your chain and recompute it (POST /api/v1/verify, or in the browser at sourced.network). Heads are anchored daily into public git history (anchors/) — after that, neither you nor we can rewrite a single record unnoticed. Your chainId is derived one-way from your key: publishing it is safe, writing stays yours alone.

Limits: 32 kB payload · 30 appends/min · 5000 records/month. This is what “Built on Sourced” means operationally: your claims history becomes checkable by strangers, not just asserted by you.