APITube

APITube is a news data API providing search and retrieval across news articles, top headlines, trends, companies, journalists, and fact-checks, with taxonomy resolution for entities, topics and locations. The public contract is an OpenAPI 3.1 document of 26 operations served from api.apitube.io, authenticated with an API key by header or query parameter. APITube also operates a first-party MCP server at mcp.apitube.io over streamable HTTP, whose tool list is readable anonymously, and publishes an RFC 9727 api-catalog linkset at the apex that names the specification, the documentation, the llms.txt and the MCP server card.

APITube publishes 1 API on the APIs.io network: News API. Tagged areas include News, Media, Data, Search, and Fact Checking.

🌐 Visit website 📡 Source on GitHub
22.8/100 emerging ▬ flat Agent 24/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs 1 MCP Servers
NewsMediaDataSearchFact CheckingEntitiesMCPAgents

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 22.8/100 · emerging
Contract Quality 14.3 / 25
Developer Ergonomics 1.9 / 20
Access Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Contract Governance 0.0 / 12
Discoverability 6.7 / 10
Agent readiness — 24/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/apitube: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

APITube News API

News search and retrieval — everything, top headlines, trends, companies, journalists, fact-checks and taxonomy suggestion. 26 operations, API key by header or query.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

APITube MCP Server

Search and filter global news articles by language, category, sentiment, entities, media and more.

MCP SERVER

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 MCPServer
MCPServer

Company 1

The organization behind the API

Website
Website

Other 1

Properties that don't map to a standard resource type

APICatalog
APICatalog

Source (apis.yml)

apis.yml Raw ↑ 
aid: apitube
name: APITube
description: APITube is a news data API providing search and retrieval across news articles, top headlines, trends, companies,
  journalists, and fact-checks, with taxonomy resolution for entities, topics and locations. The public contract is an OpenAPI
  3.1 document of 26 operations served from api.apitube.io, authenticated with an API key by header or query parameter. APITube
  also operates a first-party MCP server at mcp.apitube.io over streamable HTTP, whose tool list is readable anonymously,
  and publishes an RFC 9727 api-catalog linkset at the apex that names the specification, the documentation, the llms.txt
  and the MCP server card.
type: Index
url: https://raw.githubusercontent.com/api-evangelist/apitube/refs/heads/main/apis.yml
created: '2026-08-21'
modified: '2026-08-21'
specificationVersion: '0.23'
tags:
- News
- Media
- Data
- Search
- Fact Checking
- Entities
- MCP
- Agents
tags_raw:
- news
- media monitoring
- news api
- fact check
- journalists
apis:
- aid: apitube:apitube-news-api
  name: APITube News API
  description: News search and retrieval — everything, top headlines, trends, companies, journalists, fact-checks and taxonomy
    suggestion. 26 operations, API key by header or query.
  humanURL: https://docs.apitube.io
  baseURL: https://api.apitube.io
  tags:
  - News
  - Search
  - Data
  properties:
  - type: OpenAPI
    url: openapi/apitube-news-api-openapi.yml
  - type: Documentation
    url: https://docs.apitube.io
  - type: APIReference
    url: https://api.apitube.io/openapi.json
  - type: MCPServer
    url: mcp/apitube-mcp-server-card.json
  - type: Authentication
    url: https://docs.apitube.io
common:
- type: APICatalog
  url: well-known/apitube-api-catalog.json
- type: LLMsTxt
  url: llms/apitube-llms.txt
- type: MCPServer
  url: mcp/apitube-mcp-server-card.json
- type: Website
  url: https://apitube.io
- type: DeveloperPortal
  url: https://docs.apitube.io
maintainers:
- FN: APITube
  url: https://apitube.io
x-provenance:
  added: '2026-08-21'
  method: searched
  source: https://apitube.io/.well-known/api-catalog
  note: 'Submitted via apis.io/add on 2026-08-20 from apitubehq@gmail.com. THE SUBMITTED APIs.json URL IS WRONG: https://apitube.io/apis.json
    returns 404, and so does a control path, so the 404 is real rather than a catch-all. That is a bad pointer in the submission,
    NOT an absent surface — APITube publishes plenty. Everything here was discovered from the RFC 9727 api-catalog at the
    apex instead, which is the authoritative discovery document. TWO OPENAPI DOCUMENTS EXIST AND THEY DISAGREE. https://api.apitube.io/openapi.json
    is OpenAPI 3.1.0 with 26 paths and no component schemas; https://apitube.io/openapi.json is OpenAPI 3.0.3 with 5 paths
    and 13 schemas. Both were fetched and both are kept under openapi/_original/. The api-catalog names the api.apitube.io
    copy as `service-desc`, so that one is treated as canonical and is the working document. The apex copy is retained as
    evidence of the discrepancy; it is the provider''s to reconcile. The MCP server at https://mcp.apitube.io/ was probed
    live and answered tools/list anonymously with two tools, search_news and suggest. The REST API was probed at api.apitube.io/v1/news/everything
    and returned 401 JSON, which is correct gating.'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/apitube"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/apitube/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/apitube/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.