Squidlor

Get the per-source audit trail for a pair: every recorded round with each provider's answer, deviation from the median in basis points, staleness, read errors, and anomaly flags with reasons. Call this to investigate whether a source misbehaved, when a deviation happened, or any "did the oracle lie" question. Set flaggedOnly to see only anomalous rounds.

get_audit_trail

Get measured reliability scorecards for every oracle source on a chain over a window: how often each was fresh vs stale, its error rate, how far it sat from the round median in basis points (median/p95/max), its worst single deviation with the timestamp, and how often it was the furthest source from the median. Call this for "which oracle is most reliable", "is Pyth actually working", "which sources should I require in my consensus floor", or any question comparing providers over time. Pass a provider name (e.g. "pyth", "chainlink") to get that one rolled up plus a per-pair breakdown. Use get_audit_trail instead for the raw round-by-round record of a single pair. THREE THINGS YOU MUST CARRY INTO YOUR ANSWER: (1) deviation is measured against the round median, not truth — with only two healthy sources the median is their midpoint, so a big deviation means they disagreed, NOT which was wrong; (2) never compare outlierRate between kind="dex" and kind="oracle" sources, because a DEX reports one venue's marginal spot price and sits away from the median by design; (3) kind="unresolved" rows are our own failed name() reads, not providers — do not attribute their staleness to anyone. Report these as observed behaviour over a window, never as a rating or a recommendation.

get_provider_scorecard

Get what a feed read at a specific past moment — the aggregate median plus every source's answer at that instant. Call this for "what was NVDA at Friday's close", "what did the oracle say when my position was liquidated", or any settlement, dispute or backtest question about one point in time. Use get_price_history for a series and this for a single instant. CRITICAL: recording is sampled (roughly every 60 seconds), so an exact-timestamp observation does not exist. This returns the NEAREST recorded observation on either side and reports offsetSeconds — ALWAYS state the observed timestamp and that offset in your answer rather than presenting the number as the price at the requested instant. If outsideTolerance is true, say plainly that no observation exists near the requested time and do not let the value be used to settle anything.

get_price_at

Get the off-chain REALTIME price of one or more symbols: a 1-second median across exchanges, and the freshest number Squidlor has. Use this when the user wants the live price right now, or asks why the on-chain number differs from an exchange. The on-chain aggregate (get_price) only moves on a 0.5% deviation or the hourly heartbeat, so between pushes these two legitimately disagree. Quote this as the live market price and get_price as the value contracts read.

get_realtime_prices

Fetch a smart-contract audit report that was already generated, by its report id. This does NOT run a new audit: without an id, say so rather than implying a contract was scanned.

get_audit_report

Informational contract-risk report for an ERC-20 token: ownership, mint authority, blacklist, transfer tax and holder concentration, summarised as a risk verdict plus a score. Call this for "is this token safe", "rugcheck 0x...", "honeypot check", or when the user is weighing a token. It describes the contract; it is not investment advice and does not say whether to buy, hold or sell, so present it as a risk summary and leave the decision to the user. The result carries the time the scan was taken: say how old it is rather than implying it was checked just now. IMPORTANT: this reads STORED scans and cannot create one. Most tokens have none, and the result then says `scanned: false, verdict: "unscanned"`. That is neither a clean bill of health nor a failed check - nobody has looked - so say exactly that and do NOT suggest retrying, which cannot help.

get_token_risk_report

Token balances a wallet holds, per chain, across Ethereum (1), BSC (56), Polygon (137), Arbitrum (42161), Optimism (10) and zkSync (324). THESE CHAINS ARE SUPPORTED HERE regardless of which chains carry Squidlor price feeds: never refuse a wallet question because the oracle does not publish on that chain. Arc and Solana are NOT indexed, so say that rather than reporting nothing. Call this for "what is in my wallet", "my balances", "my portfolio", "how much do I hold", or when given a bare 0x address and asked what is in it. Omit `wallet` to use the caller's linked address. CRITICAL, read the result before describing it: `unreadableChains` lists chains whose read FAILED, and a balance there is invisible, not zero. Only say a wallet is empty when `confirmedEmpty` is true. If `unreadableChains` is non-empty you MUST name those chains and say the picture is incomplete - a user who holds tokens on a chain that errored will otherwise be told they hold nothing. Do not invent a cause for the failure (no "indexer sync window", no "fresh inflows"): the reason given in the result is all that is known. There is no USD total on purpose, because one computed over unread chains would be wrong.

get_wallet_overview

Reputation and activity profile for a wallet: how old it is, how active, how it holds. Call this for "wallet card", "onchain profile", "wallet reputation", "diamond hands check", or when asked to characterise an address rather than list what is in it.

get_wallet_card

List open Squidlor bounties: paid, scoped pieces of work a builder or agent can claim. Use this to answer "what should I build" or "how do I earn on Squidlor" with real, currently-funded options rather than generic advice.

list_bounties

List event-outcome oracle results (YES/NO/INVALID questions resolved via UMA, Reality.eth, and operator sources) on a chain. Call this when the user asks about event resolution or prediction-market outcomes.

list_events

Scan EVERY feed on a chain for flagged/anomalous rounds in one call and return a per-asset summary: how many rounds were flagged, the worst deviation in basis points, which sources caused it, and when it last happened. Call this for any cross-asset question. "which tokens/feeds have been flagged", "where did oracles misbehave", "anything anomalous lately". Instead of checking pairs one at a time with get_audit_trail (use that only when the user names a single pair). The result states the real window the recorded data covers, which may be shorter than the one asked for.

list_flagged

List your webhook subscriptions and whether each is still active. A subscription that auto-disabled after repeated delivery failures shows active:false with the reason.

list_webhooks

