Core

Users

User directory: identity, contact, role, and onboarding metadata.

low riskusers_v1

Schema

The canonical field set, printed as it ships.

7 fields with multilingual hints (DE / FR / IT / EN / ES) and field-level validators. Any source column that resolves to one of these is mapped by the cascade — most of them on the deterministic layers, with no LLM call.

users_v1
fields
7
required
2
validated
1
hints
20
Canonical columnTypeRequiredValidatorsHeader hints the cascade matches
idstringyesmatched on the column name
emailemailyesemaile-mailmailcorreocourriel
first_namestringvornameprenomprénomnombre
last_namestringnachnamenomapellidocognome
roleenumadminmemberviewerownerrollerolerolruolo
created_atdatematched on the column name
countrystringlandpayspaíspaese

Read the same definition as JSON at GET /v1/templates/users_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.

  • 7 canonical fields
  • 2 required
  • 1 validated
  • 20 header hints
  • Core pack

Try it

A real file, a real call, one template id.

8 rows, DE headers, role enum. Fully synthetic — safe to share, commit, and run in CI.

bash
curl -X POST https://api.adaptivmapr.com/v1/uploads \
  -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
  -F "file=@users_sample.csv" \
  -F "template=users_v1"
→ upload created · mappings ready · confirm before commit
mcp
adaptivmapr.match_headers({
  template_id: "users_v1",
  headers: ["id", "email", "first_name", "last_name"]
})
schema-only · headers and ≤3 clamped rows only

Ready when you are

Put users in production — without shipping raw records.

Schema-only mapping leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.

No free tier · $10 prepaid wallet to start · every map draws a small flat fee