Ragora Skill for OpenClaw

Use this skill to answer questions with Ragora data. You have two integration paths:

1. MCP (Model Context Protocol) — preferred when your client supports MCP tool binding.
2. REST API — use directly via HTTP when MCP is unavailable or when you need fine-grained control.

Both paths share the same authentication, data model, and search capabilities.

Source of Truth Docs

Consult these docs first when behavior differs across environments:

• MCP guide: https://ragora.app/docs?section=mcp-guide
• Getting started: https://ragora.app/docs?section=getting-started
• API overview: https://ragora.app/docs?section=api-overview
• Retrieve API: https://ragora.app/docs?section=api-retrieve
• Errors and limits: https://ragora.app/docs?section=api-errors
• Billing API: https://ragora.app/docs?section=api-billing

Core Concepts

Before using any tools, understand the Ragora data model.

Collections

A collection is a knowledge base — a curated set of documents indexed for semantic search. Each collection has:

• Name — human-readable label (e.g., "Employee Handbook").
• Slug — URL-safe identifier used in dynamic tools and API paths (e.g., employee_handbook).
• Description — what the collection contains and when to use it.
• Stats — document count, chunk count, last updated timestamp.

Documents & Chunks

Each collection contains documents (files, pages, articles). Documents are split into chunks — small passages optimized for semantic retrieval. When you search, results are returned at the chunk level with metadata pointing back to the source document.

Versions

Some collections support versioned documentation (e.g., API docs v1.0, v2.0). Use list_versions_{slug}() or the API to discover available versions, then pass a version parameter to scope your search.

Tags & Filters

Collections may support:

• Custom tags — string labels attached to documents (e.g., ["legal", "msa", "2024"]). Pass as custom_tags to narrow results.
• Filters — key-value metadata filters (e.g., {"region": "US", "department": "engineering"}). Pass as filters to constrain results.

Credits & Billing

• Own collections and subscriptions — free MCP/API access, no credit cost.
• Marketplace products (pay-per-use) — each retrieval deducts credits based on seller pricing.
• Credits are measured in USD. Check with check_balance() or GET /v1/billing/balance.
• Top up at https://app.ragora.app/settings/billing.

Connection Setup

Authentication

All requests (MCP and REST) require a Ragora API key.

• Format: sk_live_<uuid> (e.g., sk_live_a1b2c3d4-e5f6-7890-abcd-ef1234567890)
• Create one: https://app.ragora.app/settings/api-keys
• Shown once — copy and store it securely at creation time.
• Hashed on server — SHA-256 + bcrypt. Ragora cannot recover a lost key; generate a new one.

Security rules