Press opportunities, filtered. On-brand drafts, written. One API away.
prapi.dev pulls every HARO, Featured, and B2B Writer query into one inbox, scores each one against your brand, and drafts the response in your voice. You read the digest. You hit send.
You signed up for HARO. Then Featured. Then B2B Writer. Now your inbox is a part-time job.
Three hundred queries a week. Maybe five are worth answering. The other two-ninety-five are the wrong audience, the wrong angle, or the wrong fit. By the time you find the five, the deadline is in two hours and your draft sounds like a B2B SaaS brochure.
That's the workflow prapi.dev replaces.
Not by writing more press releases. By making sure the only queries that hit your attention are the ones with a credible chance of landing. And the draft is already written when they do.
Three steps. Then a digest you actually open.
Drop in your brand context. Connect your inboxes. Read the digest. The same loop, every morning, until press is no longer a part-time job.
Drop in your brand context.
One file. Voice, audience, GTM tolerances, do-not-say list. Generate it from your homepage in 90 seconds or write it yourself. It is the source of truth for everything below.

Connect your PR inboxes.
Forwarding address for HARO, Featured, and Help a B2B Writer. Connectively and others rolling out next. We ingest, normalize, and route.
Read the digest. Send the draft.
Every morning, the queries that match your brand. Every match comes with a draft already written in your voice. Edit. Send. Move on.

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.
A digest you actually open.
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.
Doing this yourself, between everything else.
prapi.dev is the agent that makes it tolerable. The voice file is the same paste you already do. Automated. Applied to every press query that hits your inbox.
Running PR outreach, with an empty engagement log.
prapi.dev is the layer that gives you back the funnel data and the drafts. The brand voice doc is the artifact your client signs off on once, then you ship from.
Four brands across three time zones.
One account, four brands, one digest per brand. The federal-contracting query routes to govcon. The product-management query routes to SaaS. No tab-juggling.
v0.1 ships now. v0.2 ships the API.
Right now, prapi.dev is a hosted service. You sign up, you connect your inboxes, you read the digest in the web app. Next: full API and MCP access. Same brand context file. Same scoring. Same drafts. Different surface.

Early users get v0.2 access at v0.1 pricing.
Pricing.
Two plans. One number per. The API tier lands with v0.2.
- Four brands
- Unlimited inboxes
- Daily digest per brand
- Unlimited drafts
- Voice validator on any text you paste in
- Usage-based pricing
- Generous rate-limited tier for testing
- Production tier built around how you actually use it
- Same brand context file as v0.1
Frequently asked.
The questions every prospect asks in the first email. Answered up front.
Is this PR as in pull request?
Where does the brand context 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?
Is there a free tier?
Stop reading press queries that were never going to be a fit. Start with the five that matter.
Connect HARO, Featured, or B2B Writer. Drop in one brand context file. Read tomorrow morning's digest. No card up front for the 14-day trial.