Anything in.
Anything → out.

Turn business CSV rows into structured JSON — or JSON into compliant X12. One metered API, structure-aware through a shared canonical model. Not regex surgery.

API base: transform.edibridge.com/v1

Try the API See pricing

POST /v1/transform?from=csv&to=json live

In — business CSV (v1 schema)

PO_Number,Order_Date,Item_UPC,Quantity,...
6284850222,2026-04-05,012345678901,72,...
6284850222,2026-04-05,012345678902,48,...

Out — JSON

{
  "po_number": "6284850222",
  "order_date": "2026-04-05",
  "lines": [{
    "upc": "012345678901",
    "qty": 72
  }, { "upc": "012345678902", "qty": 48 }]
}

One engine, five directions live

Every transform runs reader → canonical → writer. Qualifiers, loops, and envelopes survive because the hub understands business documents — not because we flattened strings. X12 depth when retail shows up; CSV and JSON when you're building the pipe.

POST /v1/transformCSV · JSON · X12 live

csv→json, json→csv, csv→x12, x12→json, json→x12 — JSON generation uses documentType (810, 856, 997, 850). XML and flat files are on the roadmap, not shipped.

POST /v1/validateRetailer profiles live

Baseline 850 checks plus ?profile=walmart add-ons. Findings ranked fatal / warning / info. 10 free validates per IP per day — then $0.25/file.

CSV v1 contractConvention-based, stateless

Public lane expects the documented 12-column header set (PO_Number, Order_Date, Ship_To_*, Item_UPC, …). Wrong headers → 400 with csv_schema in the body. Custom layouts → /v1/map or EDIBridge SaaS FieldMaps.

PO_Number, Order_Date, Ship_To_Name, Ship_To_Address, Ship_To_City, Ship_To_State, Ship_To_Zip, Item_UPC, Item_Description, Quantity, Unit_Price, Unit_Of_Measure

POST /v1/mapAI field mapping coming soon

Headers the engine has never seen → confidence-scored X12 mapping with reasoning attached. Never free — agents chain on honest scores.

Try it now

Live on transform.edibridge.com/v1 — structure-aware transforms and retailer-profile validation.

CSV → JSON

$ curl -X POST \
  "https://transform.edibridge.com/v1/transform?from=csv&to=json" \
  --data-binary @sample_850.csv

Validate (Walmart profile)

$ curl -X POST \
  "https://transform.edibridge.com/v1/validate?profile=walmart" \
  --data-binary @po_850.edi

Health check: GET …/health returns supported_directions. Rate limits: 60 transforms/min per IP; validate free tier 10/day per IP.

Agent-native

Built for pipelines and agents

MCP tools — live at transform.edibridge.com/mcp (transform_document, validate_edi). Prices in tool descriptions; free preview until billing ships.
Prepaid API credits — coming at launch (Stripe packs). No subscription required for meter-only use.
Machine-readable errors — every response includes code, message, and docs_url. The caller is code.

Validate response shape

HTTP/2 200
{ "valid": false,
  "profile_applied": "walmart",
  "findings": [{
    "severity": "fatal",
    "segment": "PO1",
    "code": "MISSING_UP",
    "message": "Line 3 has no UPC qualifier"
  }] }

Prices on the page

Published launch pricing. Meter turns on when billing ships — transforms and paid validates are per call, not per seat.

What	Price
/v1/transform	$0.05 / document	Any shipped direction (see health)
/v1/validate 10 free / day	$0.25 / file	Retailer-profile report — live now
/v1/map soon	$0.75 / call	AI mapping with confidence scores
order cycle	$0.35 / order	850 → 855 → 856 → 810, priced once (at launch)

monthly minimums setup fees per-partner charges sales calls lock-in

Doing real monthly volume?

Past a couple hundred documents a month, EDIBridge SaaS is the better deal — Self-Managed from $49/mo or Managed from $199/mo ($349 for multi-partner), with human support, SFTP/AS2 endpoints, and QuickBooks sync.

See edibridge.com pricing

Just here to transform?

Point curl — or your agent — at the API today. OpenAPI spec for codegen; MCP for agent toolchains. Buy credit packs at launch; the meter is the whole relationship if that's all you need.

/v1/openapi.json live · /mcp live

Anything in.Anything → out.