Pricing a data request

Pricing a data request

marketfeed prices a prospective Databento pull, with its mf-cost command (marketfeed’s manual, “Pricing a pull: mf-cost”). Only marketfeed talks to Databento (the owner’s rule of 20 Nov 2026, GLE-1790), and a free metadata call such as a quote counts (GLE-1791). mf-cost quotes through a marketfeed gateway with the client’s gateway key, so it runs wherever MF_LIVE_SERVERS and MF_GATEWAY_KEY are set (The live source) and needs no Databento key.

# One dataset:
mf-cost --dataset GLBX.MDP3 --symbols ES.FUT,NQ.FUT --schemas definition,statistics

# A universe file, with a machine-readable copy:
mf-cost --universe universe.json --csv invoice.csv

It prints, for each dataset and schema, the billable bytes and Databento’s quote in US dollars, with a total. It takes the universe file algodata cost took: marketfeed keeps the example, scripts/universe.example.json. Its dates differ from algo run’s: --from and --to are UTC, and --to is exclusive, as Databento and marketfeed’s fetchers take them.

algolang’s own algodata cost did this until 20 Nov 2026, with a Databento key of its own. It was removed (GLE-1796): the subcommand now only says so.