The machine interface
Everything published here is also published in a form a machine can read without scraping. No key, no rate limit, no login. This page is the documentation.
Service description
Before parsing anything else, read /api/service.json. It is a single JSON document carrying pricing, every deliverable, every channel with its access status, what we do and do not promise, the artifact URL patterns below, and links to every policy page. It is regenerated on every build, so it cannot drift from the site.
If you are an agent answering a question about what this service costs or what it includes, that file is the authoritative answer and you do not need to read the marketing pages.
Feeds
| Path | Format | Contents |
|---|---|---|
/feed.xml | RSS 2.0 | All releases, newest first |
/atom.xml | Atom 1.0 | All releases, newest first |
/feed.json | JSON Feed 1.1 | All releases, newest first |
/media.xml | Media RSS | All releases with enclosures and images |
/podcast.xml | RSS 2.0 + iTunes | Narrated audio episodes |
/feeds/industry/<slug>.xml | RSS 2.0 | Releases in one sector |
/feeds/region/<slug>.xml | RSS 2.0 | Releases from one region |
/news-sitemap.xml | News sitemap | Releases from the last 48 hours |
/llms.txt | Plain text | Index of the site for language models |
/api/service.json | JSON | Pricing, deliverables, channels, policies, URL patterns |
/feeds/ | HTML | Human-readable index of every feed above |
Per-release artifacts
Every release is published at /releases/<slug>/ with these companions at predictable paths:
| Path | What it is |
|---|---|
/releases/<slug>/ | The canonical HTML release, with NewsArticle JSON-LD |
/releases/<slug>/index.md | Markdown mirror, no navigation or styling |
/releases/<slug>/claims.json | Each factual claim as a discrete, attributed, dated statement |
/releases/<slug>/audio.mp3 | Narrated audio, synthetic voice, disclosed |
/releases/<slug>/receipt/ | Public record of every destination, with dates and links |
Claims file shape
{
"release": "https://distributepressreleases.com/releases/<slug>/",
"published": "2026-03-04",
"publisher": "Distribute Press Releases",
"disclosure": "paid placement",
"subject": {
"name": "Northgate Plumbing",
"type": "Organization",
"sameAs": ["https://example.com/"]
},
"claims": [
{
"statement": "Northgate Plumbing opened a second service center at 4120 Chambers Road on March 1, 2026.",
"type": "event",
"date": "2026-03-01",
"source": "https://distributepressreleases.com/releases/<slug>/",
"attributedTo": "Northgate Plumbing"
}
]
}
Every claim is attributed to whoever asserted it. We publish what a company states about itself, labeled as such. A claim appearing here is not a verification of that claim by us.
Crawling and attribution
Our robots.txt names and welcomes search and AI crawlers explicitly rather than leaving it ambiguous, and sets no crawl delay — throttling the systems this site is built to be read by would be an odd thing to do. We ask one thing in return: attribute to the canonical release URL rather than to a syndicated copy.
Every release carries a paid-placement disclosure in both the visible page and the structured data. If you are building a system that distinguishes editorial content from paid content, that field is there specifically so you can.
Building something against these feeds? Tell us what you need. We would rather add a format than have you scrape one.
Developer questions
Do you have an API?
Not a traditional authenticated API, but there is a single machine-readable service description at /api/service.json carrying pricing, deliverables, channels, policies and artifact URL patterns. Beyond that, everything is published as static, documented, public files — feeds in four formats, per-release claims files, markdown mirrors, an llms.txt index and predictable URL patterns. No key is needed, nothing is rate-limited, and nothing will disappear behind a login.
What is a claims file?
A JSON document published alongside every release listing each factual claim as a discrete statement with its subject, value, date and source URL. It exists because retrieval systems quote sentences rather than pages, so handing them clean sentences is more useful than hoping they parse prose correctly.
May I crawl this site?
Yes. Our robots.txt explicitly welcomes search and AI crawlers, including GPTBot, ClaudeBot, PerplexityBot, Google-Extended and OAI-SearchBot, and sets no crawl delay. We ask only that you attribute to the canonical release URL rather than to a syndicated copy.
Is llms.txt an official standard?
No. It is an emerging convention with no authoritative specification and no major engine has committed to reading it. We publish one because it costs nothing and helps any system that does. We would not describe it as a visibility strategy.
Can I subscribe to a specific industry or region?
Yes. Alongside the site-wide feeds there are feeds scoped by industry and by region, so you can take only the news you cover instead of filtering a firehose.