← Documentation

EVIDIQ Atlas

Reproducible research for large datasets. Give an agent CSV, JSON, NDJSON, or Parquet and receive bounded analysis, chart specifications, content-addressed artifacts, and a canonical report that can be verified independently.

Live on OKX.AI

EVIDIQ Atlas

Agent #9023

OKX.AI listing

https://www.okx.ai/agents/9023

Hire this agent directly from the marketplace.

Open

MCP endpoint

https://mcp.evidiq.dev/atlas/mcp

Streamable HTTP, x402-gated. Free tools answer without payment.

Quickstart

Connect the Streamable HTTP MCP endpoint, inspect capabilities, and validate the exact source before making a paid call.

claude mcp add --transport http evidiq-atlas https://mcp.evidiq.dev/atlas/mcp

Or probe the live pricing discovery endpoint:

curl -s https://mcp.evidiq.dev/atlas/x402

Prefer a Skill file? Fetch the agent-readable EVIDIQ Atlas Skill:

curl -s https://mcp.evidiq.dev/atlas/skill.md

What Atlas is for

Data quality

Infer schema and surface missingness, cardinality, distributions, duplicate estimates, and outliers.

Read-only analytics

Ask precise questions with one bounded DuckDB SELECT or CTE.

Visualization

Return deterministic Plotly-compatible specifications without copying Plotly source.

Version comparison

Measure row, schema, null-rate, distinct-count, and key-overlap drift.

Longer research

Combine profiles, correlations, IQR checks, and monthly trends into one canonical, optionally signed report.

Evidence

Retain dataset digests, methods, assumptions, warnings, artifacts, and optional 0G anchors.

Atlas is intentionally not a generic coding or vibe-coding agent. It exposes no user-authored Python, JavaScript, shell, package installation, database attachment, or arbitrary file export.

Dataset sources

Inline sources support CSV, JSON, and newline-delimited JSON. Public remote URLs additionally support Parquet. A source object is explicit so Atlas never guesses whether a string is data or a URL.

{
  "kind": "inline",
  "format": "csv",
  "name": "sales.csv",
  "data": "month,region,revenue\n2026-01,APAC,1200\n2026-02,EMEA,1450"
}
{
  "kind": "url",
  "format": "parquet",
  "name": "events.parquet",
  "url": "https://data.example.org/events.parquet"
}

Ten MCP tools

Five free tools support preflight and verification. Five paid tools have different immutable prices based on their bounded workload.

Paid analysis

Free preflight and verification

Recommended workflow

  1. Call atlas_capabilities for current formats and limits.
  2. Call validate_dataset_source; remote validation checks URL and DNS without downloading content.
  3. Call estimate_cost for the intended operation.
  4. Submit one paid call per request. Atlas rejects batches with multiple paid calls instead of undercharging.
  5. Preserve the report/artifact IDs and verify reports received from another party.

Payment settles before the bounded operation begins and covers the allocated attempt, including safe fetch and computation. Free validation exists to catch malformed or unsafe input first.

Read-only SQL

A single dataset is exposed as table dataset. Atlas accepts exactly one SELECT or WITHstatement and applies row, response-size, memory, and time limits.

{
  "source": { "kind": "url", "format": "parquet", "url": "https://data.example.org/sales.parquet" },
  "sql": "SELECT region, sum(revenue) AS total FROM dataset GROUP BY region ORDER BY total DESC",
  "rowLimit": 500
}

Atlas rejects external readers, globbing, extension install/load, ATTACH, COPY, DDL, DML, multiple statements, system schemas, table functions, environment/settings introspection, and volatile expressions such as random, UUID, or current-time functions. Ad-hoc SQL reports are marked deterministic only when the outer query has an effective ORDER BY; otherwise the report records deterministic: false.

Visualization

visualize_dataset emits a deterministic Plotly-compatible JSON specification. The caller controls rendering; Atlas does not execute browser code.

{
  "source": { "kind": "inline", "format": "csv", "data": "month,revenue\n2026-01,1200\n2026-02,1450" },
  "chart": { "type": "line", "x": "month", "y": "revenue", "title": "Monthly revenue" }
}

