Medialyst Agent pricing facts

Credits work with both the Medialyst API and MCP server. Top-up credits do not expire.

Pay as you go credit top-ups

Monthly plans

Annual plans

Everything your agent needs to do PR

the media intelligence layer for your agent

Give your agent live news, the journalists actually covering it, and a drafted angle for each — and keep every pitch behind human sign-off.

Get an API key (300 free credits)Read the docs

Free, no credit card required.

Install in 30 seconds
# add Medialyst as a remote MCP server
export MEDIALYST_API_KEY="<YOUR_API_KEY>"
AUTH_HEADER="Authorization: Bearer $MEDIALYST_API_KEY"

claude mcp add \
  -t http -s user \
  -H "$AUTH_HEADER" \
  medialyst https://medialyst.ai/api/mcp

claude mcp list
Connect Claude.ai and ChatGPT with the remote MCP server URL and authorize with OAuth — no API key to paste.
Supports any agent harness via MCP
The primitives

Two primitives. One rule: you stay in charge.

Agents do their best work grounded in current reporting — and their worst when they improvise who to contact. Every Medialyst primitive keeps human judgment in the loop.

01 · Real-time news search

Search the news in real time.

Generic web search was never built for news — the cycle moves too fast and stale results miss the window. Medialyst runs a dedicated real-time news search and attaches the publication's metadata to every result — including whether it's original editorial or a newswire, plus authority and reach. That's context a plain search API never gives you.

  • Built for the news cycle live coverage over keywords, URLs, or topics — not a stale web index.
  • Editorial vs. newswire, classified know whether a result is original reporting or a press-release wire — plus authority and reach.
  • 0.1 credits per search shared across UI, REST, and MCP.
mcpsearch_newslive · 0.1 cr
// tbs "qdr:h" → only the last HOUR of news
search_news({
  q: "AI safety regulation europe",
  tbs: "qdr:h"
})
response
{
  "status": "success",
  "data": { "articles": [
    {
      "title": "EU lawmakers press AI safety timeline",
      "source": "Reuters",
      "metadata": {
        "publication_type": "editorial",
        "domain_authority": 94,
        "estimated_monthly_organic_traffic": 41000000
      }
    },
    {
      "title": "Vendor launches AI compliance toolkit",
      "source": "PR Newswire",
      "metadata": {
        "publication_type": "newswire",
        "domain_authority": 76,
        "estimated_monthly_organic_traffic": 8200000
      }
    }
  ] }
}
02 · Enriched journalist profiles

Enrich journalists from their real, recent bylines.

Hand Medialyst an article or author and it resolves the journalist behind it — complete contact details with an email verified in real time, plus beat and pitch-fit scoring grounded in observed work, not model memory. Review, approval, and sending stay in the app, so the person whose reputation is on the line keeps final judgment.

  • Enrichment uses real bylines so fit scoring starts from observed work, not model memory.
  • Real-time verified email every contact validated at request time, not served from a stale snapshot.
  • No public send endpoint and no fake MCP send tool — outreach stays human-in-the-loop in the app.
mcpenrich_journalistsfit scored · no send
// enrich bylines, then score fit to the pitch
enrich_journalists({
  from: [{
    type: "article_url",
    url: "https://example.com/story"
  }],
  fit_context: {
    pitch: "AI agents changing enterprise support"
  },
  options: { wait: true }
})
response
{
  "object": "journalist_enrichment_batch",
  "status": "complete",
  "journalists": [{
    "name": "Maya Chen",
    "outlet": "The Information",
    "email_status": "deliverable"
  }],
  "research": [{
    "fit": { "score": 91,
      "personalized_angle": "..." }
  }]
}
Grounded, not guessed

Ground your agents in live, verified information — not pre-training data.

A vanilla agent answers from frozen training data and improvises the rest. The same agent working from a Medialyst media list reasons over live coverage and verified journalist records — every row backed by a real byline.

