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. Billing made explicit.

A call is one parse or one validate request. Hosted operations use the same meter through REST, the SDK, or a released authenticated MCP profile; local MCP guidance is not a billable API call. Public MCP v0.4 remains limited to synthetic evaluation.

Free

$0forever

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

5,000 calls / month, no credit card
Platform API key + public playground
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
SignalEDI bills metered usage through Stripe
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. Vercel Connectable installs use that same Stripe-direct path until Native marketplace billing is separately approved and enabled.

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 hosted REST API and webhooks as direct
MCP availability and profiles are versioned separately
Channel-specific billing is shown before activation

See marketplace channels →

MCP server

Agent-facing control for EDI integrations

SignalEDI MCP is the agent-facing integration control plane over the hosted REST data plane. Current public installs remain pinned to v0.4.0 and must use synthetic data only; its published Unix executable does not launch through npx. Hardened v0.5.0 fixes that launcher and adds default keyless docs, an isolated-sandbox profile, and a fail-closed production profile with allowlisted reads and guarded outbound/QuickBooks Online export operations. It remains pending npm and MCP Registry release proof.

The 18 tools below describe public v0.4 discovery, not the v0.5 production surface. Version 0.5 filters tools by profile: production exposes 15 local-guidance, kit, transaction/QuickBooks Online status read, outbound-send, and QuickBooks Online export tools; parse/validate, QuickBooks Online entity browsing, sync, and disconnect remain hidden.

parse_edi — Raw X12 → structured JSON + validation summary.
validate_edi — Validate an interchange against X12 structural rules.
generate_test_document — Generate local synthetic 850/810/856/837 samples without credentials.
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 request an outbound partner send.
list_transactions — List recent transactions, scoped to the key.
get_transaction — Fetch one transaction with full lifecycle status.
quickbooks_status — QuickBooks Online 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 QuickBooks Online entities and emit outbound EDI to a partner.
quickbooks_list_entities — List QuickBooks Online Invoice, PO, Customer, Vendor, or Item rows.
quickbooks_disconnect — Revoke QuickBooks Online OAuth and remove the workspace connection.
list_partner_kits — List generic API-kit catalog entries; these are not partner implementation guides.
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.

Documented configuration examples: Claude Code, Cursor, VS Code. Published as @signaledi/mcp-server.

Create a platform key →SDK examples →

Known v0.4 limitation: its published Unix executable does not launch through npx. These pinned methods are for synthetic evaluation on a verified Windows host; wait for the verified v0.5 release before macOS or Linux use.

Cursor config (Windows)Open Cursor configuration

Claude Code CLI (Windows)claude mcp add signaledi -- cmd /c npx -y @signaledi/mcp-server@0.4.0

Config JSON

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

.mcp.json

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

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 v0.1.0 and @signaledi/mcp-server v0.4.0 are live on npm; MCP v0.5.0 remains pending release proof.DistributionFreeLive

MCP Registry — officialv0.4.0 is the latest verified official MCP Registry listing (io.github.SignalEDI/mcp-server).DiscoveryFreeLive

Secondary MCP directoriesSmithery, Glama, mcp.so, and PulseMCP remain unverified until their listing is observed and any required submission or claim is completed.DiscoveryFreeComing

Vercel MarketplaceConnectable install from Vercel; usage is billed directly by SignalEDI through Stripe. Native Vercel billing remains deferred.MarketplaceSignalEDI · StripeComing

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, a platform API key, the public playground, the MCP package for synthetic evaluation, 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?

Billing depends on the channel. Vercel Connectable installs are billed directly by SignalEDI through Stripe, not on your Vercel invoice. Native marketplace billing remains deferred until a provider program is explicitly enabled. MCP availability and profile restrictions are versioned separately from hosted REST API and webhook billing.

Is the MCP server free?

The MCP package is free and open source. Public v0.4.0 is available through npm for synthetic evaluation only. After release verification, hardened v0.5.0 defaults to keyless docs and adds explicit sandbox and production profiles. Production requires a production-authorized key, the exact canonical base URL, and an independent opt-in; its tool surface remains allowlisted.

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 →