Question 1

What does this wallet hold?

Accepted Answer

a whole wallet for a cent, and what the total covers get the wallet detail for <address> with surf on monid and give me the total, the chain split and the top ten positions by usd value. if you pass a chain, use it only to filter the positions: the usd total stays at the ALL-CHAIN figure and does not follow the filter. do not paste the whole response back to me: it runs to hundreds of kilobytes what one cent buys: a thousand token balances each with a USD value, the NFTs, every active chain, the total and an exchange label at confidence 1; the counts differ per wallet, so read them rather than expecting ours the chain filter does not filter the money: asking for one chain filters the tokens and the NFTs correctly while the usd total stays at the all-chain figure. On a second wallet that made the chain-scoped answer 11.3x too high, which is the most expensive mistake available on this endpoint and the NFT list is silently capped at 200: no more-results flag, no total and no paging, and a chain-filtered call returned exactly 200 again sharing only 31 with the unfiltered 200. This page's original wallet only escaped it by holding fewer than the cap the catch: 530,801 bytes, roughly 132,700 tokens; the call is cheap and the answer does not fit in a context window, so summarise it in code before it reaches a model 26 chains, one that matters: 99.999% of the value sits on the first one; active on 26 chains is true and nearly meaningless the dearer twin is not a strict subset: it costs about 2x and returns no token amounts, so it loses on price and on holdings. But it carries transfer recency, a provenance block and a settlement id that the cheaper one has nowhere, so a reader told it is a strict subset deletes fields they cannot get elsewhere

Question 2

What are the odds on this question across venues?

Accepted Answer

subtract the timestamps before you compare the prices get the matched prediction market pairs with surf on monid, passing active_only true so the endpoint does the open-on-both filter server-side rather than you doing it by hand. if you want a particular question rather than a browse, the search endpoint takes a q keyword over the question text and the ticker what arrives: twenty cross-venue pairs, every one at confidence 100 and match type exact, across culture, sports, politics and economics, each carrying both venues' identifiers the flag that is never false: one venue reported its market active on all twenty rows while the other reported sixteen of them finalized, on both runs, so that one flag on its own keeps everything and the venue name changes case: the source field comes back capitalised while every request enum is lowercase, so a naive equality filter matches nothing the volumes are different units: one side reports dollars and the other reports contracts, in the same position of the same object; dividing one by the other means nothing there IS a keyword search, and this page said there was not: the search endpoint declares a q field described as searching the question text or the ticker, and it works: a plain phrase returned five matching markets and the status filter is a parameter, not a chore: an active-only flag is declared and does the job server-side in the same call, returning twenty rows open on both sides; an earlier version of this page told readers to filter it by hand the unit trap is documented, not hidden: the two volume fields are named for their units and the daily endpoint's own summary says so, so this is a field you must read rather than a trap that catches you

Question 3

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

Accepted Answer

deposits, or deposits plus borrowed: ask which before you quote 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 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

Surf

Try it with your agents

How-to guides

Surf

Try it with your agents

How-to guides

Related categories