omnibase_spi
ONEX Service Provider Interface - Protocol definitions
Decision gist · record as of 2026-08-14
Yes, if you are building a distributed service system or framework that needs stable, implementation-agnostic protocol definitions. The package is actively maintained, has no known vulnerabilities, and uses a permissive MIT license. It is still in Beta, so verify that the protocol surface is stable for your use case. Install it if you need to define service boundaries that multiple implementations can satisfy independently.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.12 or later.
- Low install friction with a pure-Python wheel.
- Active maintenance with a recent release 42 days ago.
License · maintenance · safety
MIT (permissive) — MIT license permits unrestricted use, modification, and distribution in both open-source and commercial projects with minimal obligations beyond attribution.
last release 2026-07-03 (42 days) · last repo commit 2026-08-12 · 1 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 137,737 downloads/mo, #11,360 on PyPI
Alternatives
Verify before relying
pip install omnibase_spi
from typing import Protocol, runtime_checkable
@runtime_checkable
class ProtocolExampleService(Protocol):
async def run(self, payload: bytes) -> bytes:
...- Whether the 231 protocol files across 39 domains are all exported or only a subset is public API
- Performance characteristics when runtime_checkable protocols are used at scale in high-throughput services
- Stability guarantees for the protocol contract surface given the Beta development status
What it is and what it does
omnibase_spi is a Service Provider Interface package that defines the protocol contracts for ONEX (OmniNode eXecution), a distributed service execution framework. It contains 231 runtime-checkable Python Protocol definitions across 39 protocol domains, plus frozen data-only contracts for wire formats. The package deliberately contains only interface definitions and shared data shapes imported from omnibase_core—no implementations, business logic, transport clients, or I/O behavior. This separation of concerns allows implementation packages to implement the protocols while keeping the SPI layer stable and reusable.
The package enforces strict dependency direction: it imports from omnibase_core but never from implementation packages, and implementation packages import from it. This design lets application and product repositories depend on the SPI for type boundaries without coupling to any concrete implementation. It requires Python 3.12 or later and uses pydantic and typing_extensions as runtime dependencies.
Use it for
- Define service boundaries in a microservices architecture where multiple teams implement the same protocol contracts independently.
- Establish type-safe interfaces for distributed services that need to be swapped or upgraded without breaking consumers.
- Create wire-format contracts for cross-service communication that remain stable even as underlying implementations evolve.
- Build plugin or adapter systems where third-party code must implement known protocol interfaces to integrate with a platform.
- Enforce architectural layering by making protocol definitions the only dependency between abstraction and implementation layers.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building a distributed service system or framework that needs stable, implementation-agnostic protocol definitions.
The package is actively maintained, has no known vulnerabilities, and uses a permissive MIT license. It is still in Beta, so verify that the protocol surface is stable for your use case. Install it if you need to define service boundaries that multiple implementations can satisfy independently.
Install
omnibase-spi on PyPI
Before you install
Low install friction with a pure-Python wheel. Active maintenance with a recent release 42 days ago. Requires Python 3.12 or later and depends on omnibase_core, pydantic, and typing_extensions—all standard, lightweight dependencies.
Requires Python 3.12 or later.
License in practice
MIT license permits unrestricted use, modification, and distribution in both open-source and commercial projects with minimal obligations beyond attribution.
Quickstart
pip install omnibase_spi
from typing import Protocol, runtime_checkable
@runtime_checkable
class ProtocolExampleService(Protocol):
async def run(self, payload: bytes) -> bytes:
...Verify before relying
- Whether the 231 protocol files across 39 domains are all exported or only a subset is public API
- Performance characteristics when runtime_checkable protocols are used at scale in high-throughput services
- Stability guarantees for the protocol contract surface given the Beta development status
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.12 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 3 packagesomnibase-corepydantictyping-extensions |
| Maintenance | Actively maintained 42 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 137,737 / month, #11,360 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaIntended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 3Programming Language :: Python :: 3.12Topic :: Software Development :: Libraries :: Python ModulesTyping :: Typed |
Evidence: omnibase_spi-0.23.1-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “protocol definitions service interface”
- omnibase_spiDefines runtime-checkable Protocol contracts and wire-format data…
- sentry-protosProvides protocol buffer and gRPC schema definitions for…
- isolate-protoProvides gRPC protocol buffer definitions for communicating with the…
Give your agent the search over MCP, or paste the wish link into any chat.
More Python Modules packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
PyYAML parses and emits YAML 1.1 data format, enabling serialization and deserialization of configuration files and Python objects to and from human-readable YAML text.
Pydantic validates Python data structures against type hints, coercing and checking input at runtime to ensure it matches a declared schema.
Provides reusable metadata objects for use with PEP-593 `typing.Annotated` to express common constraints like bounds, collection sizes, and predicates on types.
Install it if you use or build libraries that need to express type constraints in a standardized, inspectable way—or if you want to annotate your own types with…
Provides runtime tools to inspect and introspect Python type annotations, enabling programmatic examination of type hints at execution time.
See also omnibase-compat · omnibase_core · numerary · alibabacloud-gateway-spi · uipath-runtime · obspec · ciris-edge · langchain-protocol · uhi · pytest-archon