Questions, answered.

Three reasons: cost, completeness, and history. Cost: reading a finished Pulse is ~2k tokens; re-deriving five tickers of morning coverage from raw web search is 50k–100k tokens — every weekday, roughly $550–$750/month in tokens alone at typical API prices (≈$550 across the ~22 weekday delivery days; ≈$750 on a 30-day basis). Our measured generation cost is under a cent per Pulse, so a Pulse costs a small fraction of the tokens it replaces. Completeness: the pipeline handles feed monitoring, dedup against the last three days, and source attribution — the unglamorous parts you'd otherwise build and maintain yourself. History: the 90-day archive lets your agent backfill anything it missed — the finished Pulses, kept as written, not raw data to rebuild from.

The honest math. Generating one Pulse costs roughly half a cent in model tokens (measured, not estimated). An agent researching five tickers from raw search each weekday morning spends several times that in tokens alone — before counting engineering time for fetchers, clustering prompts, delivery, monitoring, and the inevitable feed breakage. At $5/month for the whole catalogue, the service pays for itself against a single hour of engineering time, and then it just runs.

Humans get email Pulses and the profile page. Everything else is agent-exclusive: the MCP server (15 tools), the REST API, signed push webhooks, the 90-day archive API, sentiment trends, price-move alerts, company profiles (SEC + Wikipedia), live market snapshots, and ticker comparison. The full list with what each replaces is in the agent quickstart.

It's a small program you run on your own machine that speaks the Model Context Protocol. It exposes Junctionary Pulse as 15 tools — get_briefing, get_briefing_history, get_sentiment_trends, get_alerts, list_my_tickers, add_ticker, remove_ticker, list_pulses, get_company_profile, get_market_snapshot, compare_tickers, get_company_people, get_earnings, get_sec_filings, get_insider_trades — so any MCP-compatible agent can pull Pulses, check trends, and manage tickers without you writing a single line of integration code.

Download junctionary_mcp.py from https://api.junctionarypulse.com/api/mcp/download using your API key as the X-API-Key header. It needs Python 3 and nothing else — standard library only, no dependencies to install. Add it to your MCP client config with your API key in the JUNCTIONARY_API_KEY environment variable. Full setup is on the agent quickstart.

Any client that supports MCP over stdio — Claude Desktop, Claude Code, and other MCP-compatible hosts. If your agent framework speaks MCP, it works.

Not yet — the server runs as a local process on your machine and forwards your API key to our API. That keeps your key under your control: it never passes through anyone else's infrastructure. A hosted option is on the roadmap.

Same data, less work. The MCP server wraps the REST API — every tool maps to an endpoint — so your agent gets structured tool calls instead of you hand-rolling HTTP requests, parsing JSON, and handling auth headers. If you prefer raw HTTP, the REST API and the quickstart docs are there for you.

Yes. Your API key is sent as X-API-Key on every upstream call, and entitlement and rate limits are all enforced server-side. A tool call for a Pulse outside your entitlement returns a clean 403-style error, not data.

Subscribe to the Agent plan and you get an API key. Your agent calls GET /api/pulse/<id>/latest each weekday morning — apple for Apple, tsla for Tesla, and so on — and receives the full Pulse as structured JSON: stories, summaries, source URLs, timestamps. Or skip polling entirely: register a webhook and we POST the Pulse to you at 6am CT, signed so you can verify it's really us. Trend, alert, and 90-day history endpoints are included. A subscription covers every Pulse in the catalogue; a free account may follow 2 Pulses, and anything outside your entitlement returns a 403. It's designed to be consumed without human involvement.

Yes. POST your https URL to /api/webhooks with your API key and we return a signing secret (shown once — save it). Every weekday morning around 6am CT we POST each of your entitled Pulses to your URL as {event: "briefing.daily", pulse, briefing} with X-Pulse-Signature and X-Pulse-Timestamp headers — HMAC-SHA256 of timestamp + "." + raw body, keyed with your secret. Verify the signature on receipt. One automatic retry on failure, then we log it. Up to 5 webhook URLs per account; we may disable endpoints that fail 7 days running.

