# Issue 3: Pay after you read: a newsroom that charges for the share you read, lets you go below zero, and keeps your persona, SGit Newsroom

> What would you pay for an article if you only paid after reading it, and only as much as it was worth to you? On 10 October the reading meter on this site went from a demonstration to a working answer, one release at a time. You pay for the share of a page you scroll through. You say how useful it was, and that sets the price, from free to double. Your balance can go below zero without a word of nagging. And your reading builds personas that are yours, kept in your browser, that a link can share. Eight articles: the plan, the numbers we will be judged on, who could cheat it, why readers should pay because it helps them, and why agents will pay too.

*Source: <https://newsroom.sgit.ai/articles/newsletter/2026/10/11/003-pay-after-you-read.html> · sgit.ai v0.7.51 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../../../../../index.md) / [SGit Newsroom](../../../../index.md) / [Newsletter](../../../index.md) / Issue 3

SGit Newsroom · Issue 3 · 2026-10-11

# Pay after you read: a newsroom that charges for the share you read, lets you go below zero, and keeps your persona

By [Dinis Cruz](https://sgit.ai/about/index.md), written with the [Journalist](../../../../../newsroom/roles/journalist.md)

***Abstract:** What would you pay for an article if you only paid after reading it, and only as much as it was worth to you? On 10 October the reading meter on this site went from a demonstration to a working answer, one release at a time. You pay for the share of a page you scroll through. You say how useful it was, and that sets the price, from free to double. Your balance can go below zero without a word of nagging. And your reading builds personas that are yours, kept in your browser, that a link can share. Eight articles: the plan, the numbers we will be judged on, who could cheat it, why readers should pay because it helps them, and why agents will pay too.*

What would you pay for an article, if you only paid after you had read it, and only as much as it was worth to you? On 10 October the reading meter on this site went from a demonstration to a working answer, built and tested one release at a time. This issue is that story, in eight articles. It is the first of three on what was published between 9 and 11 October; the next two are about [authority outside the model](https://newsroom.sgit.ai/articles/newsletter/2026/10/11/004-authority-outside-the-model.html) and about [a newsroom with no server](https://newsroom.sgit.ai/articles/newsletter/2026/10/11/005-no-server-by-design.html).

The reading meter in six pictures, one from each of the articles that built it

## Seven releases in an afternoon

[A meter in the browser](https://newsroom.sgit.ai/articles/a-meter-in-the-browser.html) started it: every page a few pence, from five pounds of credit kept in the reader's browser, with no account and nothing sent anywhere. By the end of the afternoon it was something else, and [pay after you read](https://newsroom.sgit.ai/articles/pay-after-you-read.html) tells how, in seven releases in under four hours, each one coming from using the one before:

>

You pay after you see the value.

You pay for the share of a page you scroll through, not for opening it. At the foot of each article you say how useful it was, and that sets the price, from free to double. Your balance can go below zero and stay there; nothing is blocked and nothing nags.

The reader card at the foot of an article: what it has cost, how much was read, and the choice not to pay.

## The numbers, written down first

[Going live with the reading meter](https://newsroom.sgit.ai/articles/going-live-with-the-reading-meter.html) is the plan and the business case: why below zero is allowed when most reader-funded sites count your articles and ask, what a subscription commits you to, what Stripe takes from a five-pound payment, and five hypotheses, with the number that would prove each one wrong, written down before the first payment.

>

And going below zero is not a failure state.

Six changes, and five hypotheses written down before the first payment, each with what we expect and what would prove us wrong.

The payment link is now live, so the eight weeks have started; the hypotheses will be reviewed on 6 December.

## Who could cheat it, and why that is allowed

Everything the meter knows is in the reader's browser, so anyone can change it. [Who will game the reading meter](https://newsroom.sgit.ai/articles/who-will-game-the-reading-meter.html) goes one level below "who are you protecting against": eight kinds of reader, from engineers who are invisible by habit to people who can barely click, none of them attackers, and nine ways to cheat, each of which changes a number only the cheater can see. The risks that will actually happen are quieter. Its sharpest line is about agents, which move between kinds of reader in a single request:

>

An agent is not a step; it is a lift.

## Pay because it helps you

[Pay to keep your persona](https://newsroom.sgit.ai/articles/pay-to-keep-your-persona.html) is the value proposition underneath. Paying because you have to, because you are made to feel you should, or because it is the right thing to do works to a degree, and does not scale. What a reader would pay for is what helps them: time, context, focus, and a persona built from their reading that follows them between devices.

>

The reader should pay because paying helps them.

A newsroom of your own: picks for each persona, the graph of what you read, and the personas you keep

[A link to a persona](https://newsroom.sgit.ai/articles/a-link-to-a-persona.html) is the next step, written as a brief. Personas kept in a vault by the newsroom's own agents, so that a link can open the newsroom as a CISO, a data protection officer or one particular person, and the reader can follow the persona or make it their own:

>

The better move is for the person who sends the link to choose it

## And the agents will pay too

[The agent is the reader](https://newsroom.sgit.ai/articles/the-agent-is-the-reader.html) turns the question around. Agents already pay, in tokens, to read the raw web and guess what it means. A curated graph of an article answers a question about one of its concepts in a median of 2,579 tokens, against 25,698 to read the five articles behind it, and comes with citations:

>

If a publisher saves an agent more tokens than it charges, paying is rational.

[Open source is not free](https://newsroom.sgit.ai/articles/open-source-is-not-free.html) is the same question for software: who pays to keep the old versions working, measured from public data, with five ways to pay for it simulated. Its finding for pence is the one the meter is built on:

>

Pence only work aggregated.

## The eight articles

### The meter

From a few pence a page to paying after you read, and the plan it is judged by.

- [**A meter in the browser: a penny a page, a history you keep, and a site that picks for you**](../../../../a-meter-in-the-browser.md). Every page now costs a few pence from £5 of credit kept in your browser, and the reading history it keeps is what personalises the site.
- [**Pay after you read: how a reading meter became a working business model in one afternoon, one release at a time**](../../../../pay-after-you-read.md). Seven releases in one afternoon turned the reading meter into a working model: pay after you read, and the rating sets the price.
- [**Going live with the reading meter: pay for what you read, go below zero if you like, and the numbers we will check in eight weeks**](../../../../going-live-with-the-reading-meter.md). Pay for the share of a page you read, go below zero with no nagging, top up £5 on Stripe: the plan, and the numbers we check in eight weeks.
- [**Who will game the reading meter? Eight kinds of reader, nine ways to cheat, and the risks that will actually happen**](../../../../who-will-game-the-reading-meter.md). Eight kinds of reader, none of them attackers, nine ways to cheat a browser meter, and the quieter risks that will actually happen.

### Your persona

Why readers would pay, and a link that opens the newsroom as someone.

- [**Pay to keep your persona: readers should pay because it helps them, not because they feel they should**](../../../../pay-to-keep-your-persona.md). Readers should pay because it helps them: a persona with a name and a graph, several for focus, and one that follows you between devices.
- [**A link to a persona: send people to the newsroom as someone, not as nobody**](../../../../a-link-to-a-persona.md). Send a CISO to the newsroom as a CISO: personas kept in a vault by the newsroom's agents, opened from a link, followed or forked.

### Who else pays

Agents that pay to save tokens, and the long tail of open source.

- [**The agent is the reader: why agents will pay for graphs, personas and signed claims, because it is cheaper than not paying**](../../../../the-agent-is-the-reader.md). Agents pay to read the raw web and guess its meaning. A curated graph answers for 90% fewer tokens, so paying the publisher is cheaper than not paying.
- [**Open source is not free: who pays to keep the long tail working?**](../../../../open-source-is-not-free.md). An old iMac, the long tail of old versions that projects are not paid to support, measured from public data, and five ways to pay for it, simulated.

*This is issue 3 of the SGit Newsroom newsletter, also published on LinkedIn in [Deterministic GenAI](https://www.linkedin.com/newsletters/deterministic-genai-7174563523795005440/). Every article it links to is on [sgit.ai](https://newsroom.sgit.ai/articles/index.html), with its sources and its data. To get the next issue by email, [subscribe at sgit.ai/subscribe](https://newsroom.sgit.ai/subscribe/).*

**Posting this issue on LinkedIn?** The cover is [003-pay-after-you-read.jpg](../../../../banners/003-pay-after-you-read.jpg) (1920×1080, title and key ideas on it). Upload it as the article cover, paste the title, then select and copy the body from this page. LinkedIn drops images from a paste, so add these where they appear, in this order, with the caption under each:

1. [003-2026-10-11-meter.jpg](../../../../banners/collages/003-2026-10-11-meter.jpg) The reading meter in six pictures, one from each of the articles that built it
2. [gl-line.webp](../../../../images/gl-line.webp) The reader card at the foot of an article: what it has cost, how much was read, and the choice not to pay.
3. [gl-anchors.webp](../../../../images/gl-anchors.webp) Six changes, and five hypotheses written down before the first payment, each with what we expect and what would prove us wrong.
4. [003-2026-10-11-personas.jpg](../../../../banners/collages/003-2026-10-11-personas.jpg) A newsroom of your own: picks for each persona, the graph of what you read, and the personas you keep

[← All issues](../../../index.md)


---

*[Site index for agents](../../../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/newsletter/2026/10/11/003-pay-after-you-read.html)*
