Do you replace Flatfile or Redox?

No. We are not a generic CSV importer and not a full integration engine. AdaptivMapr is a self-serve schema-mapping layer for regulated data — it maps CSV/Excel/SQL/JSON to your schema (FHIR for healthcare, your shape for finance and PII) without the cost or complexity of a heavyweight integration project.

Schema mapping for regulated data

Any messy file in.
Your clean schema out.

Map any CSV, Excel, SQL, or JSON to your schema — without shipping raw records to an LLM. Data-minimized schema-only mode; full-data PHI is routed in-region under a BAA.

Get an API key How it works →

Raw records stay putPHI in your region (BAA)FHIR R4 emit

A messy file goes in; transform code is generated from its structure — never your rows; a clean workbook comes out, in one call.

CSV
Excel
JSON
SQL
XML
PDF
Images
Audio
URLs
→ your schema →
FHIR R4
LOINC
ICD-10
ATC
CPT
NPI
IBAN
BIC
GTIN
GLN

The engine

One API, from messy file to your schema.

The same cascade engine maps, reshapes, converts, validates and emits — five capabilities behind one endpoint, so a broken export becomes clean, schema-shaped rows without a bespoke pipeline per source.

Messy headers land on your schema

Vorname, prénom, e-mail, DOB — multilingual, misspelled, reordered. The cascade resolves each source header to the right field of your schema, and only escalates the genuinely ambiguous ones to a model.

Learn more

Integrate

Two on-ramps. One engine.

The cascade is the product; everything else is an adapter around it. Drive it programmatically over REST, or hand it to your agent — and get the exact same mappings, validators, and audit trail either way.

REST API

Call /v1 from anything.

A standard REST surface. Point your existing HTTP client at it and embed mapping straight into your import flow.

HMAC self-contained keys (mp_live_) — authenticated with no key-lookup latency.
upload → match → validate → commit, or one-shot it with /v1/transform, /v1/convert, /v1/reshape.
Inline results or HMAC-signed webhook batches — you pick per request.
Idempotency keys on every POST make retries safe.

curl

# Upload — only headers + 3 sample rows leave you (schema-only mode)
curl -X POST https://api.adaptivmapr.com/v1/uploads \
  -H "Authorization: Bearer mp_live_…" \
  -F "file=@patients.csv" \
  -F "template=patient_demographics_v1"

# …or skip the steps and one-shot it
curl -X POST https://api.adaptivmapr.com/v1/transform \
  -H "Authorization: Bearer mp_live_…" -F "file=@patients.csv"

Read the API docs →

MCP & dashboard

Or map without writing code.

Give your agent the engine as a tool, or drive it by hand in the browser. Same cascade, same templates — zero SDK.

MCP server for Cursor / Claude Desktop — no-key tools: list_templates, match_headers, validate_row, csv_preview.
The Workbench — paste anything or drop a doc, get mapped rows back.
One-click layout reuse replays a confirmed mapping for a header row you have seen before.

mcp.json

{
  "mcpServers": {
    "adaptivmapr": {
      "command": "npx",
      "args": ["-y", "@adaptivmapr/mcp-server"]
    }
  }
}

Set up MCP →

Why AdaptivMapr

Cheaper than scripts. Safer than a chatbot.

Two things teams reach for to get data into their schema: a pile of hand-coded ETL, or pasting the file into a chatbot. One is expensive to maintain; the other ships your raw records to a model. Here is the side-by-side.

Mapping to your schema	AdaptivMapr	Hand-coded ETL / scripts	Raw LLM (paste to a chatbot)
Handles messy real files (offset/merged headers, transposed sheets)	Yes — structural detection	Manual per file	Unreliable
Raw records sent to an LLM	No in schema-only — headers + ≤3 rows only	No	Yes — the whole file
Deterministic & reproducible	Yes — layers 1–3 + declarative plan	Yes	No
Multilingual header matching (DE/FR/IT/EN/ES)	Built-in hints	Hand-written	Inconsistent
Checksum-strict validation (IBAN/LOINC/NPI…)	19 validators	DIY	None
FHIR R4 / code-system output	Native	Heavy	No
PHI / BAA path	in-region, under a BAA	Your burden	No
Cost on a typical file	Mostly free deterministic layers	Engineering time	Per-token, every row

Fair caveat: hand-coded ETL is hard to beat when you own one stable format forever — but the moment inputs drift or a new source lands, the per-file cost compounds. And a chatbot is fine for a throwaway one-off you can eyeball. AdaptivMapr earns its place on the recurring, regulated, multi-source imports where correctness and a clean audit trail are non-negotiable.

Ready when you are

One key, from messy file to your schema.

Start with a $10 prepaid wallet — every map draws a few tokens, and in schema-only mode only headers and a few sample rows ever leave you. Full-data cleanup, FHIR emit, and BAA coverage run on the same balance.

Get an API key See pricing →

$10 minimum to start · pay only for what you map · PHI under BAA coverage

FAQ

Straight answers before you ask.

How is schema-only mode priced?

There is no free tier — you top up a prepaid token wallet (from $10, shared across our suite) and every map draws a small flat fee, a few tokens, including deterministic maps. Schema-only is a data-minimization mode: only your column headers and up to 3 clamped sample rows (≤80 chars each) are processed; raw records never leave you. (A DPA/BAA may still apply depending on the data; we provide one on request.)

Does AdaptivMapr store my regulated data?

In schema-only mode we store nothing beyond the clamped samples (headers + ≤3 truncated rows); raw records never leave you. The mapping engine itself is stateless; account metadata and audit logs persist only where persistence is enabled. In full-data mode, sensitive payloads are routed to a PHI-eligible provider for the LLM step and are not retained by us.

Do you replace Flatfile / Redox?

No. We are not a generic CSV importer and not a full integration engine. AdaptivMapr is a self-serve schema-mapping layer for regulated data — healthcare, finance, and PII — that maps CSV/Excel/SQL/JSON to your schema (and emits FHIR for healthcare) without the cost or complexity of a heavyweight integration project.

Are you HIPAA certified?

HIPAA is not a certification anyone can hold. What we offer is a BAA, a HIPAA security risk assessment (SRA) on file, GDPR-friendly handling, and SOC 2 in progress. We say "HIPAA-ready," never "HIPAA certified."

Any messy file in.Your clean schema out.