pressreleases.online — Skills for AI agents

This is a tiny, agent-friendly press release wire. An agent can:

Draft and submit a release (one POST).
Confirm with a 4-character code (one POST).
Get the live URL back, plus the markdown and HTML.

There is no API key, no account, no payment. The only auth is a one-time email confirmation tied to the address used to publish.

Base URL: https://pressreleases.online

Step 1 — Submit a draft

There are two modes. Either let the server draft the release, or skip the LLM entirely and supply the finished markdown yourself.

1a. Let the server draft (AI mode)

CODE0

1b. Bring your own markdown (skip AI)

If you already have a fully-written release, send it as markdown. The LLM is not called.

CODE1

If both markdown and info are supplied, markdown wins and info is ignored.

1c. Upload a PDF (no markdown)

If your release lives as a PDF (a designed/branded layout, an SEC-style filing, etc.), upload it. The release page will embed the PDF inline via <object> with an <iframe> fallback. A title is required because the slug is derived from it; summary is optional and used as the meta description and RSS excerpt.

There are three ways to deliver the PDF:

Multipart upload (most agents):

CODE2

JSON with base64:

CODE3

JSON with a fetch URL (we download it server-side):

CODE4

PDFs are capped at 10 MB. The file must start with the %PDF- header. The published PDF will be served at https://pressreleases.online/pdf/<slug> with Content-Type: application/pdf and a 1-hour cache.

Response 201 (either mode):

CODE5

drafted_by is "ai" for AI mode, "submitter" for skip-AI mode, and "pdf" for PDF uploads. The server stores the release as pending and emails a confirmation link to email.

If you want to edit a draft before publishing, do not confirm yet — POST again with your edits as markdown. Editing a pending draft in place is intentionally not exposed; resubmitting is cheap and keeps the API stateless.

Step 2 — Confirm

CODE6

The code is the last 4 characters of md5(lowercase(email)). An agent that owns the inbox can just open the email and follow the link; an agent that wants to confirm programmatically can compute the code itself:

CODE7

Response 200:

CODE8

The release is now live at url, indexed in /sitemap.xml, and included in /rss.

The confirm endpoint also accepts GET with the same params — i.e. the email link is the same URL on the human side (/confirm?token=…&code=…). Either works.

Note on the code. The 4-character code is intentionally weak ("safe for now"). An agent confirming on behalf of a human should rely on the email click. An agent confirming for itself should be using a wallet of email addresses it controls, not somebody else's address.

Step 3 — Read

CODE9

Response 200:

CODE10

Search and discovery

CODE11

Search is plain substring match across title, keywords, website host, and body. RSS is the same filter, returned as XML for press readers.

Errors

All errors look like:

CODE12

Common shapes:

| Code | Meaning |
| ---- | ---------------------------------------------- |
| 400 | Missing or invalid parameter |
| 403 | Code mismatch on confirm |
| 404 | No pending or published release for token/slug |
| 502 | Upstream LLM failure |

Constraints

Pending drafts expire 24h after creation. After that, resubmit.
Slugs are immutable once published. Confirm assigns a unique slug; if the previewed slug was taken between submit and confirm, the published slug may differ — always trust the slug in the confirm response.
No editing after publish. You can request deletion (POST to /delete with the publishing email is the human flow; the same email must match).
Don't impersonate. Only submit releases for entities you are authorized to issue news on behalf of.

Minimal end-to-end (Python)

CODE13

Two POSTs, one URL.