osyra_ome.adapters
Private pre-release / network boundary: The currently usable customer surface is offline verification of an existing signed artifact against an out-of-band trust anchor. Memory/network RPC APIs and host snippets on this page describe protocol and interface shape; the public Edge bridge, package publication, and release acceptance remain pending. Do not treat
api.osyra.ai:443examples as a released customer route.
Agent-framework adapters for the Osyra Memory Engine (OME) SDK.
Each sub-package wraps the public ``OmeClient`` / ``OmeAsyncClient`` surface to expose OME as the memory store, state store, vector index, or message-history backend for a popular agent framework. Adapters are optional features gated by per-framework ``pip install`` extras so the core SDK stays free of framework imports:
- ``pip install osyra-ome[langchain]`` → ``osyra_ome.adapters.langchain``
- ``pip install osyra-ome[langgraph]`` → ``osyra_ome.adapters.langgraph``
- ``pip install osyra-ome[llamaindex]`` → ``osyra_ome.adapters.llamaindex``
- ``pip install osyra-ome[autogen]`` → ``osyra_ome.adapters.autogen``
- ``pip install osyra-ome[all-frameworks]`` → all four
Importing this sub-package is intentionally lightweight: it does NOT import any framework. Each framework sub-package raises a guided ``ImportError`` at import time if the corresponding framework is not installed, pointing the caller at the right extras.
Public API surface stability: each adapter sub-package follows the same ADR-044 commitment as the rest of ``osyra_ome``. The framework versions accepted are declared in each sub-package's ``__compat__`` module for runtime introspection and cross-port differential warnings.
This module is registered as ENG-770 / story T4-5. See the design doc ``docs/architecture/AP00013-AP00014-OSYRA-OME-SDKS-DESIGN.md`` for the parent SDK architecture; this module is additive on top of the namespaced sub-clients (verify/memory/proof/witness).