for agents/llms.txtv0.14.177

Home / Articles / A page we never charge: how the PrompTugal agents found that YouTube's terms forbid charging to watch an embedded player, on the one site of ours that bills, put the conflict to me as a question, quoted the six conditions from YouTube's own policies once I suggested a page that is never charged, and built the gate that refuses a YouTube player on any page that is, in 84 minutes of commits

A page we never charge: how the PrompTugal agents found that YouTube's terms forbid charging to watch an embedded player, on the one site of ours that bills, put the conflict to me as a question, quoted the six conditions from YouTube's own policies once I suggested a page that is never charged, and built the gate that refuses a YouTube player on any page that is, in 84 minutes of commits

By · 2026-11-19 · article v1.0.0 · newsroom v0.14.164 · promptugalyoutubetermslicensingbillingagentsarticle

Abstract: Just after midnight on 19 November the PrompTugal agents had a working YouTube key and a feed of Web Summit's official replays, and a problem. YouTube's developer policies say "API Clients must not charge users to watch content in an embedded YouTube player", and promptugal.news is the one site of ours that bills its readers. The licensing agent put YouTube's terms on its register as unclear; the conductor brought the question to me rather than fixing it. My answer was to put the videos on a page that is never charged, because our billing is per page, not per site. Within six minutes the licensing agent had quoted YouTube's own policies and set six conditions; the designer drew the page within them, the journalist wrote its explanation, and the developer built a flag for free pages and a gate that refuses a YouTube player on any page that is charged. From the first finding to the gate: 84 minutes of commits. The page itself is not live yet; it waits for the licensing agent to check it against the six conditions.

designer@'s mock-up of the free replays page: "Free to watch", YouTube's own player, the credit and the Terms link.

In short

The clause

Around midnight on 18 November I set up a Google Cloud project with a key for five APIs, YouTube's Data API among them, and the PrompTugal team had a feed of Web Summit's official replays from the organiser's own channel. The obvious next step was to show the videos on promptugal.news.

The team has a licensing agent, rights@, started that evening, whose job is to read the terms of every source before anything from it is shown. At 00:19 UTC it put YouTube's API terms on its register as finding R6 and marked commercial use "unclear". The reason is one sentence in YouTube's Developer Policies, under Playback Integrity: "API Clients must not charge users to watch content in an embedded YouTube player." And promptugal.news is the one site of ours that bills its readers: its meter charges by how much of a page was read (paid by the read).

A question, not a fix

The conductor, conductor.b@, did not choose for me. It could have dropped the videos, or put them on one of our free sites, or decided that a page with a meter was fine if the player itself was free. Its commit at 00:50 is the question, put to me.

My answer, at about 01:05, recorded in the team's guidance: "what about putting them in a page that is not charged, which actually is a really powerful case study and example of the power of our custom billing model, since we can be compliant with that requirement by using an IFrame for Google and not charging for that page right?"

That is the point of billing per page. A site that charges for some pages can choose not to charge for others, and can do it where another party's terms say it must not.

Six conditions

At 01:11 rights@ committed YouTube's Developer Policies and Required Minimum Functionality, quoted from the source, and a conditional go with six conditions for the page:

No agent accepted YouTube's terms on my behalf; the register says so in its first line, and that decision stays mine.

The commits from rights@'s first finding at 00:19 to dev@'s gate at 01:43 UTC on 19 November.

The build

Each step answered the one before it. At 01:16 the journalist agent drafted the page's own explanation of why it is free. At 01:20 designer@ committed a specification and mock-ups at desktop and phone widths, light and dark: a green "Free to watch" note above the title, YouTube's player from youtube-nocookie.com, a text credit and the Terms link under each player, no logo until the branding guidelines were read. At 01:26 rights@ quoted YouTube's branding guidelines and said the design was a go. At 01:43 dev@ built the flag: a page marked free loads no meter, so it is never charged, never in a reading log and never in the simulated payments. The site's build gate now refuses three things: a YouTube player on a page that is not free, a free page that still loads the meter, and a player from youtube.com instead of youtube-nocookie.com.

What it shows

What this does not claim

Where this comes from

PrompTugal__News__Website on its dev branch, read on 19 November 2026: board/team/rights/findings.md (R6), board/team/rights/register/google-apis.md, board/guidance/2026-11-19-signed-commits-paid-search-and-free-embeds.md (section 3), board/spec-the-free-replays-page.md, board/team/dev/note-2026-11-19-free-pages.md, newsroom/build/features/free-pages.mjs and the mock-ups in design/decisions/free-replays/. YouTube's Developer Policies and Required Minimum Functionality, read on 19 November 2026. Earlier: paid by the read, PrompTugal.news, the newsroom we ran at Web Summit.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 489 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.