# Put your press release on the newswire, not a PR retainer

Source: https://opvs.ai/blog/shipping-spideriq-spiderpr-skills

---

> Your newsroom post and outreach are ready, yet external press feeds miss your news. @spideriq/spiderpr-skills lets your agent wire approved announcements in minutes without a PR retainer.

Most company announcements die in a Google Doc or sit quietly on a blog page nobody outside your list sees. You hit real milestones all year. Maybe you launched a new product line, entered a new market, or signed a flagship partner. You want press feeds, search engines, and buyers to see that proof on the public newswire. Instead, you get stuck between two bad choices. Either you pay a monthly PR retainer for four releases a year, or you lose half an afternoon inside a wire portal.

In this post I will show you how your agent runs external newswire distribution from your desk in minutes. You will see how @spideriq/spiderpr-skills completes the SpiderIQ press desk alongside your own newsroom and outreach. I will also walk through the exact async payload it sends and the guardrails that stop duplicate billing.

## The false choice that keeps company news off the wire

I kept watching founders hit the same wall every quarter. Their product shipped on time. Their customer numbers were real. Their announcement copy was already written and approved. Yet external press pickup never happened.

Here is the false belief behind it:

You think getting onto the newswire requires either a PR agency on retainer or hours of manual portal work.

Neither option makes sense for a lean team. Hiring an outside agency or publicist just to upload finished copy costs thousands a month. Worse, it adds days of email threads before anything goes live.

Doing it yourself is no better. You log into an unfamiliar wire portal once a quarter. You format wire-ready HTML by hand and paste up to 25 tags and contact fields into tiny form boxes. Then you sit there refreshing a status page, hoping for a live link before launch hour.

## Completing the three-lane press desk on OPVS

When I built the press stack on SpiderIQ and packaged the skills on OPVS, I wanted your agent to run every channel from one approved draft.

A real press desk does three distinct jobs:

- Host the permanent newsroom archive on your own domain with @spideriq/publish-skills.

- Pitch journalists or notify your list one-to-one with @spideriq/mail-skills.

- Distribute the official release over the external newswire with @spideriq/spiderpr-skills.

Before @spideriq/spiderpr-skills, your agent could publish your newsroom page and draft your outreach. Then it handed you a manual chore at the last mile.

Now the submit-press-release skill closes that gap. You hand your agent the approved headline and body once. It dispatches the release through SpiderIQ&#x27;s SpiderPR pipeline, tracks the job until the wire clears, and returns your live public link and distribution report.

## Worked example: from approved copy to a live wire URL

The skill wraps three methods on https://spideriq.ai/api/v1 under your workspace token: submitPressRelease, getJobStatus, and getJobResults.

Suppose you have a Tuesday 09:00 UTC partnership announcement ready to ship. You ask your agent to rehearse on the test queue first, or schedule the live embargo window directly:

{
  "priority": 5,
  "payload": {
    "title": "Acme Robotics Expands Warehouse Fleet Across DACH",
    "body": "<p>ZURICH - Acme Robotics today announced...</p>",
    "summary": "Acme Robotics opens regional fulfillment deployment across Germany, Austria, and Switzerland.",
    "category": "technology",
    "tags": ["robotics", "logistics", "dach", "supply-chain"],
    "contact": {
      "name": "Media Relations",
      "email": "press@example.com",
      "phone": "+41-44-555-0100"
    },
    "scheduled_release_at": "2026-11-24T09:00:00Z",
    "test": false
  }
}Behind that single POST /jobs/spiderPR/submit call, SpiderIQ checks every field. Your title supports up to 300 characters, your body supports up to 50,000 characters in plain text or HTML, and tags accepts up to 25 keywords. SpiderIQ renders wire-ready HTML, queues the job with the wire provider (prnow), and returns a job_id with status queued.

Your agent polls GET /jobs/{job_id}/status every 3 to 5 seconds. Once the job reaches completed, it calls GET /jobs/{job_id}/results to read your verified outputs:

{
  "status": "completed",
  "published_url": "https://prnow.io/releases/acme-robotics-expands-warehouse-fleet",
  "wire_report_url": "https://prnow.io/reports/ord_9f82c1a4",
  "provider_order_id": "ord_9f82c1a4",
  "published_at": "2026-11-24T09:04:12Z"
}You get the exact public newswire URL for your social posts and investor update. You also get the full syndication report for your records.

## Built-in guardrails for paid, irreversible sends

A newswire release is not a draft blog post you can unpublish five minutes later. Every live submitPressRelease call spends credits and puts permanent copy on public press feeds. There is no recall button and no idempotency key.

While testing early agent runs, I saw two failure modes that needed hard guardrails inside the skill.

First, an impatient agent treated the initial 201 submit response as "published" and reported a link that did not exist yet. Second, when a wire job took four minutes to clear, a naive retry loop called submitPressRelease again. That billed twice and sent duplicate releases.

So submit-press-release enforces a strict confirm-before-you-wire gate:

- Your agent confirms the exact approved title and body with you before calling submitPressRelease.

- It wraps every field inside payload so flat JSON never hits a 422 validation error.

- It treats submitPressRelease strictly as an async job_id handoff, never a URL, and polls that job_id instead of resubmitting.

- Before launch morning, payload.test: true runs the submission path on the test queue without spending on a live release.

## Watch the 53-second film and put your news on the wire

You can always optimize your market presence once your milestones ship. You cannot optimize zero announcements. When wire distribution takes minutes instead of an agency retainer, every product launch, regional move, and partnership earns public proof.

I recorded a 53-second chalkboard explainer film for v0.1.2 and added the visual workflow kit to the marketplace card so you can inspect the full loop first.

Install @spideriq/spiderpr-skills on OPVS and trigger it with "send this press release". Live on the marketplace as @spideriq/spiderpr-skills.