The caller's scheduled alerts and TWAPs, with each one's history. Call this for "my alerts", "is my DCA running", "what did my TWAP do". The history is the evidence: a TWAP slice shows the provider, the output amount and `executed: false`. Quote the slice count and the times rather than asserting it "is running".

list_tasks

List every aggregated price feed available on a chain, with each feed's live median price, healthy-source count, and aggregator contract address. Call this when the user asks what assets/pairs/feeds exist, or before querying a pair you are not sure exists on that chain.

list_feeds

List projects other builders have shipped on Squidlor, with what each one does. Useful for concrete precedent before proposing an integration.

list_showcase

Decode one on-chain transaction by hash: what it did, between whom, for how much, and whether it succeeded. Call this when given a 0x hash of 64 hex characters, or for "what happened in this tx", "did my swap go through", "why did this fail". Returns `found: false` for a hash the indexer does not have, which includes one that is still pending.

get_transaction

Best available route to swap one token for another, or to bridge across chains, plus an unsigned transaction for the user to sign. SUPPORTED CHAINS: Ethereum mainnet (1), BSC (56), Polygon (137), Arbitrum (42161), Optimism (10), zkSync (324). Ethereum mainnet IS supported: do NOT refuse a swap on the grounds that Squidlor only publishes price feeds on Arc, which is a fact about feeds and not about this tool. Call this for "swap X for Y", "bridge to <chain>", "what would I get for", "best rate". PASS TICKERS, NOT ADDRESSES: send "BNB" and "USDC" and the server resolves them from the engine token list. Pass a 0x address ONLY if the user gave you that exact address. Never write an address from memory, however familiar it looks: a made-up address is rejected outright, and one that happens to exist on another chain is a lost trade. Do not ask the user for an address before trying the ticker. If a ticker is ambiguous or unknown the call fails with the candidate addresses, and THAT is the moment to ask. The response echoes the resolved address under `from.token` and `to.token`: quote it when the resolution came from a name search (`resolvedFrom: "search"`), since that source includes lookalike tokens. Omit both chain ids to stay on one chain; a different toChainId makes it a bridge. CHECK `indicative` BEFORE TELLING ANYONE TO SIGN. When it is true there is no transaction at all: either no wallet was given (the aggregators reject an empty recipient), or the winning route quoted a price and then refused to build it, and the `note` field says which. In that case report the price and the reason and stop. Saying "sign it in your wallet" when nothing was produced sends the user hunting for a button that does not exist. Quotes expire: the response carries `expiresAt`, and after that the route must be re-quoted rather than signed. `transaction.data` is CALLDATA, not a transaction hash: never present it as a link, an explorer URL or a tx id, and do not paste it into the answer. `networkFee` and `providerFee` are numbers the aggregator reports with NO unit, and the unit differs between providers: never state a currency for them. Saying "network fee 0.30 BNB" on a 0.1 BNB swap invents a fee three times the trade. Either omit them or call them provider-reported and unitless. `outputUsd` IS dollars and is safe to quote as such. There is no hash to link until the user has signed. The client renders the transaction for signing, so describe the route and the expiry in words and leave the payload to it.

quote_swap

Unsigned transaction to send a token the caller already holds to another address. Call this for "send 50 USDC to 0x…", "transfer", "pay". The token is resolved by TICKER from the caller's own balances, so the contract address is the one they actually hold and the balance is checked as a side effect. If the ticker is held on more than one chain this refuses and asks for a chainId rather than guessing, because those are different assets. Amounts are limited to floating-point precision over JSON: for "send everything", read the balance and confirm the exact figure with the user rather than sending a rounded one. Do not ask for a contract address here: the ticker is resolved from what the wallet holds.

quote_send

Contract address and decimals for a ticker on a chain. Call this for "what is the USDC address on BSC", or to confirm which contract a ticker means before quoting. You usually do NOT need it before a swap: quote_swap accepts tickers and resolves them itself. `source: "curated"` is the engine's reviewed list and is canonical; `source: "search"` matched an exact ticker in the wider token collection, which also contains lookalikes, so quote the address in your answer rather than just the ticker.

resolve_token

Split a swap into equal slices over time (a TWAP). Call this for "buy X over the next hour", "DCA into", "spread this trade out", "ladder in". Tokens may be tickers. IMPORTANT: each slice produces a SIGNABLE QUOTE and nothing executes on its own, because server-side signing is off on this deployment. Say that when confirming, or the user will assume the trade is running unattended. Tell them they can check progress with list_tasks.

create_twap

Send a synthetic delivery to one of your webhooks now, to confirm the receiver works and its signature check passes without waiting for a real price move. Do this immediately after creating one: a receiver that silently rejects every delivery is indistinguishable from a market that never moved.

test_webhook

Watch a Squidlor oracle feed and trigger once when it crosses a level, reported back through list_tasks. This is the CHAT-NATIVE alert: no API key, no URL, nothing to deploy. If the user wants a webhook POSTed to a server they own, that is create_price_alert instead, which needs a key and a URL. Choose by whether they said "tell me" or "send it to my endpoint". Call this for "tell me when BTC hits 80k", "alert me if ETH drops below 2000", "watch XAU". The pair must be a feed Squidlor carries; the call fails with the available list if it is not. The result reports the current price and whether the condition is ALREADY true, which is worth saying: "alert me when BTC is above 1000" is not a useful alert and the user probably meant a different level. It also reports `priceSource`: "onchain" readings can be hours old outside market hours, so say which number the alert watches. THERE IS NO PUSH DELIVERY: the trigger is recorded and the user finds out by asking, via list_tasks. Do NOT say you will ping, flag, notify, message or tell them when it crosses, and do not say they will get anything "here" - nothing is sent. Say it is being watched and that they can check any time.

watch_price