Why this market won't quote you a price

A vendor's pricing page opens, lists everything the product does, names the customers it is built for, and gives you a form. That is not an oversight: the fee has not been decided yet, because it depends on things about you that the page cannot know, and because the method that sets it works only while the numbers stay apart.

This is the normal condition at the institutional end of crypto data and execution software, and it is not specific to crypto. It has been described, measured and regulated in the wholesale data market next door, which is the useful thing about it: the mechanism is documented, the costs it pushes onto a buyer are documented, and the questions that get a usable answer out of it are known.

How it works

The method has a name in the regulatory literature — value pricing — and the Financial Conduct Authority's wholesale data market study, published on 29 February 2024, sets it out in one paragraph. Data suppliers "vary the price they charge to different customers based on their expected value of, or willingness to pay for, data, independently of the cost of supplying it to the customer" (paragraph 3.13). The study found this across all three markets it examined: credit ratings data, benchmarks and market data vendors.

Price discrimination needs two things to work. The first is something observable to discriminate on. The FCA lists industry, size, number of users, locations, assets under management, then the product dimensions — content, coverage, frequency, delivery method — and then the use-case licences: non-display, derived data, distribution and reporting, and licences that let the data become an input to a product of your own (paragraph 3.15).

Crypto vendors publish exactly that list, minus the numbers. The pricing page of Kaiko, read on 21 September 2026, says pricing depends on the number of assets and instruments, the data type, the granularity, historical versus live access and usage, and then offers two buttons: request a quote, request a trial. That is a published price-driver list with the prices removed, which is a more precise description of what a "contact us" page is than any adjective.

The second requirement is that the resulting numbers stay apart. The FCA found price lists "used internally but not available to customers", with the final licence fee "negotiated on an individual basis" and ad hoc discounts applied, and confidentiality clauses in the terms that stop customers comparing what they paid (paragraph 5.87). Its transaction analysis of credit-ratings data feeds found that several suppliers could not produce a price list at all — pricing came out of an internal model with "significant discretion to adjust on a per customer basis", making it "likely that data users with similar characteristics and usage" pay significantly different amounts (paragraph 4.91).

Two further reasons apply specifically here, and both are legitimate.

The vendor is reselling somebody else's permissions. An exchange publishes its prices for nothing and reserves redistribution by contract, licensing it separately and without a public figure — the subject of what exchange API terms actually let you do. A vendor that has bought those rights venue by venue is passing on a cost structure that is itself unpublished, and priced per venue, per use case and per term. A single public number would have to be the worst case across all of it.

The contract is negotiated before the price is. Wyden ships either as secure SaaS or as a dedicated managed service on a single-tenant instance, and which one you get depends on your own ICT and hosting policy. Talos says its affiliates offer software-as-a-service products, so the arrangement is a licence rather than a per-trade fee, and that is the whole of what is public about its commercial shape. In both cases the deliverable is different for each buyer, which makes a rate card genuinely hard to write — and also means no buyer can check it.

Where the silence falls

Counted across the 87 cards in this catalogue on 21 September 2026: 37 of them have at least one tier with no published price — 42 unpriced tiers in total, and on 16 of those the tier is simply called Enterprise.

The distribution is the finding. The share rises with how close the product sits to institutional data:

Software you install and run yourself names its price essentially always. Data that somebody else licensed from somebody else mostly does not.

Two harder cases sit inside that count.

Eight cards publish no figure anywhere at all: Allium, ChartIQ, CoinDesk Data, CoinRoutes, Elwood, Kaiko, Talos and Wyden. None of the eight has a free tier, and not one of them publishes how long a trial lasts. There is no way in that does not begin with a conversation.

Seven more publish a zero and nothing else — Coin Metrics, CoinAnk, Coinbase Exchange API, Footprint Analytics, growthepie, SignalPlus and TradingView Advanced Charts. Free, then quoted, with no step in between. For fifteen cards in this catalogue, then, no paid price can be learned from the web at all.

Not every blank is a sales desk, and a filter cannot tell the difference. DEXTools has an unpriced top tier because the way in is holding 100,000 of the vendor's own token rather than paying a subscription. The Coinbase Exchange API entry is not a product tier at all but the authorised-redistribution right, which has no published figure because it is granted rather than sold from a page.

What it costs

Where prices are published, this is roughly where they stop. Twenty-one of the 37 cards with a quoted tier also publish a monthly figure below it; the median of their highest published monthly tier is 499 USD a month, and the range runs from 19.90 to 999. The pattern repeats outside the catalogue: Etherscan's API plans page, read on 21 September 2026, publishes six tiers from free to 899 USD a month and then hands the top two — Metadata Enterprise and Dedicated — to a contact form. The wall is not at the door. It is at the point where volume, redistribution or a bespoke deployment starts.

What you pay in time. The published path is a card payment and a key; Amberdata sells one exchange and one market from a self-serve store at 600 USD a month or 5,000 USD a year, which is the cheapest self-serve entry into licensed data in this catalogue, and even there keys are provisioned in 24 to 48 business hours rather than instantly. The quoted path is a demo request, a scoping call, a legal review and a signature. For a regulated buyer in the EU it is longer still: a platform of the kind Wyden sells is an ICT third party under DORA, so the contract goes through outsourcing and concentration-risk review before anyone discusses money.

