VAREXIS Technologies

VAREXIS-INDEX

Source-linked evidence for human and agent workflows. Read free; save a version-bound record when you need it.

Automatic published-route retrieval is live. The separate v0.9 qualification runtime remains local-only and is not exposed as a public API.

Review MCP and agent tool permissions

Preview an answer for free
VAREXIS-INDEX identity: stacked blue geometric planes with a luminous V on the top plane.

Live evidence retrieval

Find the answer. Preserve the version you used.

Read the complete answer, sources and limits free. Pay when you need a saved, version-bound record for later retrieval. The purchase adds no fresh investigation or assessment of a new claim.

Evidence Packs: benefits, included questions and saved delivery

Agentic Production Pathway: free evidence, Tool Admission and Audit Coverage

Connect an agent and see worked examples

Live retrieval API contract

Catalogue and search coverage

The public catalogue contains 1,817 records. Existing MCP search and saved retrieval cover the frozen 1,003-record baseline. The 814 additions are free to read and save locally through their exact HTTP JSON links; enhanced natural-language discovery is not yet qualified for them.

Browse the free evidence additions · Exact record and route IDs (JSON) · Coverage manifest

Agents can also use the separate read-only catalogue connector at https://varexis.tech/mcp/catalogue. Call browse_publication_catalogue with an optional exact category, then get_publication_record with one returned record or route ID. Each read includes the original evidence, hash, source dates and rights notices. There is no fuzzy search or related-evidence fallback.

Catalogue MCP setup, categories and exact identifiers (JSON). Existing four-tool clients keep their current endpoint. Versioned publication manifests retain their original HTTP access declarations; this separate interface adds access without changing them.

These additions remain outside the original MCP preview and paid saved retrieval. Existing products, licences and subscriptions are unchanged.

Current public INDEX coverage

Find published answers and trace the evidence behind them. The catalogue combines VAREXIS evidence summaries, external documentation reviews and derived claim boundaries for human and agent retrieval.

Counts describe the public evidence-routing surface. They do not represent independent experiments, certification, advice, deployment approval or authority to act.

Search the frozen software advisory collection

Published routing surface

1,817
Public records — Evidence summaries, external documentation references and derived claim-boundary records.
1,917
Agentic routes — Published question-to-record routes for agent and human discovery.
13,791
Distinct near-question hooks — Deduplicated wording hooks across records, routes and contexts.
304,384
External advisory source records — Frozen OSV affected-package assertions, counted separately from reviewed entries. Not independently verified findings.

Compatible agents can buy one-time snapshots with MPP/Stripe SPT. Check the API contract and availability; owner spending authority is required.

Single Request

£5 + VAT

One saved published-route answer, bound to its source versions and limitations.

Evidence Receipt

£19 + VAT

The saved answer plus an unsigned delivery receipt identifying the snapshot and delivery time.

Research

£29/mo + VAT

Recurring saved-route retrieval and exports, subject to operational rate limits.

Developer/API

£149/mo + VAT

100 new published-route queries per paid monthly period. A retry with the same request reference reuses the saved result.

VAT is calculated at checkout where applicable. Monthly plans renew until cancelled. All plans use the same published evidence; no additional private evidence corpus is included.

Access, delivery and limits

Keep the access key private and save it outside the browser tab. It controls retrieval and subscription queries; automatic email key recovery is not available. API callers send it in the Authorization header. Routine delivery needs no request email.

Delivery requires payment verification. Retry the original API with your key; MPP retries keep the original credential. Do not pay again. For unresolved delivery, use billing support. Refund requests follow the checkout terms; a failed retrieval does not automatically issue a refund.

The paid Evidence Receipt is unsigned. Signed verification receipts and attestations belong to the separate local qualification engine described below. Purchases do not include fresh experiments, bespoke advice, certification, BDAS/AURIC access or authority to deploy.

Questions the evidence can help with

Check the claim before relying on it.

Does exact output prove a speedup?

The supplied Backblaze D2 review reports exact development replay without performance qualification. The entry preserves that distinction and the limits of the review.

Read the D2 evidence boundary

Can a result transfer to my workload?

The PUMP-E2C record separates its evaluated setting from broader production claims. Use the conditions and exclusions to decide what further evidence your own workload needs.

