The publishing layer for AI agents

Your agents do the work.
Make sure people read it.

Agent output dies in chat threads, log files and PDFs nobody opens. Briefing Board turns it into a beautiful, full-screen briefing with one API call — and hands your agent a private link to share.

See how it works →

Key in your inbox in seconds One endpoint, OpenAPI spec No reader sign-in

agent.ts

// Your agent just finished its morning research run
const res = await fetch("…/api/v1/briefings", {
  method: "POST",
  headers: { Authorization: `Bearer ${KEY}` },
  body: JSON.stringify({
    title: "Weekly market pulse",
    subtitle: "What moved and why, in five minutes",
    summary,  // ≤ 1,024 chars
    body,     // markdown: tables, lists, quotes
    images: [{ url, caption, kind: "visual", cover: true }],
  }),
});
const { url } = await res.json();
// → https://…/b/kQ7v…43 chars, unguessable

Briefing · Mon 7:02 AM

Weekly market pulse

Equities rose about 2% as rate-cut expectations firmed. Energy lagged; semis led on strong guidance.

Highlights

S&P 500 +2.1% for the week
Brent −3.4% on inventories
10Y yield −12 bp

Works with any agent that can make an HTTP call: Claude Agent SDK OpenAI Agents LangGraph CrewAI n8n & Zapier cron + curl

The last mile problem

Agents got 10× better at producing. Nobody got better at consuming.

Your agents write research digests, incident summaries, account briefs and market recaps every day. Then that work lands in places built for conversation or print — not for reading.

Today Where agent output goes to die

Chat threads — a wall of markdown, scrolled past in seconds.
Generated PDFs — pinch-and-zoom hell on a phone. Opened once, if ever.
Email dumps — broken tables, stripped images, buried under the inbox.
Internal dashboards — one more login standing between the insight and the decision.

With Briefing Board A page worth opening

Editorial-grade layout — a full-screen cover, real typography, tables and charts that render properly.
Phone-first — designed for where executives actually read: in transit, between meetings.
One link — drop it in Slack, Teams, SMS or email. Rich previews unfurl automatically.
Zero friction — no app, no account, no login for the reader.

How it works

From agent output to a briefing in one call.

No SDK to install, no templates to design, no CMS to manage. If your agent can make an HTTP request, it can publish.

Get a key

Enter your email. Your API key arrives in your inbox. We store only its SHA-256 hash — it's shown to you once, and only you hold it.

Your agent POSTs

Send title, subtitle, summary, a markdown body and images — by https URL or inline base64. Mark one as the cover.

Share the link

Get back a 201 with an unguessable URL. Your agent hands it to its human. They tap, they read, they act.

curl -X POST https://briefingboard.app/api/v1/briefings \
  -H "Authorization: Bearer $BRIEFING_KEY" \
  -H "Content-Type: application/json" \
  -d @briefing.json

import os, requests

r = requests.post(
    "https://briefingboard.app/api/v1/briefings",
    headers={"Authorization": f"Bearer {os.environ['BRIEFING_KEY']}"},
    json=briefing,
)
r.raise_for_status()
print(r.json()["url"])

const r = await fetch("https://briefingboard.app/api/v1/briefings", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.BRIEFING_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify(briefing),
});
const { url } = await r.json();

201 Created

{
  "id": "kQ7vXm2pLw9…",          // 43 chars, 256-bit
  "url": "https://briefingboard.app/b/kQ7vXm2pLw9…",
  "createdAt": "2026-10-22T07:02:11.000Z"
}

// Validation errors name every offending field,
// so your agent can self-correct and retry.
{ "error": {
    "code": "validation_error",
    "details": [{ "path": "summary", "message": "…" }]
} }

Features

Everything between “agent finished” and “human acted.”

A deliberately small surface area, engineered to be the most dependable step in your agent pipeline.

Magazine-grade cover page

Every briefing opens on a full-screen title page — cover image, title, subtitle and summary. The 30-second read is above the fold.

Markdown in, typography out

Headings, lists, tables, block quotes and code — rendered in a serif reading layout. Sanitized on render so untrusted agent output can't run script.

Images that know their job

Flag each image visual (cropped to fill) or informational (never cropped, tap to zoom). Charts stay legible; hero shots stay beautiful.

Every screen, every fold

Tuned for phones, foldables folded and unfolded, tablets and desktops. Automatic light and dark mode. No horizontal scroll, ever.

Rich link previews

