> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/engineering/prompts-and-examples.md). # Prompt and output examples ## Evidence normalizer The OpenAI normalizer receives only the deterministic analysis object: ``` return the supplied evidence analysis without adding facts. preserve conflicts and unknowns. never call a token safe. ``` The response must match `token_analysis_result`. Factual fields, risk flags, confidence, evidence summaries, and unknowns are reconstructed from stored evidence after the model response. ## Reply author ``` write one compact x reply in lowercase. be evidence-aware and restrained. never promise gains, give financial advice, or say safe. lead with identity conflict or weak evidence. call the product trover and preserve configured x usernames exactly. ``` Expected examples: ``` checked it. abi isn't published and visible liquidity is thin, so confidence is low. the pair exists, but this shows higher visible risk. ``` ``` address mismatch first: this is not the canonical $trover contract. possible old contract, duplicate, spoof, or outdated source. don't mix their metrics. ``` ``` rpc and explorer checks worked, but market data is unavailable right now. i can't verify live liquidity or price, so confidence stays low. ``` Disallowed outputs include “safe,” “guaranteed,” “buy now,” promised gains, invented holder counts, or metrics without an evidence ID. ## NFT market (website chat and X) Since 2026-09-08 every NFT question is answered from Trover's own index through the API's NFT routes. The reply always leads with the deterministic summary built by `compactNftSummary` (at most 200 characters, ends with the data age). On X the summary is the whole reply. On the website the summary is followed by the structured `data` block the chat renders as detail. Numbers below are illustrative; the shape is exact. ### Floor and last mint of a collection Website: `what's the floor and last mint of ponsguy` X: `@troveragent floor of ponsguy?` ``` ponsguy · minting · minted 3,210/5,555 · floor 0.012 ETH ($31.20) · 24h vol 1.84 ETH / 61 sales · 1,204 owners of 3,210 · 84 listed · last mint 3m ago · last sale 41s ago · data 12s ago ``` Capability `nft_collection_detail`. The web reply appends `data.market`, `data.mint` (stages, mints per hour, price) and `data.links` (terminal and OpenSea URLs). ### What is minting now Website: `what's minting right now on robinhood` X: `@troveragent what's minting now?` ``` minting on robinhood · Pons Planets 512/5,555 (12/h), Ink Brokers 4,100/4,444 (3/h), Alpha Gardeners 220/1,000 (30/h) · data 9s ago ``` Capability `nft_drops` with `lifecycle=minting`. `upcoming` and `ended` (sold out within the last 15 minutes) use the same shape; a collection name in the question switches to that collection's mint state. ### Trending in the last hour Website: `trending nfts in the last hour` X: `@troveragent trending last hour` ``` trending on robinhood (1h) · ponsguy 61 sales / 1.84 ETH, thefirmbrokers 22 sales / 0.61 ETH, inkbrokers-nft 9 sales / 0.20 ETH · data 7s ago ``` Capability `nft_trending`, window `1h` (default `15m`; `1m` to `24h`). The web reply appends the ranked rows with floor, holders, listed percent, minted of max and last mint. ### Top holders Website: `who are the top holders of ponsguy` ``` ponsguy · 1,204 owners of 3,210 · 37.5% unique · top 10 hold 18.2% · data 15s ago ``` Capability `nft_holders`; web data lists the top holders with counts and share. ### Price history Website: `ponsguy price history last 24h` X: `@troveragent how did ponsguy trade today` ``` ponsguy · 24h sales: 0.009–0.018 ETH, last 0.012 ETH (+9.1%) · data 12s ago ``` Capability `nft_price_history` (`market_chart` on an NFT entity routes here); web data carries up to 120 hourly candles and floor points. ### Arm a snipe Website: `snipe ponsguy on reveal, rank 50 or better, max 0.02 eth each, budget 0.1 eth` ``` snipe armed for ponsguy: on reveal, rank ≤ 50, up to 1 at ≤ 0.02 ETH each, budget 0.1 ETH, expires 2026-09-11T14:02:11.000Z. plan cln2… ``` Capability `nft_snipe_manage`, action mode only. Without a delegated embedded wallet the reply is `delegated_execution_wallet_required: … enable delegated trading at https://trover.tech/account.`; with per-trade confirmation on it is `confirmation_required_incompatible: …`; a missing rank or budget is `snipe_details_required: maxRank: a rank ceiling or at least one trait is required. say the max price per item, the total budget, and a rank ceiling or traits.` A question ("should I snipe ponsguy?") is refused as a transaction and answered as research. ### Cancel it Website: `cancel my ponsguy snipe` ``` snipe plan cln2… for ponsguy cancelled; 0 fills already made stay on record. ``` `nft_snipe_status` ("my snipes") answers `1 armed of 3 snipe plans; ponsguy 0/1 filled, 0.1000 ETH left` on X, with the plan JSON appended on the web. ### Not found ``` collection_not_found: no indexed collection matches "pons guys"; closest: ponsguy (robinhood/ponsguy), Pons Planets (robinhood/pons-planets). ``` Disallowed in any NFT reply: numbers that are not in the summary or `data`, a reply without the data age, or OpenSea figures substituted for an indexed read that failed (the failure is stated as `_unavailable`). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.trover.tech/engineering/prompts-and-examples.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.