prapi.dev
Early access · v0.1

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.

fig.heroprapi.dev: brand voice file, morning digest, and inbox routing diagram, layered.
Sources at launch
HARO · Featured · B2B Writermore rolling in 30d
Brands per account
Up to 4separate voice, audience, GTM
Surface
Web app todayAPI + MCP in v0.2
Outbound access
Nonewe draft · you send
§ 01

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.

§ 02

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.

Step 01 · Brand context

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.

A brand.md file showing name, audience, voice rules, and a do_not_say list.
Step 02 · Connect

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.

A list of five press sources with three toggled active.
Step 03 · Send

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.

Morning digest showing a Forbes match with deadline 4h and audience, voice, and GTM score bars.
§ 03

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.

F-01

Filtered, not flooded.

Every query scored on three dimensions: does the audience match your ICP, can the response be written in your voice, does the GTM fit your motion. Below threshold, it never hits your inbox.
scoringaudience · voice · GTMthresholdtunable, per brand
F-02

On-brand drafts, not generic copy.

The brand context file is loaded into every draft. Your banned phrases stay banned. Your one-liner stays consistent. The response sounds like you wrote it because the model knows what you sound like.
voice_doc1 per brand · markdowndo_not_sayenforced at draft time
F-03

Multi-brand from day one.

One operator, four brands. Different voices, different audiences, different tolerances. Each brand gets its own digest. The HARO query about federal contracting routes to your govcon brand. The query about product management routes to your SaaS brand. No copy-paste between projects.
brands_per_accountup to 4 (Operator)routingper-brand · automatic
F-04

A digest you actually open.

Top of inbox at 8am. Five to ten opportunities, ranked. Each one with the deadline, the outlet, the scores, and the draft. No dashboards to log into.
cadencedaily · 8am localsurfaceemail + web · API in v0.2
§ 04

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.

The founder

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.

The contractor

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.

The agency

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.

§ 05

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.

Two columns. Left: v0.1 hosted web app digest. Right: v0.2 terminal showing curl POST to the prapi.dev API and an MCP handshake.

Early users get v0.2 access at v0.1 pricing.

§ 06

Pricing.

Two plans. One number per. The API tier lands with v0.2.

Solo
$39/ mo
  • One brand
  • Three connected inboxes
  • Daily digest
  • Unlimited drafts
Start 14-day trial
most operators
Operator
$79/ mo
  • Four brands
  • Unlimited inboxes
  • Daily digest per brand
  • Unlimited drafts
  • Voice validator on any text you paste in
Start 14-day trial
API access
TBDv0.2
  • 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
Join the API list
§ 07

Frequently asked.

The questions every prospect asks in the first email. Answered up front.

Is this PR as in pull request?

No. PR as in press relations. The .dev TLD is because the API ships in v0.2 and we built it for people who would rather hit an endpoint than log into a dashboard.

Where does the brand context live?

Your account. One file per brand. Markdown with structured frontmatter. Editable by you, anytime. Exportable. We will open-source the format when v0.2 lands so the file works outside our product too.

What inboxes are supported?

HARO at launch. Featured, Help a B2B Writer, and Connectively rolling out in the first 30 days. If you use one we have not added, tell us.

How is this different from just pasting my brand into ChatGPT?

You can do that. You will do it three hundred times this month. prapi.dev is the version where you do it once.

Are my drafts private?

Yes. We do not train on your content. Your brand context, your inbox, your drafts are yours.

What if I want to send the response from my own email?

That is the only way to send it. We draft. You send. We never email on your behalf.

Is there a free tier?

A 14-day trial on Solo. No card up front.
Early access · v0.1

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.

We draft · you send · we never email on your behalf/how-it-works