What you pay in uncertainty. You cannot build a budget line, you cannot compare two vendors on anything but features, and — because of the confidentiality clauses the FCA describes — you cannot find out whether the desk down the corridor was quoted the same number for the same thing. The FCA's own conclusion was that users with similar characteristics likely pay significantly different amounts (paragraph 4.91).

What an unpriced arrangement costs when it changes. CoinDesk Data announced on 17 April 2026 that free API access would end on 21 May 2026 and that accounts without a subscription would stop returning data. An arrangement with no published price also has no published notice period, and the thing you built on it is the thing that finds out.

What is not free either way. Talos will provide a sandbox "depending on the integration", with no stated duration, contents or cost, and its footer is explicit that clients negotiate liquidity arrangements bilaterally — the subscription buys the plumbing, not the exchange accounts, OTC credit lines or custody relationships. Costs excluded from an unpublished price are just as invisible as the price.

Why the rules that force publication do not reach here

In the regulated market next door, the answer to this problem is statutory, and it is instructive to see what it actually requires.

MiFIR obliges market data providers to make pre- and post-trade data available on a reasonable commercial basis. ESMA's final report of 16 December 2024 sent the European Commission the technical standard that puts flesh on it. In the draft annexed to that report, market data providers must publish their market data policy free of charge, in one place on their website, and keep the previous five years of it online (article 19); publish the required fee information using a template annexed to the regulation, at a consistent granularity "to make the disclosure meaningful for clients to compare between offers" (article 21); and publish both a summary of how the level of fees was set and a detailed explanation of the cost accounting methodology behind it, including whether a margin is included and how it is kept reasonable (article 22). Fees must be expressed in a single, unique unit of count, so that two units cannot be combined to count the same access twice (article 20).

That standard was adopted as Commission Delegated Regulation (EU) 2025/1156. ESMA recorded on 23 February 2026 that it entered into force on 23 November 2025, that providers authorised before that date have until 22 August 2026 to comply, and that ESMA had withdrawn its own market data guidelines because their content now sits inside the regulation.

None of it binds the vendors on this site. Those obligations attach to trading venues, approved publication arrangements, consolidated tape providers and systematic internalisers in financial instruments. The FCA was direct about the same boundary in its own market: market data vendor activity "is generally not within scope of the FCA's perimeter as set by Parliament" unless the firm is also running an APA, an ARM or a consolidated tape (paragraph 6.62). A crypto analytics platform or an order and execution management system is none of those things. Whether the crypto-specific regimes impose anything comparable is outside what this page checked — read the comparison as what a published duty looks like when one exists, not as a claim that one is coming.

The practical use of it is the shape. Every item in that standard is a question a buyer can ask without it, and asking is free.

What you can do about it

Turn the vendor's own price drivers into the quote request. If a vendor publishes what its pricing depends on, answer it line by line before the first call: instruments and venues, history depth, update frequency, delivery method, seats, and whether anything derived from the data leaves your organisation. A scoped request gets a number in one round; an unscoped one gets a discovery call.

Ask which price you are being quoted: access, or the right to redistribute. They are different products from the same vendor and the second is usually a different tier. Decide this before the architecture, not after — the rule and the reason are in what exchange API terms actually let you do.

Ask for the venue and instrument list as a list. "65+ venues" and "85+ chains" are marketing counts. The list is the artefact, it exists internally, and the request is routine. Do the same with history: a start date per venue, not a phrase about deep history.

Get the documentation during evaluation, under NDA if it has to be. On several of the cards above the docs are an onboarding deliverable — a documentation host that answers with a login, or a knowledge base handed over after signature. Evaluating a data product without reading its schema, its rate limits and its error semantics is evaluating a brochure. If the answer is no, that is itself a finding.

Ask for the trial in writing, with a duration. None of the eight fully unpriced products here publishes how long a trial lasts or what it contains. A sandbox "depending on the integration" is not a plan. Fix the length, the data scope and whether the key survives into production.

Ask the four contract questions before the price question. Minimum term. What renewal does to the fee, and whether any uplift is capped. What it takes to leave, and on what notice. What happens to data you have already stored when the contract ends — deletion obligations are common in this market and they can reach into your own storage.

Ask whether you may say what you paid. If the terms carry a confidentiality clause, you have lost the ability to benchmark this renewal against anything. Asking for a carve-out for your own advisers is a normal request, and the answer tells you how the vendor prices.

Check the self-serve neighbour before you enter a procurement cycle. For a narrow slice — one venue, one market, one use case — a published tier may cover it outright. Where these cards publish a monthly price at all, the top one is a median of 499 USD a month, and licensed self-serve data starts at 600 USD a month per exchange and market. If your need fits under that ceiling, the quoted path costs you weeks and buys nothing.

Know the threshold below which none of this applies. One person, internal use, nothing redistributed and nothing published: the free and published tiers cover that case across almost the whole catalogue, and every product in backtesting libraries publishes its price. The wall is a function of scale and of redistribution, not of seriousness.

Budget a procurement cycle, not an afternoon. If the product you need is quoted rather than priced, the calendar cost is the one to plan around: a demo, a scoping call, a security or outsourcing review if you are regulated, then legal. Start it before the quarter in which you need the data, and carry a published comparable into the budget paper as an anchor, clearly labelled as an anchor rather than a quote.