Who is hiring for the thing I sell?

a posting board changes weekly; a funding round happens twice in a company's life search live job postings for with builtin on monid and give me the employer, location and salary per row, then tell me which employers appear more than once the depth: 127 pages of live postings for one role, across every employer hiring today per row: real employer names and salary bands, one of them $179,000 to $205,000, though on a second run only 17 of 25 rows carried a salary at all and one employer's seven rows were all null why it repeats: this is the signal you can run every Monday and get a different answer the spread: five more providers answer the same question between $0.01 and $0.10

Defillama APIs

Q: What is locked in this protocol, and what does it pay?

deposits, or deposits plus borrowed: ask which before you quote get the tvl for from the free defillama protocol endpoint on monid, passing the slug as a path parameter rather than a query one. then get the same protocol's per-chain breakdown and tell me the split between deposits and borrowed before you quote a single figure: the two sources count different things and the gap is not a fixed percentage the gap is real and its size is not: 68.0% on the first lending protocol and 42.4% on a second; 0.14% on the first staking one and 1.42% on a second. The direction held on all four: lending diverges, staking barely does why: summing the plain per-chain keys reproduces the free number exactly, and adding the borrowed aggregate reproduces the paid one. One counts deposits, the other deposits plus borrowed and some of the gap is just age: the paid source was about 28 hours behind on a second run, so on a protocol where deposits and borrowed barely differ, staleness rather than the definition is what a reader will actually see so there is no fix: borrowed is most of a lending protocol and none of a staking one, so the gap is a property of the protocol and no correction factor exists and one of the two is free: the all-protocols endpoint costs nothing and returns the TVL and the per-chain breakdown for every protocol in one call, so the paid per-protocol metrics call is usually buying a field you can have for nothing do not sum that object: its 51 keys mix chains, suffixed chains and bare aggregates in one namespace; adding them all gives $46.043bn and means nothing

What is locked in this protocol

Say this to your agent

>get the tvl for <protocol> from the free defillama protocol endpoint on monid, passing the slug as a path parameter rather than a query one. then get the same protocol's per-chain breakdown and tell me the split between deposits and borrowed before you quote a single figure: the two sources count different things and the gap is not a fixed percentage

What the agent runsdone

defillama /api/tvl/{protocol}$0.00

defillama /api/v2/metrics/tvl/protocol/{protocol}$0.0006

surf /project/defi/metrics$0.012

What came backone protocol, one control · 2026-09-25

Two sources, two protocols, same dayUS dollars locked

lending · free source$19.21bn

lending · paid source$32.28bn

staking · free source$26.25bn

staking · paid source$26.29bn

the gap is real and its size is not68.0% on the first lending protocol and 42.4% on a second; 0.14% on the first staking one and 1.42% on a second. The direction held on all four: lending diverges, staking barely does

whysumming the plain per-chain keys reproduces the free number exactly, and adding the borrowed aggregate reproduces the paid one. One counts deposits, the other deposits plus borrowed

and some of the gap is just agethe paid source was about 28 hours behind on a second run, so on a protocol where deposits and borrowed barely differ, staleness rather than the definition is what a reader will actually see

so there is no fixborrowed is most of a lending protocol and none of a staking one, so the gap is a property of the protocol and no correction factor exists

and one of the two is freethe all-protocols endpoint costs nothing and returns the TVL and the per-chain breakdown for every protocol in one call, so the paid per-protocol metrics call is usually buying a field you can have for nothing

do not sum that objectits 51 keys mix chains, suffixed chains and bare aggregates in one namespace; adding them all gives $46.043bn and means nothing

$0.0006the number and its parts

What a pool is actually paying

Say this to your agent

>get the pools for <protocol> on <chain> with defillama on monid and give me the current apy next to the 7 day and 30 day averages for each. they are all in the same row, so quote the window i asked for rather than whichever one is highest

What the agent runsdone

defillama /yields/v2/earn/query$0.0006

surf /onchain/yield/ranking$0.012

What came backone protocol, one control · 2026-09-25

One pool, three windows, one responseAPY

30 day average2.864%

7 day average0.587%

right now0.484%

the honest endpointevery pool arrives with its current rate, its seven-day average and its thirty-day average side by side, split into base and reward, so there is no excuse for quoting the wrong window

how far they driftone pool was paying 0.484% against its own 30-day average of 2.864%, a 2.380 point gap in a single row

size is not returnon the first protocol two of the six largest pools paid 0.000%, being collateral assets with nothing in the row saying so. On a second protocol none of its pools did, so check rather than expect it

the range0.0000% to 5.2561% across the 38 pools, and their TVL total is a third figure for the protocol because the query is scoped to one version on one chain

$0.000638 pools, three windows each

A token's price, for nothing

Say this to your agent

>get the current price of <token> with defillama on monid. do not reach for a paid price endpoint first: on our run the free one returned the same number to four decimal places, and it carries a confidence figure the others do not

What the agent runsdone

defillama /coins/prices/current/{coins}$0.00