Without Medialyst
Vanilla agent
With Medialyst
Agents with Medialyst
News search
Falls back to web search, which returns stale data
Real-time news search — specify the window an article was published in
Finding journalists
Reads a stale byline from memory
Dedicated byline and author-retrieval flow with waterfall email lookup, cross-referenced against our media database
Email validation
Does not validate — sends to whatever it guessed
Every email validated and verified in real time
Journalist beat understanding
Guessed from memory, often out of date
Resolved from real, recent bylines
Publication context
Unknown or invented
Outlet type, authority, and reach attached
Email sending
No guardrails — can burn your reputation spamming journalists
Human-in-the-loop, built in by design
Same model, same prompt. The only difference is whether the agent is working from memory or from live, verified media data.
The surface

Same key. REST or MCP. Four tools through MCP.

Each MCP tool is a direct shim over a public REST endpoint. Agents get the same auth, scopes, errors, credits, and response shapes as any third-party API client. See the full OpenAPI spec.

MCP Server

Drop into Claude Cowork, Cursor, Codex, or any agent harness.

REMOTEhttps://medialyst.ai/api/mcp

Four REST-backed tools: search news, enrich journalists, poll the enrichment job, and check credits.

get_credit_balancesearch_newsenrich_journalistsget_journalist_enrichment_job
Streaming HTTP transport · public REST parity · org-scoped keys
REST API

The same surface, hand-callable.

BASEhttps://medialyst.ai

API-key authenticated and scoped per organization. The paths below are the public v1 routes that MCP mirrors, documented in the OpenAPI spec; outreach send and reply-fetch endpoints are intentionally absent from public v1.

GET/api/v1/credits/balance
POST/api/v1/news/search
POST/api/v1/journalists/enrich
GET/api/v1/journalist-enrichment-jobs/:jobId
Per-call credit cost · 402 on quota exhaustion · shared UI/API/MCP credits
Pricing

Pay as you go or subscriptions. Your choice.

Start with PAYG credit packs, then switch the slider for recurring monthly or annual views when usage is predictable.

Pay as you go

Start with credits. Scale when usage proves it.

Credits work across both API and MCP usage, and top-up credits do not expire. Add more when agents need them, then move to a monthly plan once volume is predictable.

Total$69
Selected top-up1,000 credits$0.069 / creditSave 31%
Get an API key (300 free credits)
How credits are used

Every action has a flat, predictable cost.

Credits are shared across UI, API, and MCP and draw from the same workspace pool — so agent usage and in-app work bill the same way.

1 credit ≈ $0.043 at Starter · less at Pro and Scale
News search
Per real-time news query — specify the window an article was published in.
0.1 credit
Enrich a journalist
Complete contact information, including an email verified in real time.
5 credits
Need bespoke volume, custom retention, or an MSA? Talk to us →
FAQ

Questions procurement asks. Answers agents can read.

Our search results mirror search-engine news search, so you get the same real-time coverage you would expect. When a source is in our publication index, the news item also gets Medialyst metadata such as publication type, domain authority, and estimated monthly organic traffic.

Journalist resolution and contact enrichment happen when you enrich from selected articles or author URLs. Search is retrieval plus source classification, not a fake byline-resolution endpoint.

Yes. Add it as a remote HTTP MCP server with your API key. The install snippet at the top of this page matches the documented claude mcp add --transport http command.

Journalist data is retrieved in real time, so everything stays fresh. Contacts and bylines are resolved against live sources at request time rather than served from a stale snapshot.

We log requests for billing, abuse prevention, and debugging. We do not train models on your media lists, queries, or outreach content.

The REST API returns 402 Payment Required. MCP returns the same condition as structured tool content so the agent can surface the quota issue instead of silently continuing.

Yes, inside the same organization and product workflow. Reselling raw journalist contact data is not permitted; building an agent or product experience on top of Medialyst data is what the API is for.

Muck Rack, Cision, and Prowly are built around human PR teams using a UI — they sell a static database with a per-seat license.

Medialyst is a callable surface. The journalist data is resolved in real time from articles, not pulled from a fixed database. The public primitives — real-time news search and journalist enrichment — are callable from REST or MCP. Pricing is per credit, not per seat, so agent usage draws from the same shared workspace pool as the app.

If you're a PR pro at a desk, those tools are mature and well-supported. If you're a marketer driving work through an agent, Medialyst is the layer underneath that work.