# 2s EDI X12 Parser

> 2s EDI X12 Parser is a paid API for AI agents from 2s.io, paid per call via x402, $0.0018/call, status unknown (last checked 2026-09-15).

Parses raw X12 EDI interchange text and returns structured JSON with transaction sets, segments, delimiters, and document summaries

## Facts

- Endpoint: POST https://2s.io/api/edi/parse
- Price: $0.0018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/2s-edi-x12-parser-54438c59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DOxcPdKuynrCmGCUhwlU1

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability 2s-edi-x12-parser-54438c59 -d '<json body>'
```

Example prompt: Can you parse this raw X12 EDI interchange for me and tell me what transaction type it is, who the sender and receiver are, and break out the individual segments? Here's the data: ISA*00* *00* *ZZ*ACME *ZZ*BUYERCORP *240115*1200*^*00501*000000001*0*P*>~GS*PO*ACME*BUYERCORP*20240115*1200*1*X*005010~ST*850*0001~BEG*00*SA*PO-99012**20240115~PO1*1*10*EA*25.00**VP*WIDGET-A~CTT*1~SE*4*0001~GE*1*1~IEA*1*000000001~

## When to prefer this

Use this endpoint when you have raw X12 EDI text (beginning with ISA) that you need to decode into structured JSON — especially for 850 purchase orders, 810 invoices, or other X12 transaction sets in B2B supply chain workflows. Prefer this over manual parsing or custom EDI libraries when you need fast, pay-per-call parsing without setup, API keys, or subscription overhead.

## Known failure modes

- Invalid or malformed EDI text that doesn't begin with ISA returns an error
- Missing required ISA segment structure causes parse failure
- Unsupported X12 transaction set types may parse segments but lack rich summary fields
- Empty edi field or non-string input returns validation error
- Payment failure (402) if USDC balance insufficient

## How this service works

The (most) everything API: 575+ pay-per-call endpoints for AI agents — ground-truth data, a full AI gateway, and agent infrastructure (storage, queues, watchers). USDC via x402, no signup, no API keys, and upto billing: pay actual usage, not the quote.

## Output

Returns a JSON object with ok:true, interchange metadata (sender ID, receiver ID, usage mode), delimiter characters, segment count, functional group count, and an items array where each entry contains the transaction set type (e.g. '850'), a human-readable typeName, a summary with PO number/date/line item count, an array of decoded segments with tag names and element values, and control numbers. Total transaction count is also included.

## Example request

```json
{
 "edi": "ISA*00* *00* *ZZ*SENDER123 *ZZ*RECEIVER456 *240115*1200*^*00501*000000001*0*P*>~GS*PO*SENDER123*RECEIVER456*20240115*1200*1*X*005010~ST*850*0001~BEG*00*SA*PO-12345**20240115~PO1*1*5*EA*50.00**VP*PRODUCT-001~CTT*1~SE*4*0001~GE*1*1~IEA*1*000000001~"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edi": {
   "type": "string",
   "description": "Raw X12 interchange text (begins with ISA)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/2s-edi-x12-parser-54438c59/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 2s.io](https://www.zero.xyz/host/2s.io/llms.txt)