surf /market/price$0.012

surf /dex/token/price$0.006

surf /search/token$0.006

What came backone protocol, one control · 2026-09-25

The same token, three sourcesUS dollars

free endpoint$152.9038

$0.012 endpoint$152.9038

$0.006 candles$152.7330

identicalthe free call and the paid call returned the same price to four decimal places on both runs, and the whole three-source spread was about a tenth of a percent. It held on a micro-cap priced at a third of a cent, where the paid call bought nothing either

what free addsa confidence of 0.99 on every row, which neither paid endpoint carries

and both id schemesit answered the same query keyed by a chain address and by a registry id in one call, so no translation lookup is needed

the outlier is unfinished, not stalethe candle feed's last bar is stamped at its OPEN and is still forming, so it is a partial bar rather than a lagging one. An earlier version of this page called it an hour behind, which sends a reader to apply a time correction to a number that needs none

$0.00and a confidence with it

A stablecoin's supply and its peg

Say this to your agent

>get <stablecoin> with defillama on monid. the call returns a short stub carrying a download link rather than the body itself, and that link expires in an hour, so fetch it in the same run, write it to a file, and pull the circulating balance and the price out of the file in code. it is tens of megabytes of daily history and it must never reach a model whole

What the agent runsdone

defillama /stablecoins/stablecoin/{asset}$0.00

defillama /stablecoins/stablecoins$0.00

defillama /stablecoins/stablecoinprices$0.00

What came backone protocol, one control · 2026-09-25

Where one stablecoin's supply sitsshare of $183.8bn, of 130 chains

chain 150.42%

chain 239.85%

chain 35.00%

the other 1274.73%

what you wanted$183,768,149,251 circulating, a price of 0.9997963 which is 20 basis points under peg, a fiat-backed mechanism and a named price source

what you got21.4 MB on the first stablecoin and 10.6 MB on a second, tens of thousands of daily history points across dozens of chains either way

and it does not arrive inlinethe run writes a stub of a few hundred bytes carrying a download link that expires in an hour. Neither field this sentence asks for is in that stub, so a reader who stops at the saved output has nothing; an earlier version of this page missed the fetch step entirely

free is not cheapthe call bills $0.0000 and reading the fetched body whole is the most expensive thing in the pipeline; take the two fields in code and drop the history

count the live chainsa quarter of the chains listed reported a zero balance on both stablecoins, and the top two held 90% and 97% of the supply, so the long tail of chains is presentational

$0.0021 MB, and two fields you want

Compare two protocols on one measure

Say this to your agent

>get both protocols from the free all-protocols endpoint on monid in a single call, and say so in the answer. one call for both makes the same-source rule structural rather than something you have to remember, and it costs nothing

What the agent runsdone

defillama /api/tvl/{protocol}$0.00

surf /project/defi/metrics$0.012

defillama /api/v2/metrics/tvl/protocol/{protocol}$0.0006

What came backone protocol, one control · 2026-09-25

the ruleone source for a comparison, named in the answer; the two on this page disagree by 68% on one protocol and 0.14% on another

why a mixed comparison liesreading a lending protocol on the source that counts borrowed and a staking protocol on the one that does not makes the lender look 68% bigger than it is

a third figure exists toosumming a protocol's pools gives yet another number, because that query is scoped to one version on one chain; three figures, three scopes

what it costs to be rightnothing. One free call returns the TVL and the per-chain breakdown for every protocol at once, which answers this whole sentence and removes the chance of mixing sources rather than merely warning against it

$0.00two protocols, one ruler

The empty page that bills

Say this to your agent

>if a pools query for <protocol> comes back empty, do NOT conclude the protocol has no pools, and do not try to settle it with the free TVL endpoint: the two do not share a slug namespace, so a slug the TVL endpoint likes can still be one the pools endpoint has nothing under. query a pool you know exists on that protocol, or try the family's other slugs, before you report an absence

What the agent runsdone

defillama /yields/v2/earn/query$0.0006

defillama /api/tvl/{protocol}$0.00

surf /search/token$0.006

What came backone protocol, one control · 2026-09-25

what it looks likean empty data array and a pagination block reporting a total of zero, HTTP 200, billed in full

what it is indistinguishable froma real protocol that genuinely has no pools on that chain; nothing in the response separates the two

the cheap check does not work, and this page used to recommend itthe two endpoints do not share a slug namespace. On a second protocol family the parent slug returned $1.63bn of TVL from the free endpoint while the pools endpoint returned an empty page for it and billed, which is a false all-clear; and the bare family name was refused outright by the free endpoint while the pools endpoint accepted it and billed, which is the opposite error

so test a guard in both directionsa check that can pass a wrong slug and fail a right one is worse than no check, because it converts a doubt into a wrong answer you now trust

what does workask for a pool you know the protocol has. A positive result proves the slug; nothing else in this pair of endpoints does

why it matters here morein an aisle where most calls are free, the ones that bill are the ones worth getting right first time

$0.0006the cost of a typo