Add APITube to Commercial & Proprietary Services

[liamka]

Adds APITube to Commercial & Proprietary Services.

APITube is a hosted news API. Every indexed article is returned as JSON already enriched: sentiment
scores at article level (sentiment.title, sentiment.body, sentiment.overall, each with a score
and a polarity) and at entity level (entities[].sentiment), resolved named entities with numeric
IDs and Wikidata links, IPTC media-topic categories and industry tags. Filters combine in one
GET /v1/news/everything call: entity.id, language.code, source.country.code,
source.domain, category.id, industry.id, sentiment.*.polarity and
published_at.start / published_at.end.

Relevance to this list: it is a general-purpose news source, not a market-data vendor, but the
enrichment and the date-range filter are what quant workflows need from news — per-entity sentiment
time series, event windows around a company or industry, and news counts joined to a price series.
/v1/news/trends returns trending values for a field over time buckets, /v1/news/stream is a
Server-Sent Events feed for live use, and CSV/TSV/XLSX/Parquet exports come out of the same query.

Verified against the live API today (2026-08-21):

# entity-level sentiment on business news
curl -s -G "https://api.apitube.io/v1/news/everything" \
  --data-urlencode "category.id=medtop:04000000" \
  --data-urlencode "sentiment.overall.polarity=negative" \
  --data-urlencode "per_page=2" --data-urlencode "api_key=$APITUBE_KEY"

# historical window, entity filter (Tesla, Inc. = 1580517 via /v1/suggest/entities?prefix=tesla)
curl -s -G "https://api.apitube.io/v1/news/everything" \
  --data-urlencode "entity.id=1580517" \
  --data-urlencode "published_at.start=2024-03-01" \
  --data-urlencode "published_at.end=2024-03-31" --data-urlencode "api_key=$APITUBE_KEY"

Both return 200. Date-range queries reach back to at least January 2020.

Placement. APITube is a hosted commercial service. The public repositories under
https://github.com/apitube are client SDKs, integration examples and migration kits — thin by the
definition in CONTRIBUTING.md — so the entry goes in Commercial & Proprietary Services rather
than Market Data & Data Sources, and the [GitHub] suffix points at the Node/TypeScript SDK
(https://github.com/apitube/news-api-node, published as @apitube/news-api, last pushed
2026-08-16) only as a usage reference.

Free tier and pricing (https://apitube.io/pricing, checked 2026-08-21):

	Free	Starter	Basic	Professional
Price	$0	$29/mo	$99/mo	$199/mo
Requests	100/day	10,000/mo	50,000/mo	150,000/mo
Articles per request	10	50	200	250

The free tier is permanent, resets daily and needs no card ("No credit card required" on the pricing
page). It is not a trial: all enrichment — sentiment, entities, categories, industries, topics,
source metadata — is returned in full, along with article URL, title, description and images. What
free does not include is the full article body (truncated to 200 characters) and the hosted MCP
server, which starts at Starter. Both limits are stated in the entry.

Public documentation: https://docs.apitube.io (parameter reference, response schema, error codes).

• No duplicate: apitube does not appear in README.md or in any open or closed PR.
• scripts/validate_readme.py --diff-from origin/main passes on the added line.
• One entry, one file, README.md only.

Disclosure: I work on APITube, so this is a self-promotional submission.

[wilsonfreitas]

Thanks for the detailed submission and disclosure. The entry is correctly placed under Commercial & Proprietary Services, the linked GitHub repository is appropriately treated as a client SDK rather than substantive service implementation, and I found no duplicate APITube submission. The current-head validation and site-generation checks also pass.

This needs a few changes before acceptance:

1. Please reconcile the published free-plan limits. The pricing page says the free plan has a 12-hour delay and one month of history, while the free-plan support article describes access to the live index. Those pages also disagree about image availability, Trends API access, and requests versus credits:
   • https://apitube.io/pricing
   • https://support.apitube.io/en/articles/billing/plans/free-plan-limits
2. Once the authoritative limits are clear, update the entry to disclose the free tier's delay and history limit. The current wording says the archive reaches back to 2020 without clarifying that the pricing page limits free accounts to one month.
3. Please condense the entry to one concise factual sentence.
4. The branch currently conflicts with main; update it and rerun CI after resolving the conflict.

If the pricing page reflects the intended free limits, one possible entry is:

- [APITube](https://apitube.io) - `REST` `MCP` - News API with entity sentiment and structured metadata; the permanent no-card free tier includes 100 requests a day, 10 articles per request, a 12-hour delay, one month of history, truncated text, JSON-only output and no MCP, with paid plans from $29 a month. [GitHub](https://github.com/apitube/news-api-node)

The permanent no-card free tier otherwise appears useful enough to qualify.