Tools for addon authors: manifest validator, typed helpers, example addons.
Deliberate. An addon author should never hit a licensing question while writing an addon (madde 33). The client's copyleft protects the core from being taken closed; applying it to the developer SDK would only tax the ecosystem it is meant to grow.
For the same reason eon-stream-spec is Apache-2.0: a
specification nobody else may implement is not a specification.
Scaffold — Faz 2. The contracts exist (eon-stream-spec) and are at v0, unstable; the SDK
follows once they settle enough to wrap without immediately rewriting.
Planned:
eon validate <manifest>— validate an addon, module or package descriptor against the published schemas, with errors a human can act on.eon serve— run an addon locally with request logging and the compatibility checks the client applies.eon package— build and sign a material package.- Typed helpers for JavaScript/TypeScript first, Rust second.
- Example addons: a minimal catalogue, a stream resolver, a material package producer.
You do not need this SDK. A remote addon is an independent HTTP service returning JSON —
any language, any framework. Read
docs/addon-protocol.md
and validate against the schemas directly.
EON Stream tracks the Stremio addon protocol, so an existing Stremio addon generally works
unchanged. The exceptions are documented, and they are exceptions by design rather than bugs:
docs/compatibility.md.
eon-stream-spec — the contracts · eon-stream-marketplace — publishing · eon-docs — the plan
MIT.