SERV Hackathon 02 · Kite track Record signed Base mainnet · USDC GitHub

What a spending limit costs, before you sign it.

A per-call cap and a total budget are easy to set and hard to reason about. The recorded run shows why: a $0.0025 budget bought $0.002 of evidence and left the answer $0.051 short. This page prices that trade for your facts and your caps, with the same solver. Your own facts are priced over the live Kite catalog, read today over plain HTTPS with no key. The recorded run is priced over the catalog of the day it ran, because that is the catalog its prices belong to. No account, no session, nothing moves.

One per line. Leave it empty to price the recorded run.

Automatic prices your facts over today's catalog and the recorded run over the catalog it ran on.

The answer

Working out the price…

How the number is worked out

The solver is exact, not clever. It enumerates the subsets of your facts, costs the cheapest catalog endpoint that covers each one, takes the basket that fits inside your caps, and reports what is left over. There is no model in the loop and no cut-off, so the same inputs always give the same answer.

  • A cover is demonstrated or declared, and the page says which. A demonstrated cover is an endpoint the record already shows being chosen for that fact, so its price is the merchant's quoted price and a paid attempt carries its transaction. A declared cover is an endpoint whose own catalog text claims the fact.
  • A claim has to be complete. Every meaningful word of your fact has to appear in the endpoint's own text. Strictness costs recall and buys the one thing worth buying here: a cover is never claimed without something behind it.
  • A fact nobody sells is left unpriced. If no merchant in the catalog claims it, the answer names it and leaves it out of the total rather than putting a number in the headline that nothing backs.
  • What the caps forbade is priced once. If one endpoint would have covered two facts, it is counted once, because that is what it would have cost.

The catalog is the live Kite service catalog, filtered to Base mainnet USDC. Your facts are priced over it as it stands today, read over plain HTTPS with no key and no account. The recorded run is priced over the catalog of the day it ran, which is the catalog its prices belong to, and that answer is the number the run measured. Prices belong to the merchants. The same answer is available as /api/limit-cost and as the price_my_limit tool in the @oxunify/capsule-mcp package.