Invidious

Invidious is an open-source, privacy-focused front-end for YouTube that allows users to watch videos without a Google account, avoids tracking, and provides a fully documented REST API for developers. The project is licensed under AGPL-3.0, supports multiple languages, and offers features such as ad-free playback, SponsorBlock integration, and playlist management. It can be self-hosted or accessed via public instances listed on its site.

Invidious is listed with 2 APIs on the APIs.io network. Tagged areas include video, open-source, privacy, api, and frontend.

The Invidious catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Invidious’ developer surface includes authentication, documentation, API reference, getting-started guide, support, and 11 more developer resources.

27.0/100 thin Agent 18/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →
2 APIs
videoopen-sourceprivacyapifrontendyoutube

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Invidious It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/invidious/"><img src="https://apis.io/badge/invidious/card.svg" alt="Invidious on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
10 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/invidious/apis.yml: open an issue on github.com/api-evangelist/invidious to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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

Invidious API

Public REST API for Invidious, documented at https://docs.invidious.io/api/.

Invidious API

Invidious API as documented publicly: 55 operations. Contract generated from the documentation by API Evangelist (2026-10-28); not the provider's own document.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Invidious Context

38 classes · 119 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Invidious API Rules

10 rules · 7 errors 2 warnings 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetApiV1AuthPreferencesResponse

25 properties

JSON SCHEMA

GetApiV1ChannelsIdResponse

18 properties

JSON SCHEMA

GetApiV1PostIdCommentsResponse

14 properties

JSON SCHEMA

GetApiV1SearchResponse

26 properties

JSON SCHEMA

GetApiV1TrendingResponse

15 properties

JSON SCHEMA

GetApiV1VideosIdResponse

39 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Invidious Authentication

2 schemes

SECURITY

Invidious Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Invidious Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: invidious
name: Invidious
description: Invidious is an open-source, privacy-focused front-end for YouTube that allows users to watch videos without
  a Google account, avoids tracking, and provides a fully documented REST API for developers. The project is licensed under
  AGPL-3.0, supports multiple languages, and offers features such as ad-free playback, SponsorBlock integration, and playlist
  management. It can be self-hosted or accessed via public instances listed on its site.
url: https://artifacts.apis.io/invidious/apis.yml
image: https://invidious.io/invidious-colored-vector.svg
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- video
- open-source
- privacy
- api
- frontend
- youtube
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/invidious-rules.yml
- type: JSONLD
  url: json-ld/invidious-context.jsonld
- type: Vocabulary
  url: vocabulary/invidious-vocabulary.yml
- type: DataModel
  url: data-model/invidious-data-model.yml
- type: Authentication
  url: authentication/invidious-authentication.yml
- type: Conformance
  url: conformance/invidious-conformance.yml
- type: Hosts
  url: hosts/invidious-hosts.yml
- type: SDKs
  url: packages/invidious-packages.yml
- type: Packages
  url: packages/invidious-packages.yml
- type: DomainSecurity
  url: security/invidious-domain-security.yml
- type: Website
  url: https://invidious.io/
- type: Documentation
  url: https://docs.invidious.io/
- type: APIReference
  url: https://docs.invidious.io/api/
- type: GettingStarted
  url: https://docs.invidious.io/installation/
- type: Support
  url: https://invidious.io/contact/
- type: GitHubOrganization
  url: https://github.com/iv-org
apis:
- name: Invidious API
  description: Public REST API for Invidious, documented at https://docs.invidious.io/api/.
  humanURL: https://docs.invidious.io/api/
  baseURL: https://api.invidious.io
  aid: invidious:invidious-api-2
- aid: invidious:invidious-api
  name: Invidious API
  description: 'Invidious API as documented publicly: 55 operations. Contract generated from the documentation by API Evangelist
    (2026-10-28);

    not the provider''s own document.'
  humanURL: https://docs.invidious.io/api
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/invidious-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/invidious-get-api-v1-videos-id-response-schema.json
  - type: JSONSchema
    url: json-schema/invidious-get-api-v1-search-response-schema.json
  - type: JSONSchema
    url: json-schema/invidious-get-api-v1-auth-preferences-response-schema.json
  - type: JSONSchema
    url: json-schema/invidious-get-api-v1-channels-id-response-schema.json
  - type: JSONSchema
    url: json-schema/invidious-get-api-v1-trending-response-schema.json
  - type: JSONSchema
    url: json-schema/invidious-get-api-v1-post-id-comments-response-schema.json
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The Invidious documentation is publicly available HTML but provides no machine‑readable OpenAPI, GraphQL, AsyncAPI,
    or other contract.
  evidence:
  - url: https://docs.invidious.io/api/
    status: 200
  checked: '2026-10-28'
x-submission-probe: 200, 2026-10-26
x-enrichment:
  date: '2026-10-28'
  status: enriched
  artifacts_added: 23
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

Invidious API — frequently asked questions

Does Invidious have an API?

Yes. APIs.io lists 2 APIs from Invidious, including Invidious API and Invidious API.

Is there an OpenAPI specification for the Invidious API?

Yes. APIs.io indexes 2 OpenAPI specifications for Invidious, each linked for download from this page.

How do I authenticate with the Invidious API?

Invidious uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Invidious Authentication.

Is the Invidious API ready for AI agents?

Invidious has a Kin Score of 27.0 out of 100 (thin) and an Agent Readiness score of 18.3 (agent-aware), scored by API Evangelist on 2026-10-31.

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/invidious"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/invidious/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/invidious/evidence"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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