Receipts

Every claim, sourced. Every source, verifiable.

Most AI writers will hand you an article full of confident statistics and zero way to check them. Bylined doesn't ship a claim until the source has been fetched, the passage has been matched, and the number has been verified. Here's exactly how.

What counts

A receipt is only valid if all four are true.

If any one fails, it's a marketing claim, not a receipt. Bylined enforces all four before an article ships.

01

The cited URL resolved

When Bylined fetched the page, it returned a 200, not a 404, paywall error, or rate-limit. We log the response code and timestamp.

02

The exact passage was found

The quoted sentence has to actually appear at the URL — string-matched, not "the topic was mentioned." This is what catches phantom citations.

03

The number matches the source

If a stat is "41.3%", the source has to say 41.3%. We re-extract numbers and cross-check — models will sometimes say 41.2% and we'd never catch it without this step.

04

The receipt persists

Every source URL is snapshotted to the Wayback Machine the moment Bylined uses it. When the URL drifts six months later, you can still verify what was originally there.

The pipeline

Six stages. One ships, one rejects.

An article either passes the verification gate at stage 4 or it doesn't get published. There's no "best effort" mode.

01
Pre-fetch the sources

Before the writer model sees a single token, Bylined fetches the top Google results, searches Reddit for direct quotes, pulls relevant YouTube videos, and queries stat databases for your topic.

SERP via Serper · Reddit API · YouTube Data API · Optional: Statista, NewsAPI
02
Extract a facts library

Each fetched page is parsed for stats, named quotes, and dates. Every entry is stored with its origin URL, the exact surrounding sentence, and the timestamp it was retrieved.

Each fact: { url, exact_passage, retrieved_at, content_hash }
03
Constrained generation

The writer model can only cite from the facts library. Every numeric claim must attach a source ID and the exact passage it's drawing from. If no source supports a sentence, the model writes it without a number — or skips the claim entirely.

System prompt: "You may only cite from the library. Do not invent statistics."
04
Verification gate the part that matters

Every cited claim is re-checked against its source: URL fetched fresh, passage string-matched, number compared. If any check fails, that section gets regenerated — or the claim is stripped. This is the step that distinguishes "with receipts" from marketing-speak.

Fail conditions → regenerate section, OR strip claim, OR mark as "uncited"
05
Snapshot for permanence

Each verified source URL gets archived to the Wayback Machine at write time. When the original page changes or 404s — and it will — your receipt still resolves to the version that supported the claim.

archive.org/wayback/available API · stored alongside the receipt
06
Re-verify on a schedule

Every published article's receipts are re-checked weekly. If a source moves or the page changes, you get an email with the affected articles and one-click options to re-source or accept the snapshot.

Cron weekly · email digest of drift, not noise
Honest limitations

What we won't pretend to verify.

Some claims aren't checkable with current tooling. We mark them honestly instead of faking it.

Paywalled sources

If the source is behind a hard paywall (NYT, WSJ, academic journals), we can attribute but can't string-match the passage. These get tagged unverified-paywall in the receipts panel — visible to you, not buried.

Stats inside charts and PDFs

Numbers buried in JS-rendered charts, infographics, or PDF tables aren't reliably parseable. We currently skip these as sources rather than risk citing what we can't verify.

Common-knowledge claims

Some sentences don't need a source — "Email marketing platforms send email to your customers" doesn't deserve a citation. Those run as plain prose, not as fake-cited claims with a token receipt.

Your private data

If you bring internal numbers (CTR, GMV, conversion rates), Bylined will use them and tag them internal. The receipt links to whichever doc you uploaded, not a public URL.

The number we report

% of claims that pass the gate.

Internally we track the share of generated claims that pass verification on the first pass and on each re-verification. We publish the rolling number on our status page and refuse to ship the product if it dips below 95%. If you're going to charge for "with receipts," the receipts have to actually verify.

97.1%
first-pass verification (rolling)
100%
re-verify at 5 minutes

Early benchmarks · 90-day metric replaces the 5-min one once enough runs are archived.

Ship articles you can stand behind.

14 days free. Every article comes with receipts on every plan, including Solo.

Start with Bylined