What is AIOMetadata?

AIOMetadata is a next-generation metadata addon for Stremio that aggregates and enriches movie, series, and anime catalogs from multiple providers — TMDB, TVDB, MyAnimeList, AniList, IMDb, TVmaze, Fanart.tv, MDBList, and more. It gives you fine-grained control over which provider supplies metadata for each content type, lets you build custom catalogs, and integrates streaming-service catalogs with region and monetization filters.

Features

• 🎬 Multi-source metadata — choose your preferred provider per content type (TMDB, TVDB, MAL, AniList, IMDb, TVmaze)
• 🎨 Rich artwork — high-quality posters, backgrounds, and logos with language-aware selection and fallback
• 🎌 Deep anime support — MAL, AniList, Kitsu, AniDB, and TVDB/IMDb mapping; studio, genre, decade, and schedule catalogs
• 🗂️ Custom catalogs — drag-and-drop add, reorder, and delete catalogs (MDBList, custom lists, streaming services)
• 📺 Streaming-service integration — provider catalogs with region and monetization filters
• 🔍 Dynamic search: per-type search engines, plus AI-powered search included with your plan
• 🔐 Per-user config & passwords — secure addon password protection, trusted UUIDs for seamless re-login
• ⚡ Redis-backed caching — ETag-aware, self-healing cache for fast, reliable responses
• 🔥 Metadata pre-warming — ElfHosted private instances support customized pre-warming for non-default languages and providers, so your initial catalog loads are fast

AIOMetadata in Your Streaming Ecosystem

• 📡 AIOStreams — pair AIOMetadata's enriched catalogs with AIOStreams' aggregated stream sources
• 🎬 Comet / MediaFusion — better metadata equals better matching against debrid hashlists
• 🌍 Public instance — aiometadata.elfhosted.com is rate-limited and shared; private instances support custom pre-warming

Why ElfHosted?

AIOMetadata is genuinely complex to self-host. The Redis-backed caching layer means another service to deploy, network, and persist. Then you need API keys from TMDB, TVDB, Fanart.tv, MDBList, and (for AI search) Gemini — registering and managing each one manually. The Next.js frontend needs HTTPS for Stremio integration, which means yet another reverse proxy and SSL certificate. And the killer for international users: pre-warming non-English metadata caches takes hours of cold loading on first use unless you have someone already running it.

• 🚀 No Redis to deploy — managed cache included
• 🔑 Provider API keys handled — no separate registrations to manage
• 🔥 Pre-warmed metadata — language and provider caches warmed on demand for fast first-load
• 🔒 HTTPS by default — no reverse proxy or SSL setup
• 💝 Developer supported - ElfHosted maintain an ongoing monthly sponsorship of the upstream AIOMetadata developer

Technical Specs

• 🧩 Protocol: Stremio addon (HTTPS endpoint)
• 💾 Cache: Redis-backed, ETag-aware, self-healing
• 🧠 UI: React/Next.js with drag-and-drop config
• 🔗 Public instance: aiometadata.elfhosted.com (shared, rate-limited)

FAQ

How is this different from the public AIOMetadata instance?
The public instance is shared and rate-limited. Private ElfHosted instances support custom pre-warming for non-default languages and metadata providers, so your initial catalog loads are dramatically faster.

Do I need to bring my own TMDB / TVDB / API keys?
No — the hosted instance includes provider API access. You can optionally configure your own keys for higher rate limits if needed.

Does AIOMetadata work with anime catalogs?
Yes — it has deep anime support via MAL, AniList, Kitsu, and AniDB, with cross-mapping to TVDB and IMDb IDs.