Skip to main content
Every Tied resolution uses one or more LLMs to route, reason and respond. LLM cost is never bundled into the resolution price. Every invoice carries exactly two numbers: a flat orchestration fee per resolution, set by the resolution’s class, and the LLM cost at exactly what the provider charged — zero markup, at every tier.

What zero markup means mechanically

No markup coefficient exists at any tier, at any value — including 1.0. There is no field to set, no default to carry, and no floor to enforce. Billing mode is one of exactly two values: itemized_passthrough or byok. The consequence for routing: Tied’s revenue is identical whether a resolution runs on a frontier model or a cheap one, because the orchestration fee is set by the resolution’s class and the token cost is passed through unchanged. Model selection has no effect on what Tied earns. Tied publishes its model recommendations alongside the benchmarks behind them, so which model ran and why is always visible.

Bring your own keys

You may supply your own provider keys — Anthropic, OpenAI, Google, Mistral and others — at any tier, not just Enterprise.
1

You pay the provider directly

On your own provider account, your own enterprise agreement, your own negotiated rates.
2

Tied never touches that money

It does not pass through our billing system, our balance sheet, or our invoice. It was never ours to bill and never ours to waive.
3

Your Tied invoice reduces to one number

The orchestration fee alone.
Bringing your own key is choosing your own model, which is why BYOK is available on every plan while pinning a model from the Tied-hosted menu is an Advanced capability. See Plans.

How tokens are priced on Tied-supplied keys

If you use Tied-supplied keys, we need a per-token price at the moment of each resolution — before the provider’s monthly invoice exists. How model cost is priced at run time and reconciled against the provider invoice monthly. How model cost is priced at run time and reconciled against the provider invoice monthly.
1

An effective-dated price table

Tied maintains its own price table for every model we route to. Each entry records the provider’s published rate and the date range it applies to. Resolutions are priced against the entry in effect at the time they ran — so a mid-month provider price change does not retroactively rewrite your earlier resolutions.
2

Monthly reconciliation against the real invoice

At month end we reconcile that table against the provider’s actual invoice.
3

The difference is allocated back, pro-rata by tokens

Any difference — in either direction — is allocated to customers in proportion to tokens consumed, and appears as an explicit reconciliation line on your invoice.
The passthrough is not a promise about our intentions. It is an arithmetic identity that closes out monthly, in public, on your bill.

What appears on the receipt

Every resolution’s receipt itemizes the LLM cost by model, token count, provider rate and total — separately from the orchestration fee, never blended into it. A resolution that did not bill can still show an LLM cost. The two numbers are independent: the orchestration fee is what Tied charges for resolving something, and it is zero when nothing was resolved. The token cost is what the provider charged for tokens that were genuinely consumed. Zeroing out a real provider charge would make the receipt easier to read and less true.

Model choice by plan

Next

How pricing works

The two-number model and the credit peg.

Resolution pricing

The seven classes and what each costs.