The PR system for multi-brand operators.
Stop running each brand on a different tool and paying per profile. PRAPI is one workspace for the whole portfolio: PR, editorial, outbound, and assets, with one voice rule per brand.
fig.demo · see your pitch
Enter your site. PRAPI reads your public pages, drafts a pitch in your voice for a sample request, and visibly will not fabricate. No signup.
Prefer a tour first? See the modules
brief.md is an open spec, stewarded by The Integrity Framework. PRAPI is the canonical implementation, not the only one. Read the spec →
One system. Six modules. Every brand.
Most GTM tools were built for a single brand and priced per seat. PRAPI inverts both. One workspace for the whole portfolio, modules that share the same brief.md, the same voice rules, the same diligence layer. Four modules live today (PR-Pitch, Editorial Calendar, Outbound, Asset Management). Source Directory ships Q4 2026.
PR-Pitch
LIVEInbound source-request matching + drafting. HARO, B2B Writer, Substack, LinkedIn, X. Forwarded into one inbox, scored against your brand brief, drafted in your voice.
Editorial Calendar
LIVECross-brand content cadence. Plan slot drafts and topic fanouts from one grid. Recurring weekly slots, approval state machine, multi-channel publish (social, newsletter, blog) when the date arrives. Same brief.md drives the voice.
Outbound
LIVEMulti-brand cold email + LinkedIn paste-and-validate. Per-brand sequences, per-brand voice, unified inbox with reply classification + one-click resume / suppress / mark-engaged. Cap 50 sends/brand/day. Pause-forever-on-reply.
Asset Management
LIVEVersioned brand assets (logos, headshots, press kits). Non-destructive history per brand with restore. Bulk ZIP import. Public press-kit page + ZIP feed the Q4 source directory.
Source Directory
Q4 2026Consent-based brand-source directory. Brands publish their own brief.md and opt into discovery. Human UI at prapi.dev/sources, plus REST API + MCP for AI agents. JWS-signed from V1. We do not aggregate scraped journalist contacts.
Backlinks
ROLLINGBacklink targeting for brands running outbound. Reuses voice validator + outlet diligence + DataforSEO scorer to prioritize high-fit opportunities.
Same brief.md drives every module. Same voice rules. Same diligence. No copy-paste between modules. No per-module upcharge. Pricing scales with brand count, not module count.
Step 01. Tell us what your brand is about.
One short file per brand: your voice, your audience, the phrases you refuse to use. Generate it from your homepage URL in 90 seconds, or write it by hand. The file is yours; PRAPI just reads it. The same brief.md drives every PRAPI module (PR-Pitch, Editorial, Outbound, Assets) across your portfolio.

