Checked news, by API.
Ask for a story. Get it back as JSON or a signed webhook, with its sources and check result. Held stories never reach your app.
Base URL: https://api.tlsnewsroom.com
Three calls to your first story.
- 1Get an API keyCreate one in the Console under Integrations. Send it as a Bearer token.
- 2Ask for a storyPOST to /generations with a story type. Add an Idempotency-Key so retries never double-bill.
- 3Read what passedGET /articles for ready stories, or add a webhook and get each one as it lands.
NR=https://api.tlsnewsroom.com/v1/newsrooms/nr_markets # Ask your newsroom for a story curl -X POST $NR/generations \ -H "Authorization: Bearer $NEWSROOM_API_KEY" \ -H "Idempotency-Key: fed-decision-0917" \ -H "Content-Type: application/json" \ -d '{ "output_format": "ticker_card" }' # Then read the stories that passed curl $NR/articles \ -H "Authorization: Bearer $NEWSROOM_API_KEY"
Or let your coding tool do it.
One prompt sets up Newsroom in your project. Copy it into any AI coding tool, or open it straight in Claude, ChatGPT, Cursor, or GitHub Copilot.
Copy the setup prompt, or click a tool to open it there. It builds the client, the feed, and the webhook for you.
- Asks for your API key and keeps it on the server
- Builds a small client for the Newsroom API
- Adds a news feed that shows the AI label
- Sets up a webhook and checks its signature
Every story comes with its proof.
Only stories that passed are in /articles. Here’s what each one carries.
title, summaryThe headline and a one-line summarybody_markdownThe full story, in Markdownsource_urlsLinks to every source it useddisclosureThe AI label to show your readersgate_reportWhat the check found, fact by factevidence_idPull the full evidence from /evidence{
"data": [{
"status": "ready",
"format": "ticker_card",
"title": "Fed holds at 4.25% — fourth straight pause",
"summary": "Futures ticked up 0.3% after the statement.",
"disclosure": "Written by an AI writer",
"source_urls": ["https://www.federalreserve.gov/…"],
"gate_report": { … }
}]
}The calls you’ll use most.
Every route needs your API key. Responses come wrapped in { data, meta }.
Stories
Your newsroom
Set output_format.
ticker_cardTicker, 35–80 words, $0.20feed_itemFeed item, 120–250 words, $0.30briefBrief, 400–800 words, $0.50analysisAnalysis, 900–1,500 words, $10fullFull story, 1,500–2,500 words, $30Signed, and retried.
Each delivery has a Newsroom-Signature header. Check it with your webhook secret, like the Webhook tab above.
article.readyA story passed and is in your feedgeneration.blockedA story was held. Not billedarticle.retractedYou pulled a story backgeneration.failedSomething broke. Not billedYour newsroom, inside your assistant.
The same newsroom and the same check, from the AI tools your team already uses. Until then, the API does it all.
Ask for checked stories from Claude, Cursor, or any MCP client. Your sources, your rules, the same check.
- Ask your AI assistant for a story on your beat
- Read your feed and each story’s sources in chat
- Same check, same price, held stories still free
Build with checked news.
Get a key, ask for a story, and see the sources behind it.