Developers — API & MCP

Wire your systems directly into the Geminga Newswire launch sequence. A first-class REST API and a Model Context Protocol server let your code — and your AI agents — submit, track, and analyze press releases without a human at the console.

Geminga Newswire is built for automation from the ground up. Everything you can do in the dashboard — draft a release, submit it to editorial mission control, watch its status, and pull telemetry once it’s live — you can do programmatically over HTTPS.

Our developer surface has two orbits: a conventional REST API for backend integrations and workflows, and a Model Context Protocol (MCP) server that gives AI agents a native, tool-based interface to the same capabilities. Both are available on the Supernova and Singularity tiers.

REST + JSON Bearer token auth MCP server Supernova & Singularity

Get your API token

Tokens are organization-scoped and take about a minute to set up:

  1. Be on an eligible tier. API and MCP access ship with Supernova and Singularity. On any other plan the token panel shows an upgrade link instead. Compare tiers.
  2. Open Organization Settings. Sign in and go to Dashboard → Organization Settings → API Tokens. You’ll need the admin or owner role in your organization.
  3. Generate the token. Name it after what will use it (“CI pipeline”, “newsroom agent”) and click Generate Token. The full gk_live_… value is shown once — copy it into your secrets manager immediately. Afterwards only the prefix is visible.
  4. Send it as a bearer header. Authorization: Bearer gk_live_… on every request, to both the REST API and the MCP server. Revoke a token any time from the same panel; revocation is immediate.

Tokens inherit your organization’s permissions and keep working only while the org is on an eligible tier — a plan change locks them (403 plan_required) without deleting them. Tokens are automatically revoked when their creator leaves the organization or loses the admin role.

Rate limits

Each token may make 120 requests per minute (429 rate_limited beyond that, with a Retry-After header), and each organization may submit 30 releases per 24 hours through the API (429 daily_limit_reached). Reads — status polls, lists, analytics — only count toward the per-minute limit. Publishing always happens from the dashboard Launchpad, where credits are checked and spent.

REST API

The API is served from api.geminganewswire.com. Authenticate every request with a bearer token generated from your account settings. Tokens carry your organization’s permissions and credit balance, so a submission over the API travels the same editorial launchpad as one created in the dashboard.

Submit a press release

Send a POST to /v1/press-releases with the release fields as JSON. On success you receive a 201 with the new release’s id and a status of pending_review — it’s now queued for our editors.

Request
curl https://api.geminganewswire.com/v1/press-releases \
  -X POST \
  -H "Authorization: Bearer gk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "headline": "Acme Robotics Unveils Autonomous Warehouse Fleet for Mid-Size Distributors",
    "summary": "Acme Robotics today launched a fleet of autonomous warehouse robots...",
    "body": "<p>The fleet ... \"We built this for mid-size operators,\" said Dana Whitfield, CEO.</p>",
    "industry": "Technology",
    "dateline": "San Francisco, CA",
    "company_name": "Acme Robotics",
    "boilerplate": "Acme Robotics designs autonomous robots for warehouse logistics...",
    "contact_name": "Priya Shah",
    "contact_title": "Communications Director",
    "contact_email": "[email protected]",
    "contact_phone": "+1 555 010 2030"
  }'
Response · 201 Created
{
  "id": "142",
  "status": "pending_review",
  "headline": "Acme Robotics Unveils Autonomous Warehouse Fleet",
  "industry": "Technology",
  "dateline": "San Francisco, CA",
  "company_name": null,
  "publish_date": null,
  "public_url": null,
  "created_at": "2026-08-30T14:03:22.681Z",
  "self": "/v1/press-releases/142"
}

Distribution compliance check

Every release is checked against our distribution networks’ editorial standards before it is accepted: a factual headline (8–20 words), a dateline, a lead (summary), a 500–1,200-word body with at least one attributed quote, company boilerplate, a media contact (name plus email or phone), neutral non-promotional language, and no restricted content. A release that fails is not created — you receive a 422 listing what to fix. The check can take up to ~30 seconds for new content.

Response · 422 Unprocessable Entity
{
  "error": "compliance_failed",
  "message": "2 issues to fix before distribution",
  "blockers": [
    { "check": "quotes", "message": "Add at least one real quote attributed to a named person.", "field": "body" },
    { "check": "boilerplate", "message": "Add an \"About the company\" paragraph (100+ characters).", "field": "boilerplate" }
  ],
  "warnings": [
    { "check": "links", "message": "Add 1–3 links to the company or product page.", "field": "body" }
  ],
  "compliance_score": 61
}

Network topic warning