Reports and artifacts

Every paid result carries a complete report body: request parameters, dataset digests, engine version, result, methods, assumptions, warnings, and reproducibility metadata. Atlas computes SHA-256 over canonical JSON for the complete body and adds an EIP-191 signature when its signer key is configured.

{
  "reportId": "atlas_report_…",
  "body": {
    "schemaVersion": "evidiq.atlas.report.v1",
    "tool": "profile_dataset",
    "datasets": [{ "digest": "sha256:…", "format": "csv", "bytes": 18422 }],
    "methods": ["DuckDB schema inference", "descriptive statistics"],
    "warnings": []
  },
  "integrity": {
    "algorithm": "sha256",
    "canonicalization": "evidiq-jcs-v1",
    "digest": "sha256:…",
    "signature": "0x…",
    "signer": "0x…"
  }
}

Report verification separates integrity from trusted authenticity. An unsigned report can have a valid structure, derived report ID, and body digest, but valid and authentic become true only when its EIP-191 signature matches an explicit expectedSigner or the deployment's configured trusted signer.

Artifacts are file-backed and content-addressed. Their ID-derived kind, digest, byte count, content type, and canonical content are checked on retrieval. They provide integrity and reproducibility, not authorization; deployments must protect sensitive artifact IDs and apply their own data policy.

Remote-fetch and runtime security

DuckDB, E2B, and 0G

DuckDB is Atlas's primary engine because its MIT-licensed in-process OLAP runtime fits CSV/JSON/Parquet and bounded read-only SQL. E2B is retained behind an optional provider boundary, but Atlas v1 honestly keeps deterministic tools on DuckDB and does not expose E2B's generic code runtime.

0G Storage anchoring is optional and best-effort. Its public, privacy-minimized record contains only the report ID, fixed integrity labels and report-body digest, plus each dataset's format, digest, and byte count. It excludes artifact IDs/digests/kinds, dataset names, source URLs, signatures, signer addresses, raw datasets, results, samples, and query rows. A storage failure is surfaced as storageNote and does not falsify the local report.

x402 pricing

ToolAtomicUSDT0Access
profile_dataset50000.005x402
query_dataset100000.01x402
visualize_dataset150000.015x402
compare_datasets200000.02x402
research_dataset300000.03x402
atlas_capabilities0FreeAlways ungated
validate_dataset_source0FreeAlways ungated
estimate_cost0FreeAlways ungated
verify_atlas_report0FreeAlways ungated
get_artifact0FreeAlways ungated

Payments use x402 v2 exact with USDT0 (6 decimals) on X Layer (eip155:196). The public discovery endpoint lists all ten tools. If a broadcast settlement is awaiting confirmation, Atlas returns HTTP 202 with its transaction hash; retry the same authorization so confirmation can be checked without broadcasting or paying again. Ambiguous facilitator settlement returns a service error instead of a new 402 challenge.

Verification and settlement run through the official OKX Onchain OS Payment SDK (@okxweb3/x402-core and @okxweb3/x402-evm). The OKX facilitator verifies each authorization and settles it on X Layer before an analysis begins. Each immutable per-tool price reaches the SDK as an explicit USDT0 atomic amount, so neither the fee nor its token can be substituted by currency conversion.

Settled on X Layer

A live profile_dataset call paid 0.005 USDT0 (5000 atomic), settled through the OKX facilitator, and returned a canonical dataset profile.

0x3ea2fa7947eabcfb6527702700b57d6c760cffe6bc356b048528a8468115da6c

Licensing

EVIDIQ owns and licenses its original Atlas integration code under MIT. DuckDB, E2B, the 0G SDK, MCP SDK, and other dependencies remain third-party technology under their own licenses. Atlas consumes pinned packages, does not copy upstream source, and preserves notices in THIRD_PARTY_NOTICES.md and package distributions.

Atlas produces reproducible descriptive evidence, not a guarantee that a source is complete, unbiased, legally usable, or causally explanatory. Review source provenance, sampling, units, and domain assumptions before acting on a result.

← Back to docs