Documentation hub

RAGO-X Documentation and Adoption Guide

This hub helps teams evaluating or adopting RAGO-X quickly find its capabilities, constraints, and operating model.

Written and reviewed by the icube-x RAGO-X product teamLast updated: 2026-11-09

Understand the product

The product overview explains the problem RAGO-X solves, its core workflow, and organization features.

  • Document ingestion and knowledge bases
  • Grounded RAG answers
  • Project, cabinet, and user permissions
  • RAG testing and QA management

Adoption information

Dedicated guides cover security, supported document formats, API integrations, and the answer workflow.

  • Security and data handling
  • Supported formats and limits
  • API and service integrations
  • Search, answer, and evidence workflow

Use current information

Product specifications and plans can change. Confirm contractual or security-sensitive requirements through sales or customer support.

From first setup to a working integration

Start with representative supported files and check processing, answers, and cited passages in a cabinet. For a team, configure organization roles separately from cabinet access groups. To connect an existing service, follow the API guide through key creation, cabinet discovery, question submission, and streaming. The detailed guides below include configuration steps and request examples.

Validate answers with your first document

Start with one current document whose answers you can verify yourself. Check supported formats and your plan limits, upload it to a cabinet, and check processing status. Upload acceptance alone does not mean the document is ready for retrieval.

  • Record the document title, version and effective date
  • Ask questions in the cabinet after processing completes
  • Compare cited passages with the original document
  • Record the expected answer, evidence and any errors together

Three questions for an adoption evaluation

For a travel-policy evaluation, prepare a direct lookup, a question that distinguishes conditions, and a question with no answer in the document. These are test examples, not statements of your company policy.

  • Direct lookup: What is the expense-submission deadline?
  • Conditions: How do domestic and international travel approvals differ?
  • Missing evidence: Is an exception expense absent from the policy reimbursable?
  • Acceptance check: Verify support in the correct document version and check that missing rules are not invented

When an answer differs from expectations

Check the selected cabinet and processing status first, then the document version and the context of the cited passage. Record retrieval failures separately from misinterpretation of retrieved evidence to identify what needs correction. Before inviting a team, test both allowed and disallowed cabinets with a member account as well as an administrator account.