Read the PUMP-E2C scope

Browse the evidence catalog

Evidence and machine contract

Architecture, routing model and machine-readable boundaries.

The architecture, capability groups, verification states and signed artifacts below describe the separate local-only qualification engine. They are not automatically included in the live published-route retrieval purchase.

Public INDEX records support discovery and bounded retrieval. Authentication permits API operations; it does not create truth, certification, advice or authority to act.

Architecture

From source to current state.

The implemented local build connects source-linked records, historical verification and maintained current-state observations.

  • Maintained, not static.
  • Versioned, not overwritten.
  • Evidence-linked, not confidence theatre.
  • Machine-queryable, not merely human-readable.

Routing model

How a claim becomes a bounded machine-readable response

Public abstraction only. The model shows evidence movement and authority boundaries, not implementation detail.

Cryptographic receipts and current-state attestations remain separate. Authentication permits API operations; it does not create truth or authority to act.

Deeper local qualification detail

Local qualification, evidence-state separation and attestation detail remains available for technical review without hiding the main architecture.

Executable core · v0.9 qualification integration

Implemented and locally validated.

Records and evidence

  • Versioned claim and source records
  • Explicit evidence bindings
  • Verification tiers
  • Evidence posture
  • Contradiction retention
  • Revision history

History and verification

  • Dependency-impact traversal
  • Deterministic index snapshots
  • Ed25519 signed verification receipts
  • Historical-vs-current status comparison
  • Deterministic machine verification bundles

Maintenance and acquisition

  • Bounded source-maintenance scheduling
  • Controlled HTTPS source acquisition
  • Source-change detection
  • Revalidation queues
  • Signed acquisition-aware current-state attestations

Requests and service boundary

  • Demand and prioritisation records
  • Verification request lifecycle
  • PostgreSQL persistence
  • Tenant-bound authenticated service identity
  • Credential scopes, rate admission and access audit

Separate dimensions of verification.

Verification tier describes the recorded assessment. Evidence posture describes the claim's relationship to evidence. Claim lifecycle, source-maintenance state, request state and outstanding revalidation remain separate dimensions.

Verification tier

Declared
An assertion recorded without independent source checking.
Source checked
An assertion checked against attributable source material.
Independently tested
Relevant independent evidence or testing recorded within the claim's scope.

Evidence posture

  • Unbound
  • Partial
  • Bound
  • Contradicted
  • Halted

These are record classifications. They do not describe external validation of VAREXIS-INDEX or confer permission to act.

Historical authenticity. Current-state observation.

Signed historical receipt

Binds an issued verification record to a deterministic snapshot. Its signature can remain authentic after the underlying indexed state changes.

Signed current-state attestation

Reports current claim status, source maintenance, unresolved revalidation and dependency impact at a specific time. It remains separate from the historical receipt.

Cryptographic authenticity does not establish truth, correctness or current validity.

Machine contract

Separate local qualification contract.

Qualification contract published; the separate v0.9 qualification engine is locally implemented only and is not exposed as a public API.

VAREXIS-INDEX informs evidence reliance; it does not grant authority to deploy or act.

Local observation interface.

Local read-oriented and authenticated service interfaces have been implemented and validated within their stated scopes.

Automatic published-route retrieval is available through /index-access and the /api/index interface; check /api/index/capabilities for checkout availability. The separate v0.9 qualification runtime remains local-only and is not exposed as a public API. Paid snapshots do not perform fresh research or bespoke qualification.

Local validation evidence.

VAREXIS-INDEX v0.9 qualification integration completed 809/809 local tests, including 16 qualification-contract tests; historical disposable PostgreSQL 18.6 validation completed 45/45 on the fresh 0001→0002→0003 path and 43/43 on the controlled 0001+0002→0003 upgrade path.

Internal/local and disposable integration evidence only. This is not production deployment validation, independent verification or certification.

Evidence context

NVIDIA Inception

VAREXIS Ltd is an NVIDIA Inception program member.

NVIDIA, the NVIDIA logo and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.

UKRI AI Research Resource (AIRR) - Isambard-AI

Compute access awarded through the UKRI AI Research Resource for BDAS evaluation on Isambard-AI.