Some networks in Orbit and Supernova don’t accept certain topics: medical claims, dating, cannabis, gambling, politics, religion and digital currency. If a release covers one, it is not created and you get a 422 naming the topic and the networks affected. Resubmit with "accept_network_risk": true to submit anyway — the rest of your package still distributes it.

Response · 422 Unprocessable Entity
{
  "error": "network_topic_warning",
  "message": "This release covers Gambling / sportsbook, which some networks in your package don't accept. ...",
  "networks": ["USA TODAY Network – Local Newspaper 200+"],
  "topics": [{ "id": "gambling", "label": "Gambling / sportsbook", "match": "sportsbook" }]
}

Swap gk_live_xxx for your live API token from account settings. Never expose a live token in client-side code — keep it server-side or in a secrets manager.

Endpoints at a glance

A compact map of the core surface. Every endpoint is scoped to the token’s organization.

  • POST /v1/press-releases Create and submit a release for editorial review.
  • GET /v1/press-releases/:id Retrieve a release and its current status (pending_review, approved, published…).
  • GET /v1/press-releases List your organization’s releases, filterable by status and industry.
  • GET /v1/press-releases/:id/analytics Retrieve real-time telemetry — views, scroll depth, read-through rate, link clicks, daily trend, devices, referrals, wire-network syndication placements, earned pick-ups, and a platform scroll-depth benchmark. Everything needed to build a white-labeled distribution report.

MCP Server for AI agents

The press release is entering the AI era — and so is the newsroom. Geminga Newswire ships a Model Context Protocol server so autonomous agents can operate the wire directly, no glue code required.

MCP is an open standard for connecting AI assistants to tools and data. Point an MCP-capable agent — ChatGPT, Claude, or your own orchestration — at our server and it gains a set of typed tools mirroring the REST API: draft a release from a brief, submit it for review, poll its status, and pull analytics once it goes live. The agent reasons; the MCP server does the docking.

Native tool calls

Submitting and tracking releases become first-class tools an agent can invoke mid-conversation — no bespoke HTTP plumbing.

Works with the models you use

Any MCP-compatible client — including ChatGPT and Claude — can connect and start driving the wire.

Same launchpad, same guardrails

Agent-submitted releases pass through identical editorial review and org permissions — automation without loosening control.

Connect
Endpoint:  https://api.geminganewswire.com/mcp
Transport: Streamable HTTP (JSON-RPC 2.0 over POST)
Auth:      Authorization: Bearer gk_live_xxx
Server:    geminga-newswire v1.0.0

Protocol methods

Standard JSON-RPC 2.0 over a single POST to the endpoint. The server is stateless — each call carries the bearer token; there is no separate SSE stream (a GET returns 405).

  • initialize Handshake. Returns the protocol version, capabilities.tools, and serverInfo (geminga-newswire).
  • tools/list Enumerate the available tools and their input schemas.
  • tools/call Invoke a tool by name with an arguments object. The result is returned as JSON text content; tool-level failures come back with isError: true rather than a transport error.
  • ping Liveness check. Returns an empty result.

Tools

Four typed tools, each scoped to the token’s organization and mirroring the REST surface. Required arguments are marked.

  • create_press_release Create a release and submit it for editorial review; returns the id and a pending_review status, and fires the same lifecycle emails as a dashboard submission. Arguments: headline*, body* (HTML or plain text), summary, industry, dateline (e.g. “Phoenix, AZ”), company_name, contact_name, contact_email, boilerplate, accept_network_risk.
  • get_press_release Fetch one of your organization’s releases by id, including its current editorial status. Argument: id*.
  • list_press_releases List your organization’s releases. Arguments: status (draft, pending_review, approved, published, rejected, scheduled), industry, limit (default 50, max 200).
  • get_press_release_analytics Real-time telemetry for a release — views, unique visitors, scroll depth, referral sources, and external pick-ups. Argument: id*.
Example · tools/call
curl https://api.geminganewswire.com/mcp \
  -X POST \
  -H "Authorization: Bearer gk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "create_press_release",
      "arguments": {
        "headline": "Acme Robotics Unveils Autonomous Warehouse Fleet",
        "body": "SAN FRANCISCO - Acme Robotics today announced...",
        "industry": "Technology",
        "dateline": "San Francisco, CA"
      }
    }
  }'

The MCP server authenticates with the same bearer tokens as the REST API, so an agent inherits exactly the permissions and credit balance you grant it. The same limits apply: 120 requests/minute per token, and create_press_release is additionally capped at 30 submissions per organization per 24 hours. Read and create only — publishing, scheduling, and editing stay in the editorial launchpad.

Ready to automate your wire?

API and MCP access ship with the Supernova and Singularity tiers. Choose your mission profile and start distributing releases from your own systems and agents.

View pricing & get API access