New 6 companies · First observed June 2026 · Updated June 2026

BYO-API keys zero out the model-cost meter

Quick answer

A cohort of agentic and workflow platforms now runs two meters: an orchestration credit they keep, and a passthrough model/data cost they mark up. The tell is that Bring-Your-Own-Key zeroes or halves only the passthrough meter — six corpus vendors expose this lever, while first-party APIs (OpenAI) have none and some seat+credit tools (Cursor) are pulling it back.

6 vendors let buyers zero or halve the model meter via BYOK

What's happening — and why

What's happening: platforms that resell model inference are increasingly splitting the bill into two separate meters. One meter charges for their own orchestration — Clay's Actions, Relevance AI's Platform Credits, Gumloop's workflow nodes — and a second meter charges for the model and data they pass through (Clay's Data Credits, Relevance's Vendor Credits). The diagnostic is what happens when you bring your own LLM API key: BYOK zeroes or halves only the passthrough meter, never the orchestration one. Clay's BYOK eliminates Data Credit cost while still burning Actions; Relevance's BYOK zeroes Vendor Credits; Gumloop's BYOK cuts agent AI-model credits by exactly 50% (its native nodes already cost 0 credits). Vectara and Byword extend the same logic to bundled models and writing.

Why: the split makes the vendor's real value metric legible. By offering a key that zeros the model meter, the platform concedes it is not the cost center on inference — it is charging for the plumbing, not the tokens. The lever isn't new (Byword sold an 'Unlimited' plan on the customer's own GPT-4 keys at $2,499/mo back in December 2023); what changed is that mid-market tools now expose it openly instead of pricing it as a five-figure enterprise escape hatch.

How it works

your usage orchestration Actions / nodes passthrough model / data always billed BYOK zero / -50% vendor bill orchestration only model provider you pay wholesale
Two meters: BYOK zeroes (or halves) the model passthrough while orchestration credits keep billing — you pay the model provider directly.

Evidence over time

6 supporting · 2 counter — hover or tap a point for detail, click to jump to the row.

supports ↑ challenges ↓ 2026
supporting evidence counterexample

Evidence

Company Date What happened
Clay Jun 2026 Two-meter model (Actions + Data Credits) where bringing your own API keys 'eliminates Data Credit cost while still consuming Actions' — BYOK zeros the data/AI passthrough meter but not the orchestration meter.
Relevance AI Jun 2026 Bills Platform Credits + Vendor Credits (raw model cost passed through at wholesale); bringing your own LLM keys on any paid plan 'zeroes this out' — buyers can opt out of one of the two metered dimensions entirely.
Gumloop Jun 2026 Bringing your own API key cuts agent AI-model credit costs by 50%; native workflow nodes (logic, loops, Sheets, Slack) already cost 0 credits — BYOK halves the model-driven portion of the bill.
Byword Jun 2026 Credit-priced rebuild offers a BYO-API path (Claude + Gemini) on an Unlimited plan; the BYO-key idea is long-standing here — a Dec-2023 archive already sold an 'Unlimited' plan running on the customer's own GPT-4 keys at $2,499/mo.
Vectara Jun 2026 Every tier bundles Vectara's own retrieval + generative LLMs but offers Bring Your Own Model (ChatGPT, Claude, Gemini) — letting enterprises substitute their own model contract for the bundled one.
Lemlist Jun 2026 Monetizes the data you pull through credits rather than the bundled 650M+ database; BYO-data/key economics let buyers collapse the 'data tool + sender' stack and avoid double-paying for model/data passthrough.

Counterexamples

  • OpenAI · May 2026 — First-party model API — there is no 'bring your own key' lever; you pay per token directly, with no orchestration/passthrough split to opt out of.
  • Cursor (Anysphere) · Feb 2026 — Coding tool restricts/deprecated raw BYOK on its managed plans in favor of bundled credits — the trend toward letting buyers zero the model meter is not universal; some seat+credit tools pull the lever back.

Trivia

  • Clay's BYOK (2026-06-02) zeroes the Data Credits meter but still burns Actions — the single sharpest proof in the corpus that these vendors charge for orchestration, not inference: a buyer who supplies their own model key pays Clay nothing for the AI/data and everything for the plumbing, exactly inverting the assumption that the model is the cost center.

  • Gumloop (2026-06-02) puts a precise number on the lever almost no other vendor discloses: bringing your own API key cuts agent AI-model credits by exactly 50%, and its native workflow nodes (logic, loops, Sheets, Slack) already cost 0 credits — so the credit meter only ever measured the model passthrough, which BYOK halves.

  • Byword shows the lever is six years old, not a 2026 invention: a December-2023 archive already sold an "Unlimited" plan that ran on the customer's own GPT-4 keys at $2,499/mo — meaning BYO-key economics predate the agentic-platform wave that made them mainstream, and the only thing that changed is that mid-market tools (Clay, Relevance, Gumloop) now expose it instead of pricing it as a five-figure enterprise escape hatch.

See all pricing trivia

For buyers

If a platform exposes a BYOK lever, price the workload both ways. Heavy-inference jobs usually win by bringing your own key and paying the model provider at wholesale — you keep only the orchestration meter (Gumloop cuts model credits 50%; Clay and Relevance zero theirs entirely). The trap is platforms that mark up passthrough with no BYOK escape hatch; there the 'credit' hides a model markup you can't opt out of. Ask explicitly whether BYOK exists and which meter it touches before you size a plan.

For vendors

Running this play needs a clean two-meter architecture — an orchestration credit you keep, plus a passthrough meter buyers can route around with their own API key. Be explicit about which meter BYOK affects (Clay: zeros Data Credits, keeps Actions; Gumloop: halves model credits, native nodes already free) so the value story stays legible. The strategic risk is the Cursor counter-move: if your differentiation is bundled-credit margin on inference, exposing BYOK concedes you aren't the cost center and invites buyers to unbundle — weigh transparency against the markup you're protecting.

Outlook — what to watch

Expect more mid-market agentic and workflow tools to expose BYOK as a transparency and margin signal, normalizing the two-meter split. The status flips from new to holds if more corpus vendors ship an explicit passthrough-zeroing key, or to weakens if seat+credit tools follow Cursor and pull raw BYOK back to defend bundled-credit revenue — betting buyers prefer one bill over a cheaper assembled one. Watch whether any vendor publishes its dollar-to-credit conversion alongside the BYOK option, which would make the orchestration markup fully legible.

Bottom line

Six corpus vendors (Clay, Relevance AI, Gumloop, Byword, Vectara, Lemlist) split the bill into orchestration vs passthrough meters and let buyers zero or halve the model passthrough with their own API key. It's a transparency and margin signal — the platform admits it charges for plumbing, not tokens — but it isn't universal: first-party APIs have no such lever, and some seat+credit tools are pulling it back.

FAQ

What does 'bring your own key' (BYOK) do to my bill?

On platforms that run two meters, BYOK zeroes or halves the model/data passthrough meter while leaving the orchestration meter untouched. Clay's BYOK eliminates Data Credit cost but still burns Actions; Relevance AI's BYOK zeroes Vendor Credits; Gumloop's BYOK cuts agent AI-model credits by exactly 50%.

Why would a platform let me zero out its model cost?

Because the model was never their cost center. Offering a key that zeros the passthrough meter makes their real value metric explicit — they charge for orchestration (the plumbing), not the inference. It's a transparency and margin signal: you pay them for the workflow and pay the model provider directly at wholesale.

Do all AI platforms offer BYOK?

No. First-party model APIs like OpenAI have no BYOK lever by definition — you pay per token directly with no passthrough split to opt out of. And the direction is contested: some seat+credit tools, like Cursor, have restricted or deprecated raw BYOK to defend bundled-credit revenue.

Is BYOK pricing a new 2026 invention?

No — it's at least six years old. Byword's December-2023 archive already sold an 'Unlimited' plan running on the customer's own GPT-4 keys at $2,499/mo. What changed in 2026 is that mid-market tools (Clay, Relevance, Gumloop) now expose the lever openly instead of pricing it as a five-figure enterprise escape hatch.

All trends