Yes — a 90-day archive, exclusive to the API. GET /api/pulse/<id>/history?days=30 returns per-day rollups — headline, story count, aggregate sentiment, and a link to that day's full Pulse — newest last. For the scored sentiment time-series with volume trends, use /api/pulse/<id>/trends. Only your entitled tickers are accessible; every finished Pulse is kept for 90 days, so a missed morning is a lookup, not a rebuild.

Yes. The 90-day archive isn't limited to your subscription period — the day you subscribe, you can pull any Pulse from the last 90 days for your entitled tickers. New agent, mid-quarter onboarding, backtesting a strategy: GET /api/pulse/<id>/2026-08-14 returns that day's full Pulse as structured JSON. Raw news APIs can't do this — they give you today's feed, not finished Pulses from two months ago.

Recently shipped, free for subscribers: custom alert thresholds (your trigger per ticker, set on your profile), earnings dates + alerts, SEC filing and insider-trading tools via MCP, and Slack & Discord webhook delivery. On the roadmap: new pulse types — sports leagues, crypto, and more sectors — plus a hosted MCP server option.

One subscription covers every Pulse in the catalogue — tickers and sectors alike. Picking Pulses is a follow preference, never a purchase: follow the ones you want and get a morning Pulse for each — through the API, by email, or on the web. Anyone may follow 2 Pulses free, no card required, and Election Pulses are permanently free.

$5 a month for agents, $3 for humans — flat, for the whole catalogue. Annual billing is also available: $50/year for agents, $30/year for humans (2 months free). Monthly or annual billing, no contracts.

No. A subscription covers every Pulse in the catalogue, so there is no per-Pulse maximum to buy up to. Without a subscription, you may follow 2 Pulses free.

Five companies — Apple, Nvidia, ServiceNow, Microsoft, AWS — get curated coverage: deeper sourcing and practitioner-grade framing. Every other ticker gets standard coverage: the same five-minute Pulse format. Each Pulse is labeled with its coverage.

Everything lives on your profile page. Sign in with a magic link we email you — no password to remember — then add or drop tickers and set your notification preferences in one place.

Set your threshold on your profile page (default 3%). We check prices every 30 minutes during market hours and notify you the moment one of your pulses moves beyond it — by email, or through the API for agents. Earnings alerts are included too.

Every Sunday at 7am CT you get a week-in-review email: the top stories across your pulses, the week's biggest movers, and the trend lines — one email to catch up on the whole week.

Each story carries a sentiment tag — Positive, Negative, or Neutral — reflecting whether its coverage leans bullish or bearish for that ticker. It's a triage signal: scan your pulses and spot which names are having a good or rough day before you read a word.

News APIs sell data — headlines, sentiment scores, raw feeds. We sell the finished Pulse: LLM-written per-ticker narratives with sources, structured for your agent to read directly. No parsing, no summarization, no 50k-token research loops. Plus a 90-day archive of the finished Pulses themselves, kept as written.

Yes — native integrations for both. The LangChain toolkit (pip install junctionary-pulse-langchain) gives your agent 10 tools as standard BaseTools: get_briefing, get_briefing_for_date, get_briefing_history, get_sentiment_trends, get_alerts, get_watchlist_digest, compare_tickers, get_earnings_date, resolve_ticker, and list_pulses. The n8n community node (n8n-nodes-junctionary-pulse) includes an action node and a trigger node that fires your workflow when each morning’s briefing lands.

The news is free; your time isn't. Each Pulse replaces an hour of tab-hopping with a five-minute read — plus the practitioner's "why it matters" that raw news doesn't give you. If it doesn't save you time in the first month, cancel.

The pipelines are fully automated: they scan feeds nightly and cluster stories into Pulses. The editorial logic — what counts as signal, how stories are summarized and framed — was built by practitioners and is tuned per ecosystem.

Pulses publish every weekday morning around 6:00am Central Time — email, web archive, and API update together. When a subject's coverage is too thin that day, a short notice goes out instead of a Pulse for that subject. Price alerts go out intraday as they happen, and the digest lands Sundays at 7am CT.

Yes. Changing which Pulses you follow takes effect immediately and does not change your price, because a subscription covers the whole catalogue. Cancelling takes effect at the end of your current billing period: you keep what you paid for until then. No contracts, no cancellation hoops. New customers get a 7-day full refund on the first charge — see the refund policy.