QVeris Open Ecosystem — Frequently Asked Questions
The QVeris ecosystem includes the CLI (v0.4.0, recommended for agents), MCP Server (v0.5.0), Python SDK, and community-contributed skills distributed through GitHub, npm, and ClawHub. All developer-facing tooling is published openly for inspection and reuse.
- What is the QVeris open ecosystem?
- The QVeris ecosystem is a collection of open-source clients, SDKs, an MCP Server, CLI tools, and community-contributed skills that connect to the QVeris capability routing network. Source code is published on GitHub (github.com/QVerisAI), packages on npm (@qverisai), and skills on ClawHub.
- What open-source tools does QVeris provide?
- QVeris publishes the CLI (@qverisai/cli v0.4.0) for low-token agent tool calling (80%+ fewer tokens vs MCP), an MCP Server (@qverisai/mcp v0.5.0) for Cursor and Claude Code integration, a Python SDK, a REST API, and the OpenClaw capability runtime. All packages are available on GitHub and npm under the QVerisAI organization.
- What is ClawHub and how does it relate to QVeris?
- ClawHub is a skill distribution platform for AI agent capabilities. QVeris publishes reusable skills to ClawHub, and agents can install them to extend their capability set. ClawHub works alongside GitHub and npm as part of the QVeris open ecosystem.
- How can I contribute to the QVeris ecosystem?
- Developers can contribute by publishing skills to ClawHub, submitting pull requests to QVeris GitHub repositories, creating npm packages that extend QVeris functionality, or building new capability providers that integrate with the routing network.
- What is OpenClaw and how does it relate to QVeris?
- OpenClaw is an open-source capability runtime that QVeris contributes to upstream. OpenClaw handles execution of individual capabilities, while QVeris provides the managed routing network layer — discovery, quality signals, provider selection, and billing — on top of it.