What goes in.
Your voice rules (short sentences, no corporate jargon, banned phrases). Your credentials. Your one-liner. Your headshot URL. Your bios. The outlets you respect, the outlets you decline. Most operators land on something around 60 to 100 lines per brand.
It is an open spec.
The format is called brief.md: plain markdown with structured frontmatter. Stewarded by The Integrity Framework, a separate organization that holds the trademark. PRAPI is the canonical implementation, not the only one. Other tools that implement the spec can read your file compatibly. Move tools, take your brand context with you.
Read the brief.md spec ↗Two ways to author.
- Generator: paste your homepage URL, get a starter brief in 90 seconds. Try it free →
- By hand: write the markdown directly. Commit it to your own Git repository if you like; PRAPI reads from there.
Step 02. Connect your PR inboxes.
One forwarding address per source. Set up takes a minute. We do not replace your inboxes; we sit downstream, ingest every query, normalize the schema, deduplicate, and route by brand.
Sources at launch.
- HAROjournalist queries, dailylive
- Help a B2B WriterB2B-focused querieslive
- Substackreporter newsletter poollive
- X (Twitter)#journorequest, 3×/daylive
- LinkedIn#journorequest signallive
How forwarding works.
You set the forwarding address once on each source. We ingest every query, normalize the schema across sources, deduplicate, and route to the matching brand. You don’t change your existing tools or accounts. If we miss a source you use, tell us.
Step 03. Read your inbox. Send the draft.
Every query that matches your brand lands in your inbox with a draft already written in your voice. The voice validator runs on every draft. Edit. Send. Move on.
Need a CFO source on retention pool measurement gaps in M&A.
Founders running 2 to 10 brands: how do you keep voice from collapsing?
Influencer marketing trends 2026. Generic, low audience match.
Email-first.
Your inbox is the surface. Each match carries the deadline, the outlet, the scores, and the draft. Below threshold, it never hits your inbox. No dashboards to log into.
We never send for you.
You review, you edit, you hit send from your own email. We do not have outbound access. The quality discipline is structural; automation without review produces the kind of spam that ruined HARO.
API. CLI. MCP. Every module. Every tier.
Every module ships with a REST API, a CLI, and an MCP server alongside the dashboard. Build pipelines, connect your editor, query from a shell. AI agents (yours or ours) can drive any module. No upcharge for the developer surface. Included at every tier.
A PR chief-of-staff that prepares, never sends.
Talk to it, or let it surface what needs you across every brand. It scores queries, drafts in each brand's voice, and docks the result for your review — it has no tool that can send. Prepare-and-surface is enforced in the code, not just the prompt. Live on web, REST, MCP, and CLI.
Meet the agent →Pull the digest, score a query, draft a pitch, mark a status.
Bearer-auth endpoints at app.prapi.dev/api/v1. Same scoring engine, same brief.md merge, same voice validator as the dashboard. Full MCP-tool parity. Build whatever pipeline fits your workflow.
prapi from your shell.
Single binary. Pipes to jq, integrates with your scripts, ships drafts straight to your editor. Works against the same API.
Drop into Claude Code, Cursor, ChatGPT.
220+ MCP tools surface every shipped module: PR-Pitch (list, draft, score, polish, status), Editorial Calendar (slots, drafts, strategy, engagement), Outbound (prospects, touches, inbox), Asset Management (versions, visibility), Portfolio signals, Newsletter subscribers, AIO citation tracking. Hand your AI assistant first-class access. Same auth as the API and CLI.
$ curl -H "Authorization: Bearer $PRAPI_KEY"
https://app.prapi.dev/api/v1/digest
→ 7 queries · 5 drafts ready · top: Forbes 0.92/0.81
$ prapi pitches list --brand prapi --since 24h
→ 3 drafts ready · 2 awaiting review · 0 sent
$ mcp handshake prapi.dev
→ tools/list (220+):
list_pitches · suggest_angles · polish_pitch
list_slots · publish_calendar_slot
list_prospects · inbox_unread · enroll_prospects
list_assets · restore_asset_version
aio_list_briefs · aio_publish_brief · aio_outcomes
list_open_signals · brief_suggestions ...Same brief.md. Same scoring. Same drafts. Different surface, and the same parity ships per-module as Editorial, Outbound, Assets, and Directory roll out. Included on Solo, Operator, and Intel.
What you get.
A digest, not a dashboard. Filtered by audience, voice, and GTM fit. Your banned phrases stay banned. Your one-liner stays consistent. Multi-brand from day one.
Filtered, not flooded.
On-brand drafts, not generic copy.
Multi-brand from day one.
Inbox-first delivery.
Auditable scoring
It learns on your corpus, and keeps the receipts.
The scoring improves from real outcomes, and every change is written to an audit log you can read: what changed, when, and why. Your data sharpens your scoring, not a shared black box. With your sign-off, never silently.
Built for operators who already do this work.
If you have ever pasted “here is my brand voice, here is my ICP, here is what I am working on” into a chat window, you are the buyer.
Two to five brands, one inbox.
One account, up to five brands, one digest per brand. The federal-contracting query routes to govcon. The product-management query routes to SaaS. No tab-juggling, no voice drift, no copy-paste.
Three to five clients, each a different voice.
One brief.md per client, signed off once. The funnel data and drafts come back to you. The voice each client expects gets enforced at the draft layer, not in your head.
One brand, but voice and credibility you refuse to outsource.
PRAPI is the agent that makes PR tolerable when you are also the product, the sales lead, and the support team. Your brief.md is the same paste you already do, automated.
Editorial.
Two credibility surfaces PRAPI publishes alongside the product. Original research on PR, AI in journalism, AEO citation patterns, and source-request economics. Plus the operator newsletter.
Named-citation reports on PR, AEO, and source-request economics.
Original research drawn from PRAPI’s corpus of journalist queries and named practitioner contributions. Contributors are cited in full with a link back to their work.
Read the research →Cited newsletterWhere operators get cited. AEO research and playbooks.
Operator-focused newsletter on AEO research, source-request economics, and the playbooks that actually move citations. Weekly. From Prapi.
Subscribe at cited.prapi.dev ↗Pricing.
Three plans. All modules at every tier. PR-Pitch, Editorial, Outbound, and Assets are live today; Source Directory ships Q4. The only thing that scales is brand count.
- 1 brand
- Unlimited inboxes · real-time delivery
- Unlimited drafts · voice validator on every draft
- Standalone voice validator
- Full outlet diligence
- API + CLI + MCP access
- 14-day trial · no card up front
- Up to 5 brands
- Everything in Solo
- Per-brand inbox · per-brand routing
- Real-time delivery across all sources
- 14-day trial · no card up front
- Up to 10 brands
- Everything in Operator
- Priority support
- Best fit for indie agencies and fractional CMOs
- 14-day trial · no card up front
Fair-use cap on every tier: 2,000 scored queries/mo and 200 drafts/mo per brand. Over-cap is a support conversation, not an auto-throttle.
Frequently asked.
The questions every prospect asks in the first email. Answered up front.
What is PRAPI?
Why a "system" not a tool?
Which modules are live today?
How many team members can I invite?
Is this PR as in pull request?
Where does my brief.md live?
What inboxes are supported?
How is this different from just pasting my brand into ChatGPT?
Are my drafts private?
What if I want to send the response from my own email?
How does the voice validator work?
What is the difference between Solo, Operator, and Intel?
What are the fair-use limits?
Is there a free tier?
Built by Tom Pinder.
PRAPI is the tool I built for myself. I run six brands. I use it every morning. The design decisions reflect what an operator who refuses to spam, refuses to outsource voice, and refuses to pay per-profile actually needs.

I’m a USMC veteran. Before that, four years at MillerKnoll doing systems work. Now I run StartVest LLC. PRAPI, FieldLedger, IdeaLift, HirePosture, ClarityLift, and a govcon advisory practice all sit under it.
Six brands. One operator. Every GTM tool I tried was priced like I was an agency and assumed I had one voice across all of them. PR, content, outbound, assets: each on a different SaaS, each in its own database, none talking to each other. I built PRAPI because I needed the opposite: one workspace, every brand, modules that share one brief.md.
You read the inbox. You hit send. I do the same. If something feels off, email me. The address is on my LinkedIn.
Stop running each brand on a different stack. Start running the portfolio from one workspace.
PR-Pitch, Editorial Calendar, Outbound, and Asset Management are all live today. Source Directory ships Q4 2026, included at every tier, no upgrade. 14-day trial, no card up front.
Brand context for AI assistants: prapi.dev/brief.md