Haz que tu router sea listado y medido
TKX clasifica el mercado de routers por medición, no por afirmaciones. Implementa el estándar abierto — la mayoría está a 30 minutos — y nuestro colector horario te verifica automáticamente. Tú expones, nosotros medimos.
The four levels
GET /v1/models. TKX measures your model coverage every hour. Evidence chip: Coverage measured.L2 pricing formats (any of these four)
Prices must be machine-readable per model. We already auto-detect all four dialects in production:
{"id":"org/model","pricing":{"prompt":"0.0000025","completion":"0.00001"}} — USD per token (strings).{"id":"org/model","input_price":2.5e-6,"output_price":1e-5} — USD per token (numbers). Used by Requesty.{"id":"org/model","input_token_price_per_m":25000,"output_token_price_per_m":100000} — 1/10000 USD per 1M tokens. Used by Novita.{"model_name":"model","quota_type":0,"model_ratio":0.125,"completion_ratio":8} — ratio × $2/1M input, × completion_ratio for output; your existing /api/pricing works as-is. quota_type 1 (per-call) rows are skipped.Recommended for new implementations: dialect A (OpenRouter-compatible). Running one-api/new-api? Your public /api/pricing is already dialect D — just submit it. Sanity valves apply: fewer than 3 priced models, prices outside $0.0005–$2000 /1M, or a median markup outside −80%…+300% vs official list will reject the source — garbage can't buy a ranking.
Why implement it
<a href="https://tkx.org/a/your-slug/">Measured on TKX</a> to your site. Your TKX profile page links back to you.Node protocol — for institutions publishing valuations
Some things cannot be measured. Private-company valuations and pre-IPO secondary prices are not public by definition — they move between funds, advisers and counsel. TKX will not pretend to measure them.
So this layer works differently from the rest of the site. Instead of us measuring you, you publish under your own name and TKX guarantees what happens to that name. Those guarantees are the protocol. Every one of them is enforced by code and re-checked automatically on every publish — you can run the checker yourself against our live API.
What TKX guarantees your data
| Guarantee | How it is enforced |
|---|---|
| Your byline never detaches — every figure carries the node that published it, on the page and in the API | Column is NOT NULL; an observation without attribution cannot physically be written |
| You are never averaged away — multiple nodes produce a published range, never a single blended "consensus" number | Bands carry lo/mid/hi; a single-source figure is labelled as such and shows no fake range |
| Your data is never mixed with a different basis — primary rounds, secondary trades and fund marks stay in separate bands | Band key is (company, method); the checker fails if one key ever produces two bands |
Publishing more does not buy you more weight — n counts distinct nodes, not observations, and only your latest figure per basis counts | n === new Set(nodes).size, asserted every run |
| We never fold your figures into a TKX index | Node-tier evidence is excluded from TTPI / TTV / SPI by construction, same as self-reported volume |
| Secondary interest carries no price, size or discount — your client relationship stays yours | Those columns do not exist in the schema; a whitelist strips them on write and records what was dropped |
| We never claim to have verified you — we publish the credential URL you give us and label it unverified | verified is hard-coded false |
What TKX tracks about you
One number, computed after the fact and never by hand: calibration — the median absolute deviation between the valuations you published and the funding rounds those companies subsequently announced. Only observations dated before the round count; marking a company after its round is already public earns nothing.
Under three usable samples it reads collecting. We would rather show nothing than a precise-looking score built on two data points — the same rule that keeps our hardware index empty until it has real trades behind it.
This is deliberately a two-sided deal. You take reputational risk by signing your figures; in exchange you get a public, comparable track record that nobody can assemble on their own, because only the aggregator sees every node's calls next to the outcomes.
Verify all of it yourself
None of the above is a promise in a deck. The checker is in our repo and runs against the live public API:
node scripts/verify-valuations.mjs https://tkx.orgTen assertions, exit code 1 if any fails. If TKX ever breaks one of these guarantees, that command says so before we do.
Becoming a node
- Create an account at /account/.
POST /market/node-applywith{slug, name, credentialUrl}— the credential URL is any page that evidences who you are.- We review by hand. Accredited nodes publish to the board; listed nodes are recorded but held out of it.
- Publish with
POST /market/valuation{co, method, asof, valuationUsd}, orPOST /market/secondary-intent{co, side, note}. Thenodefield is taken from your account, never from the request body — otherwise a byline would mean nothing.
Submit
Email echo@minax.io with your router name + base URL. If your /v1/models is already public, say so — verification is automatic within the hour. Machine contract: openapi.json.