Developer pricing

Developer API 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 →

SignalEDI · Stripe for Vercel Connectable

Install through a marketplace

Already build on Vercel or GitHub? Add SignalEDI through the supported integration flow. Vercel Connectable installs use SignalEDI direct billing through Stripe; the current GitHub App is free. Native marketplace billing is not enabled.

Install/authorize once — provisioning resolves to a scoped account
Vercel Connectable usage is not added to your Vercel invoice
Same REST API, MCP server, and webhooks as direct
Channel-specific billing is shown before activation

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. Run without a key in demo mode (parse/validate/generate only), then add a platform key for send and partner flows.

parse_edi — Raw X12/EDIFACT → structured JSON + validation summary.
validate_edi — Validate an interchange against X12 structural rules.
generate_test_document — Synthetic 850/810/856/837 samples (demo mode).
explain_edi_error — Local dictionary lookup for ack/validation errors.
lookup_x12 — Search segment and acknowledgement reference.
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.
quickbooks_status — QBO connection status for your workspace (no tokens returned).
quickbooks_sync_to_qbo — Push EDI transactions into QuickBooks (810→Invoice, 850→Bill).
quickbooks_export_to_edi — Pull QBO entities and emit outbound EDI to a partner.
quickbooks_list_entities — List QBO Invoice, PO, Customer, Vendor, or Item rows.
quickbooks_disconnect — Revoke QBO OAuth and remove the workspace connection.
list_partner_kits — List packaged API kits (retail, healthcare, quickstart).
get_partner_kit — Fetch one kit by id (endpoints, webhooks, sample payloads).
validate_x12_structure — Alias for validate_edi — spec-facing discovery name.
parse_segments — Alias for parse_edi — spec-facing discovery name.
lookup_element_definition — Alias for lookup_x12 — search by element or segment.

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

Create a platform key →SDK examples →

Install in CursorOpen Cursor installer

Claude Code CLIclaude mcp add signaledi -- npx -y @signaledi/mcp-server

Config JSON

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

.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 v0.3.1 on npm — install with npx or add to package.json.DistributionFreeLive

MCP Registry + directoriesListed on the official MCP Registry (io.github.SignalEDI/mcp-server). Smithery, Glama, mcp.so, PulseMCP crawl from there.DiscoveryFreeLive

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

GitHub MarketplaceAction live (signaledi-convert-edi-to-json). App listing submitted — pending GitHub review at github.com/marketplace/signaledi.MarketplaceGitHub · flat plansBeta

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 source. Once published on npm it runs via npx with no install fee; 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 →