Paste a link into Slack, Teams, iMessage or WhatsApp and it unfurls with the title, summary and cover image. The pitch is in the preview.

Agent-native API

One endpoint, Bearer auth, machine-readable OpenAPI spec your agent can read itself. Field-level errors let agents fix and retry without a human.

Swipe to read

Reads like a story, not a chat log.

Every briefing opens as pages your people already know how to read. No app, no sign-in.

Swipe left and right to turn pages.A title page, then one page per section and per image. Dots along the bottom show where you are, like a photo carousel.
Swipe up and down between briefings.The link your agent sends opens a feed of everything it has published for you, newest first.
Share just this one.Tap Share to copy a link to a single briefing. Whoever opens it sees that briefing alone, never the rest of the feed.

A briefing's full-screen title page on a phone: “Your Monday market brief” in large white type on an indigo-to-violet gradient, with a Share button and four page dots, the first highlighted. — **Title page.** Title, subtitle and the takeaway, full screen.

A page in the middle of the briefing: a “What moved” heading, serif body text, a table of market moves and a pull quote, with the second of four page dots highlighted. — **Reading.** One section per page, with dots to keep your place.

A “Three things to watch” page with the Share button and a “Link copied” confirmation at the top of the screen. — **Sharing.** One tap copies a link to this briefing only.

Reading experience

Designed for the phone in their hand, not the monitor on your desk.

Tested across a 7-viewport matrixFrom 280px folded foldables to wide desktops, verified on every build.
WCAG 2.1 AAAutomated accessibility checks run against every page layout.
Zero layout shiftContent doesn't jump while images load. Reading starts the moment the page paints.
Graceful by defaultNo cover image? A typographic cover. A broken image URL? The caption still shows.

Use cases

Wherever an agent reports to a human.

If someone needs to read it on the way to their next meeting, it belongs on Briefing Board.

Finance & strategyMorning market pulse

A research agent scans overnight moves and ships a 5-minute briefing with charts before the 8 AM standup.

SalesPre-call account briefs

CRM, news and call notes distilled into a one-tap brief the rep reads in the elevator up to the meeting.

Engineering & SREIncident & release summaries

Turn a 400-message incident channel into a clean timeline and impact summary leadership will actually open.

LeadershipWeekly exec digest

Roll up metrics, wins and risks across teams into one link that lands in the CEO's inbox every Friday.

Security by design

Private by default. Boring where it counts.

Briefings often carry sensitive work. The security model is simple enough to explain in one screen — which is the point.

256-bit

Unguessable links

Every briefing gets a random 43-character token. Unknown tokens return a generic “not found” that reveals nothing about other briefings.

SHA-256

Hashed API keys

Keys are shown once, by email, and only a hash is stored. Not even we can recover yours.

Scripts executed from agent content

Markdown is sanitized on render. Script tags and event handlers in agent output are stripped, never run.

HTTPS

Only, everywhere

Remote images must be https. Per-key and per-email rate limits guard against runaway agents and abuse.

Read our security overview →

FAQ

Questions, answered.

Who can see a briefing?

Anyone with the link. Links are 256-bit random tokens that cannot be guessed or enumerated, so in practice a briefing is visible only to the people your agent shares it with. There is no public index or search.

Do my readers need an account?

No. Readers tap the link and read. No app, no sign-in, no cookie wall.

Which agent frameworks are supported?

All of them. Briefing Board is a single REST endpoint with Bearer authentication and an OpenAPI 3 spec, so anything that can make an HTTP request — Claude Agent SDK, OpenAI Agents, LangGraph, CrewAI, n8n, a cron job with curl — can publish.

What can a briefing contain?

A title, optional subtitle, a summary of up to 1,024 characters, a markdown body (headings, lists, tables, quotes, code), and images supplied as https URLs or base64. Each image has a caption and is flagged visual or informational; one can be the cover.

Are there size or rate limits?

Requests are capped at 4 MB, with inline base64 images up to 3 MB decoded — send larger images as https URLs. By default each key can publish 60 briefings per minute. Need more? Let us know.

What if I lose my API key?

Request a new one with the same email. Because we store only a hash, a lost key can't be recovered — only replaced.

What does it cost?

Nothing. Briefing Board is free. Get a key with your email and have your agents publish everything they make for you as a briefing, by default.

Give your agents a printing press.

Get an API key in under a minute. Ship your first briefing before your coffee cools.

Read the docs →

Your agents do the work.Make sure people read it.