Developer pricing

Usage-based pricing. Free to start.

Pay for what you call — 5,000 calls / month free, then $0.0015 / call. No seats, no per-document fees, no sales call. Bill through us, or install through a marketplace you already use and let it bill you.

Get an API key Read the docs →

Building full SMB EDI workflows (partners, VAN, certification)? See SMB plan pricing — flat monthly tiers separate from this API meter.

Plans

One metered API. Three ways to pay for it.

A call is one parse or one validate request. The same key works across the REST API, the SDK, and the MCP server — usage counts the same wherever it comes from.

Free

$0forever

Build and ship a real integration before you pay a cent.

5,000 calls / month, no credit card
Sandbox + production API keys
MCP server + TypeScript SDK
Signed webhooks (997 / 999 / TA1)
Community + docs support

Get an API key

Pay as you go

$0.0015 / callafter your first 5,000 calls / month

Usage-based and metered. No seats, no per-document traps.

Everything in Free
Metered overage at $0.0015 / call
Usage dashboard + per-key rate limits
Pay through us (Stripe) or your marketplace
Email support

Start free, pay as you grow

Scale

Customcommitted volume

Volume pricing, an SLA, and BAA when you need them.

Discounted committed-volume rates
Uptime SLA + priority support
BAA for PHI workloads
AS2 / SFTP exchange at scale
Marketplace private offers

Talk to us

How billing works

Bill through us, or through a marketplace

The integration surface is identical either way — only the billing relationship changes. Come directly and we bill you on Stripe; install through a marketplace and it bills you and remits to us.

SignalEDI · Stripe

Come directly to us

Sign up, issue a scoped key in the developer console, and add a card. We meter your usage and bill you through Stripe — you hold the relationship with SignalEDI.

Self-serve API key in minutes — no sales call
Start free; a card is only needed past the free tier
Metered usage, transparent per-call pricing
Upgrade to committed volume when you scale

Open the developer console →

Your marketplace → remits to us

Install through a marketplace

Already build on Vercel, GitHub, or AWS? Add SignalEDI the same way you added your last integration. The marketplace bills you on the invoice you already pay and remits to us — one less vendor relationship to set up.

Install/authorize once — provisioning resolves to a scoped account
Billed on your existing marketplace invoice
Same REST API, MCP server, and webhooks as direct
No second contract, no new payment method

See marketplace channels →

MCP server

EDI as tools in any AI client

Give any MCP client the SignalEDI engine as tools — parse, validate, send, and inspect EDI right inside a conversation or agent loop. No EDI logic in your prompt, just a key.

parse_edi — Raw X12/EDIFACT → structured JSON + validation summary.
validate_edi — Validate an interchange against X12 structural rules.
send_outbound_document — Serialize JSON to EDI and send to a partner (webhook-acked).
list_transactions — List recent transactions, scoped to the key.
get_transaction — Fetch one transaction with full lifecycle status.

Works with Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP host. Published as @signaledi/mcp-server.

Create a platform key →SDK examples →

.mcp.json

{
  "mcpServers": {
    "signaledi": {
      "command": "npx",
      "args": ["-y", "@signaledi/mcp-server"],
      "env": { "SIGNALEDI_API_KEY": "sk_live_…" }
    }
  }
}

Where to get it

Get SignalEDI where you already work

Direct today; marketplace channels are rolling out so you can install and pay where your stack already lives.

ChannelTypeBilled byStatus

Direct API + ConsoleIssue a scoped /v1 key and pay us directly. The fastest path.DirectSignalEDI · StripeLive

npm — SDK + MCP server@signaledi/sdk and @signaledi/mcp-server. Bring your own key.DistributionFreeLive

MCP Registry + directoriesDiscoverable in the MCP Registry, Smithery, Glama, mcp.so, PulseMCP.DiscoveryFreeLive

Vercel MarketplaceInstall from Vercel; billed on your Vercel invoice. The Railway model.MarketplaceVercel → remits to usComing

GitHub MarketplaceAction + App. Billed through your GitHub account.MarketplaceGitHub · flat plansComing

RapidAPIRapidAPI meters and bills; no second payment method to set up.MarketplaceRapidAPI · meteredComing

AWS / Azure / GCP MarketplaceProcure through your cloud bill for enterprise sourcing.MarketplaceCloud → remits to usComing

FAQ

Pricing & billing questions

What counts as a call?

A call is one parse or one validate request. Your first 5,000 calls / month are free every month; beyond that you pay $0.0015 / call. Webhooks and acknowledgements are not billed as calls.

Do I need a credit card to start?

No. The Free tier gives you 5,000 calls / month with sandbox and production keys, the MCP server, and the SDK. A card is only required once you exceed the free tier on the direct (Stripe) path.

Who bills me if I install through a marketplace?

The marketplace does. If you provision SignalEDI through Vercel, GitHub, AWS, or another supported marketplace, your usage shows up on the invoice you already pay there, and the marketplace remits to us. The API, MCP server, and webhooks are identical to the direct path.

Is the MCP server free?

The MCP server itself is free and open on npm. It calls the same metered /v1 API under your key, so usage through MCP counts toward your free tier and per-call pricing exactly like a direct API call.

Can I move between direct and marketplace billing later?

Yes. The integration surface never changes — only the billing relationship does. Start direct on our Stripe and move to a marketplace (or the reverse) without rewriting your integration.

Start building

Free to start. Pay as you grow.

Issue a scoped key in the developer console and make your first call in minutes. Add billing only when you pass the free tier.

Get an API key Developer overview →