Politics and policy monitoring
Use Vox endpoints to turn politics and policy monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Vox's public Atom home feed, section pages, and article pages into normalized JSON for explainer and policy news monitoring.
Get Vox's public section list, site-wide and per-section headlines, and full public article content as structured JSON.
Endpoint families
5
Documented params
8
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
8
Schema refs
5
{
"platform": "Vox",
"endpoint": "vox-article",
"method": "GET",
"path": "/vox/article",
"auth": "apiKey"
}Use cases
Get Vox's public section list, site-wide and per-section headlines, and full public article content as structured JSON.
Use Vox endpoints to turn politics and policy monitoring into repeatable API requests with documented inputs and JSON responses.
Use Vox endpoints to turn explainer content tracking into repeatable API requests with documented inputs and JSON responses.
Use Vox endpoints to turn content aggregation into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Vox endpoint catalog — 5 endpoints, 8 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Vox endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.
8 request parameters are documented across those Vox endpoints, 8 of them required — the full input contract is public before you write any integration code.
5 of the 5 Vox endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Vox endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the Vox endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/vox/article
/vox/author
/vox/headlines
/vox/news
/vox/sections
Endpoint catalog
/vox/articleReturns public Vox article metadata and body paragraphs from a canonical article URL.
MCP tool vox_article
/vox/authorReturns a Vox author's byline metadata, biography, and recent articles from a canonical author URL.
MCP tool vox_author
/vox/headlinesReturns fresh headlines from one public Vox section.
MCP tool vox_headlines
/vox/newsReturns fresh public Vox stories from its RSS feed.
MCP tool vox_news
/vox/sectionsReturns the public Vox editorial section inventory.
MCP tool vox_sections
Related APIs
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
Media & Streaming
Turn Apple Books ebook and audiobook pages into structured data — search, catalog detail, paginated customer reviews, similar titles, author bibliographies, series listings, and chart rankings as normalized JSON. Credential-free.
Media & Streaming
Search public Ticketmaster events and browse the full discovery hierarchy by category or city, with pagination plus event, attraction, and venue detail endpoints -- including fan reviews, related attractions, trending attractions, and enhanced venue branding -- for live-entertainment research.
How to scrape Vox
Vox's future-perfect section is bylined by a small rotating cast — its 9 most recent headlines on 2026-09-22 spanned 9–20 September and included guest columnist Shayla Love filling in on the "Your Mileage May Vary" advice column while regular writer Sigal Samuel is on parental leave. Crawlora's four endpoints return Vox's ten sections, its Atom feed, per-section headlines, and articles as normalized JSON.
/vox/sections returns the full 10-slug list /vox/headlines accepts — politics, culture, policy, world, money, technology, science-and-health, climate, future-perfect, and explainers.
/vox/news reads Vox's public home Atom feed. On 2026-09-22 its two most recent items were an ethics advice column and a long-form explainer on AI-assisted bioweapons risk, both bylined and dated.
Pass a slug from /vox/sections to /vox/headlines for that section's headlines, parsed from its public category page. future-perfect returned 9 headlines on 2026-09-22 dated 9–20 September, including a guest column from Shayla Love covering for Sigal Samuel during parental leave.
Pass a canonical vox.com URL to /vox/article for title, author, section, and body paragraphs. Eric Levitz's 35-paragraph explainer on AI-assisted bioweapons risk, tagged section: Technology, published 2026-09-19 with no separate revision timestamp.
FAQ
10 — politics, culture, policy, world, money, technology, science-and-health, climate, future-perfect, and explainers — call /vox/sections for the live list.
Atom, not RSS. Vox's home feed at vox.com/rss/index.xml is Atom-formatted, and /vox/news parses it directly.
A canonical vox.com URL, for example vox.com/technology/503361/ai-bioweapons-pandemics-extinction.
No. These endpoints read Vox's public Atom feed, category pages, and article pages — no login or subscription is bypassed. Crawlora API authentication still applies.
It leans that way lately but isn't only that: of the 9 headlines returned on 2026-09-22, several concerned AI safety and biosecurity, but the section also covered animal welfare ("4 charts" on factory farming), urban wildfire smoke risk, and wildlife highway crossings — Future Perfect's beat is effective-altruism-adjacent policy broadly, not one topic.