What is live, what is rolling out, what is on the way.
Public roadmap. Module-by-module status at the top, then sources / surfaces / features / protocol. Updated as the launch sequence ships.
Platform modules
PRAPI is a PR system for multi-brand portfolios. Six modules. Same brief.md drives them all. Four GA today, Backlinks rolling, Source Directory ships Q4 2026.
- PR-Pitchinbound source-request matching + drafting: 5 sources live, voice-validated drafts, outlet diligencelive
- Editorial Calendarcross-brand content cadence + slot drafts + topic fanouts + recurring weekly slots + approval state machine + auto-publish to Buffer. Epic #429 V1 shipped (PR #517), Phase 1 complete (PR #764, 2026-05-07)live
- Outboundmulti-brand cold email + LinkedIn paste-validate + JIT generation + unified inbox with reply classification + REST/MCP/CLI. Epic #430 V1 shipped (PR #578), Phase 1 substantially complete 2026-05-07live
- Asset Managementversioned brand assets + per-asset scope + version-timeline UI + bulk ZIP import + soft-delete + public press-kit (HTML page + ZIP). Epic #431 V1 shipped (PR #564), Phase 1 complete 2026-05-07live
- Source Directoryconsent-based brand-source directory: brands publish their own JWS-signed brief.md, surfaced via human UI + REST API + MCP. We do not aggregate scraped journalist contacts.q4 2026
- Backlinksbacklink targeting reusing voice validator + outlet diligence + DataforSEO scorer. Epic #549, V2 shipped (PR #610)live
PR-Pitch · ingestion sources
Sources feeding the PR-Pitch module. Email-forwarded plus poll-driven. We do not replace your inboxes; we sit downstream and route by brand.
- HAROjournalist queries via helpareporter.com (email-forward); highest-volume feedlive
- Featuredwired, but negligible direct volume; Featured is folding into Connectively (revamp expected mid-2026) — its query stream reaches us via the HARO feedon roadmap
- Help a B2B WriterB2B-focused querieslive
- PressRangerwired email-forward; negligible inbound volume to dateon roadmap
- SourceBottlewired email-forward (free tier; Australia/SE Asia/global); no inbound volume yeton roadmap
- Reporter Substack poolcurated 15 journalist Substacks polled 3x weekday (8am, 12noon, 5pm ET) via RSS through a proxy, classified by Claude Haiku for source requests; ~300-500 extracted requests/weeklive
- Twitter (X)#journorequest + #prrequest + #bloggerrequest polled 3x weekday via Apify’s apidojo/tweet-scraper actor; classified by Claude Haiku for source requestslive
- Redditpaused: r/journorequest was banned, alternates (r/HelpAReporter, r/Qwoted) are all dead. Infrastructure ready if a viable sub emerges.on roadmap
- LinkedIn#journorequest hashtag polled 3x weekday via Apify’s harvestapi/linkedin-post-search actor (no-cookies path); classified by Claude Haiku with author bio context for outlet/beat inferencelive
- GitHub release feedshipping signals into LinkedIn-side outbound (separate from query inbox)rolling out
- PressPlugs (UK)low priority: UK demand unproven, plus GDPR exposure on per-user forwarded EU journalist querieson roadmap
Surfaces
How you read, score, draft, and ship. The email inbox is the default; the developer surfaces are included on every tier.
- Email inbox (real-time per match)each match lands the moment it scores past threshold, per brandlive
- Web app at app.prapi.devinbox + history viewlive
- MCP serverBeta: Claude Code, Cursor, ChatGPT connectorslive
- Public REST APIv1 live at app.prapi.dev/api/v1: bearer auth, full MCP-tool paritylive
- Single-binary CLIv0.10.0: `prapi {auth, brief, brands, pitches, submissions, assets, content, calendar, outbound, outlets, portfolio, aio}`. Install via prapi.dev/clilive
- Customer-facing team dashboardmulti-member workspaces beyond the operator accounton roadmap
Product features
The shared-engine behavior. What runs on every draft, every score, every submission package.
- Voice validator on every draftlive
- Standalone voice validator (paste any text)live
- Outlet diligence (DA + retraction history + audience overlap)live
- Multi-brand routing keyed on brief.mdlive
- Submission package composer (headshot, bio, assets)live
- BYOK Anthropic API key supportlive
- Per-tier fair-use cap (2k scored / 200 drafted per brand/mo)live
- brief.md generator from URLlead-magnet tool, also surfaces /brief-generatorlive
- Scheduled outbound (LinkedIn drafts queued from GitHub releases)rolling out
- Cross-brand analytics dashboardfunnel data per brandon roadmap
The protocol
brief.md is stewarded by The Integrity Framework. Other tools can implement the spec compatibly. The protocol surface is what makes brand context portable.
- brief.md spec v0.1published at theintegrityframework.org/specs/brief-mdlive
- Reference parser (open source)opens once the spec stabilizesrolling out
- journalist-brief.mdtwo-sided protocol: journalists publish their pitch preferenceson roadmap
- Structured pitch transactionsverified handoff between brand and journaliston roadmap
Editorial
PRAPI publishes original research and an operator newsletter. Editorial credibility is a separate surface from the product; the customer side runs PR-Pitch, Editorial Calendar, Outbound, and Asset Management.
- Research reports at /researchoriginal research on PR, AI in journalism, AEO citation patterns, and the economics of source requests. Named-citation reports with Schema.org Article markup.live
- Cited newsletter at cited.prapi.devoperator playbooks and AEO research, weekly cadence. Subscribe at cited.prapi.dev.live
- Methodology page at /methodologyhow reports are built, intake filtering, citation consent, exposure surfaceslive
- Plan-tier signup query handling/signup?plan=solo|operator|intel referenced in funnel doc; signup page does not yet honor the query string. Next.rolling out
Tell us what you need next.
Customer asks shape the order. If a source you use is not on the list, or a feature you need is not landing fast enough, say so. The roadmap moves to fit what operators actually need.
Frequently asked questions
Which PRAPI modules are live today?
Four of five GTM modules are live: PR-Pitch (5 inbound source-request feeds + voice-validated drafts + outlet diligence), Editorial Calendar (cross-brand grid + recurring slots + auto-publish to Buffer), Outbound (multi-brand cold email + LinkedIn paste-validate + unified reply inbox), and Asset Management (versioned assets + bulk import + public press-kit ZIP).
When does Source Directory ship?
Q4 2026. Brand-side directory only, no centralized journalist database (deprioritized 2026-05-07 for legal + ToS reasons). Brands publish their own consent-based brief.md and opt in to a JWS-signed directory entry. Dual-surface: human-facing UI + REST API + MCP for AI agents.
Does PRAPI support API + CLI + MCP today?
Yes. Every shipped module ships its REST surface in the same scope as the web app, not "API parity later". /api/v1/* endpoints are bearer-authed; the MCP server lives at /api/pr-pitch/mcp; the single-binary CLI ships at prapi.dev/cli. Source Directory will follow the same pattern at launch.
How fast does PRAPI ship?
Q3 2026 was the compressed roadmap quarter: Editorial Calendar V1, Outbound V1, Asset Management V1 all shipped within Q3. The original 3-quarter stagger was compressed because brief.md plus existing PR-Pitch infrastructure cut new code per module to ~30–40%. Expect monthly module-level releases through 2026.
Is brief.md going to be open-sourced?
Yes. The spec is already public at theintegrityframework.org/specs/brief-md. The reference parser (brief-core) and CLI (prapi-cli) become open-source once the spec stabilizes at v1.0. brief.md works outside PRAPI today; PRAPI is just the canonical implementation.
Brand context for AI assistants: prapi.dev/brief.md