Do I need an API key to use the generate API?

No. edi.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 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 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.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.

edi.generate

Generate a ready-to-send ANSI ASC X12 EDI document from structured JSON. POST type ('850' Purchase Order, '810' Invoice, or '856' Ship Notice/ASN) plus senderId, receiverId, documentNumber (PO#/invoice#/shipment id), optional date, parties (N1 loops — role like ST/BT/VN + name), and items (quantity, uom, price, productId). For an 810 you can pass poNumber and total; for an 856 pass poNumber (the PO shipped). Returns the full X12 interchange in meta.edi — correct ISA/GS/ST…SE/GE/IEA envelope, party loops, PO1/IT1 line items (or the 856 HL Shipment→Order→Item hierarchy with LIN/SN1), and CTT/TDS totals (implied 2-decimal). Deterministic, no external calls. The outbound complement to edi.parse and edi.ack: assemble valid EDI envelopes instead of hand-rolling segment terminators and control numbers.

price

$0.0018 USDC per call

method

POST/api/edi/generate

payment

x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)

auth

None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The generate API is a pay-per-call edi endpoint built for AI agents and autonomous software. Generate a ready-to-send ANSI ASC X12 EDI document from structured JSON.

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 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

Give an AI agent live generate lookups as a tool, with no API key to provision or rotate — the agent pays per call from a wallet you fund.
Enrich records in a data pipeline with edi data, paying only for the calls you actually make instead of a monthly seat.
Ground LLM answers in authoritative edi data to cut hallucination, then optionally request a signed response for verifiability.
Prototype against the live generate API in minutes using the free trial call, then flip to per-call x402 payment for production with no code change.

Parameters

Name	Type	Description
`type`required	string	one of: 850 \| 810 \| 856
`senderId`required	string	min 1 chars · max 15 chars
`receiverId`required	string	min 1 chars · max 15 chars
`senderQualifier`	string	max 2 chars
`receiverQualifier`	string	max 2 chars
`documentNumber`required	string	min 1 chars · max 60 chars
`poNumber`	string	max 60 chars
`date`	string	max 10 chars
`parties`	array
`items`required	array
`total`	number	810 invoice total in USD.
`controlNumber`	string	max 15 chars
`usage`	string	one of: P \| T

Code samples

cURLbash

# 1. Probe the endpoint with no auth — receive 402 with PaymentRequirements
curl -sS -X POST 'https://2s.io/api/edi/generate' \
  -H 'Content-Type: application/json' \
  -d '{"type":"850","senderId":"example","receiverId":"example","senderQualifier":"example","receiverQualifier":"example","documentNumber":"example","poNumber":"example","date":"example","parties":[{"role":"example","name":"example","idQualifier":"example","id":"example"}],"items":[{"quantity":1,"uom":"example","price":1,"productId":"example","idQualifier":"example"}],"total":1,"controlNumber":"example","usage":"P"}'

# 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/generate' \
  -H 'Content-Type: application/json' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>' \
  -d '{"type":"850","senderId":"example","receiverId":"example","senderQualifier":"example","receiverQualifier":"example","documentNumber":"example","poNumber":"example","date":"example","parties":[{"role":"example","name":"example","idQualifier":"example","id":"example"}],"items":[{"quantity":1,"uom":"example","price":1,"productId":"example","idQualifier":"example"}],"total":1,"controlNumber":"example","usage":"P"}'

# 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/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.generate({
  "type": "850",
  "senderId": "example",
  "receiverId": "example",
  "senderQualifier": "example",
  "receiverQualifier": "example",
  "documentNumber": "example",
  "poNumber": "example",
  "date": "example",
  "parties": [
    {
      "role": "example",
      "name": "example",
      "idQualifier": "example",
      "id": "example"
    }
  ],
  "items": [
    {
      "quantity": 1,
      "uom": "example",
      "price": 1,
      "productId": "example",
      "idQualifier": "example"
    }
  ],
  "total": 1,
  "controlNumber": "example",
  "usage": "P"
})

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.generate(type="850", senderId="example", receiverId="example", senderQualifier="example", receiverQualifier="example", documentNumber="example", poNumber="example", date="example", parties=[{"role":"example","name":"example","idQualifier":"example","id":"example"}], items=[{"quantity":1,"uom":"example","price":1,"productId":"example","idQualifier":"example"}], total=1, controlNumber="example", usage="P")

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.generate",
    "arguments": {
      "type": "850",
      "senderId": "example",
      "receiverId": "example",
      "senderQualifier": "example",
      "receiverQualifier": "example",
      "documentNumber": "example",
      "poNumber": "example",
      "date": "example",
      "parties": [
        {
          "role": "example",
          "name": "example",
          "idQualifier": "example",
          "id": "example"
        }
      ],
      "items": [
        {
          "quantity": 1,
          "uom": "example",
          "price": 1,
          "productId": "example",
          "idQualifier": "example"
        }
      ],
      "total": 1,
      "controlNumber": "example",
      "usage": "P"
    }
  }
}

Response

Field	Type	Description
`ok`	boolean	one of: true
`items`	array
`total`	integer	Total matching rows upstream; null when unknown.
`source`	object
`meta`	object

Example response datajson

{
  "ok": true,
  "items": [
    {
      "type": "example",
      "documentNumber": "example",
      "lineItems": 1
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "edi": "example",
    "segmentCount": 1,
    "controlNumber": "example"
  }
}

FAQ

Do I need an API key to use the generate API?: No. edi.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 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 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.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

/api/directory — full catalog of every endpoint
/openapi.json — OpenAPI 3.1 spec (per-op x-payment-info, x402Payment security)
/.well-known/x402 — machine-readable service descriptor for x402-aware crawlers
/.well-known/mcp/server-card.json — MCP SEP-1649 server card
/llms.txt — plain-text manifest for LLM ingestion

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