← Back to search
65
Partial
Agentic Readiness Score
+25 llms.txt +20 OpenAPI missing +20 ai-plugin
Raise this score to 95+
We ship the 6-file GEO uplift as a pull request against your repo. Flat fee, turnaround under 72 hours.
Fix this for $199 →
ai-tools openapiapiaillms-txt

Agentic Signals

📄
Found
🤖
ai-plugin.json
Not found
📖
OpenAPI Spec
Found
🔗
Structured API
Found
🛡
Not specified
🏷
Schema.org Markup
Found
MCP Server
Not found

Embed this badge

Show off your agentic readiness — the badge auto-updates when your score changes.

Agentic Ready 65/100

            

llms.txt Content

# QVeris > Every capability. One call away. QVeris is the capability routing network for agents — discover, compare, call, and settle real-world, verified capabilities through one protocol. ## What QVeris does - Lets Agents discover the right capability with natural language instead of blindly picking APIs - Provides quality signals (success rate, latency, price) so Agents can make informed choices - Handles permissions, sandbox execution, billing, audit, and supply-side distribution - Allows Agents to both consume and (in the future) provide capabilities ## Core protocol - Discover: find capabilities with natural language (free) - Inspect: view capability details, parameters, success rate, latency - Probe: validate candidate parameters and obtain a quote without executing or consuming credits - Call: invoke any capability, get structured results and compact pre-settlement billing when available - Audit: query usage history and credits ledger with summaries or precise filters - Covers finance, search, weather, maps, docs, social, blockchain, healthcare, and 15+ categories - 99.99% call availability, <500ms average latency ## Use cases - Agent needs to call third-party APIs or data sources - Agent needs to dynamically discover and select capabilities - Need a unified calling protocol with structured returns ## How QVeris relates to OpenClaw - OpenClaw lets Agents use tools (runtime) - QVeris lets Agents know which to call, why to trust it, and how to pay (capability routing) - They are runtime + capability routing network, complementary not competing ## Access methods (recommended order) - CLI v0.10.0 (recommended for agents): npm install -g @qverisai/cli — zero prompt tokens, deterministic output, 10,000+ tools without prompt bloat - MCP Server v0.13.0: npx @qverisai/mcp — for IDE integrations (Cursor, Claude Desktop, OpenCode) - Hosted MCP: open /hosted-mcp on this site for the correct remote endpoint and Bearer authentication setup - TypeScript SDK v0.

OpenAPI Spec (preview)

openapi: 3.1.0 info: title: QVeris Public REST API version: 2026-07-30.1 summary: External REST API for enterprise integration. description: OpenAPI 3.1 schema for the formally released public `/api/v1` REST API surface. It covers search, provider discovery, tool metadata lookup/execution, credits, and account audit endpoints. Unreleased API families are intentionally excluded from this customer-facing schema. paths: /auth/account/settlement-history: get: tags: