edi.edifact-generate

Generate an outbound UN/EDIFACT document from JSON — the international counterpart to edi.generate (X12). POST type ('ORDERS' = purchase order or 'INVOIC' = invoice) + senderId, recipientId (with optional qualifiers), documentNumber, optional date (CCYYMMDD), parties (NAD role+name, e.g. BY buyer / SU supplier / IV invoicee), items (quantity, productId, price), and for INVOIC an optional total. Returns the full EDIFACT interchange in meta.edi — a correct UNA/UNB/UNH…UNT/UNZ envelope with BGM, DTM, NAD, LIN/QTY/PRI, MOA/CNT — with proper delimiters and release-character escaping. Deterministic, no external calls. Round-trips through edi.edifact.

price
$0.0018 USDC per call
method
POST/api/edi/edifact-generate
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The edifact generate API is a pay-per-call edi endpoint built for AI agents and autonomous software. Generate an outbound UN/EDIFACT document from JSON — the international counterpart to edi.generate (X12).

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in edifact generate data source for an agent tool-use loop, an MCP host, or a backend that needs edi data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
typerequiredstring
one of: ORDERS | INVOIC
senderIdrequiredstring
min 1 chars · max 35 chars
recipientIdrequiredstring
min 1 chars · max 35 chars
senderQualifierstring
min 1 chars · max 4 chars
recipientQualifierstring
min 1 chars · max 4 chars
documentNumberrequiredstring
min 1 chars · max 35 chars
datestring
min 6 chars · max 8 chars
partiesarray
itemsrequiredarray
totalnumber
controlRefstring
max 14 chars

Code samples

cURLbash
# 1. Probe the endpoint with no auth — receive 402 with PaymentRequirements
curl -sS -X POST 'https://2s.io/api/edi/edifact-generate' \
  -H 'Content-Type: application/json' \
  -d '{"type":"ORDERS","senderId":"example","recipientId":"example","senderQualifier":"example","recipientQualifier":"example","documentNumber":"example","date":"xxxxxx","parties":[{"role":"example","name":"example"}],"items":[{"quantity":1,"productId":"example","price":1,"idType":"example"}],"total":1,"controlRef":"example"}'

# 2. Sign the EIP-3009 transferWithAuthorization for the advertised price +
#    payTo from the 402 envelope, then retry with PAYMENT-SIGNATURE:
curl -sS -X POST 'https://2s.io/api/edi/edifact-generate' \
  -H 'Content-Type: application/json' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>' \
  -d '{"type":"ORDERS","senderId":"example","recipientId":"example","senderQualifier":"example","recipientQualifier":"example","documentNumber":"example","date":"xxxxxx","parties":[{"role":"example","name":"example"}],"items":[{"quantity":1,"productId":"example","price":1,"idType":"example"}],"total":1,"controlRef":"example"}'

# Or just use the canonical runner — it handles the whole loop:
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/edi/edifact-generate'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.edi.edifactGenerate({
  "type": "ORDERS",
  "senderId": "example",
  "recipientId": "example",
  "senderQualifier": "example",
  "recipientQualifier": "example",
  "documentNumber": "example",
  "date": "xxxxxx",
  "parties": [
    {
      "role": "example",
      "name": "example"
    }
  ],
  "items": [
    {
      "quantity": 1,
      "productId": "example",
      "price": 1,
      "idType": "example"
    }
  ],
  "total": 1,
  "controlRef": "example"
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.edi.edifact_generate(type="ORDERS", senderId="example", recipientId="example", senderQualifier="example", recipientQualifier="example", documentNumber="example", date="xxxxxx", parties=[{"role":"example","name":"example"}], items=[{"quantity":1,"productId":"example","price":1,"idType":"example"}], total=1, controlRef="example")

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "edi.edifact-generate",
    "arguments": {
      "type": "ORDERS",
      "senderId": "example",
      "recipientId": "example",
      "senderQualifier": "example",
      "recipientQualifier": "example",
      "documentNumber": "example",
      "date": "xxxxxx",
      "parties": [
        {
          "role": "example",
          "name": "example"
        }
      ],
      "items": [
        {
          "quantity": 1,
          "productId": "example",
          "price": 1,
          "idType": "example"
        }
      ],
      "total": 1,
      "controlRef": "example"
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {
      "controlRef": "example",
      "segmentCount": 1
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "edi": "example"
  }
}

FAQ

Do I need an API key to use the edifact generate API?
No. edi.edifact-generate is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the edifact generate API cost?
$0.0018 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the edifact generate API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call edi.edifact-generate from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: edifact generate api · edi edifact generate api · edifact generate api for ai agents · x402 edi api · edifact generate api no api key · pay per call edifact generate api · edi api