{"repo":"Corpus-OS/corpusos","free":true,"listed":false,"github":"https://github.com/Corpus-OS/corpusos","clone":"git clone https://github.com/Corpus-OS/corpusos.git","description":"Open-source protocol suite standardizing LLM, Vector, Graph, and Embedding infrastructure across LangChain, LlamaIndex, AutoGen, CrewAI, Semantic Kernel, and MCP. 3,330+ conformance tests. One protocol. Any framework. Any provider.","language":"Python","stars":213,"topics":["python","agents","ai-agents","anthropic","autogen","chatgpt","crewai","enterprise","gemini","langchain"],"license":"Apache-2.0","category":"ai-agents","readme_excerpt":"Corpus OS Reference implementation of the Corpus OS — a wire-first, vendor-neutral SDK for interoperable AI frameworks and data backends across four domains: LLM , Embedding , Vector , and Graph . --- Contact: team@corpusos.com Website: https://corpusos.com Docs: https://docs.corpusos.com --- Keep your frameworks. Standardize your infrastructure. Open-Core Model : The Corpus OS Protocol Suite and SDK are fully open source (Apache-2.0). Corpus Router and official production adapters are commercial , optional, and built on the same public protocols. Using this SDK does not lock you into CORPUS Router. --- Table of Contents 1. Why CORPUS 2. How CORPUS Compares 3. When Not to Use CORPUS 4. Install 5. Quick Start 6. Domain Examples 7. Core Concepts 8. Error Taxonomy & Observability 9. Performance & Configuration 10. Testing & Conformance 11. Documentation Layout 12. FAQ 13. Contributing 14. License & Commercial Options --- Why Corpus OS Modern AI platforms juggle multiple LLM, embedding, vector, and graph backends. Each vendor ships unique APIs, error schemes, rate limits, and capabilities — making cross-provider integration brittle and costly. The problem: - Provider proliferation — Dozens of incompatible APIs across AI infrastructure - Duplicate integration — Different error handling, observability, and resilience patterns rewritten per provider and framework - Vendor lock-in — Applications tightly coupled to specific backend choices - Operational complexity — Inconsistent monit","default_branch":null,"files":null,"tree":[],"storefront":"/r/Corpus-OS","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/Corpus-OS/corpusos/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}