> 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/verify-2026-09-08-agent-nft-reads.md).

# Verify 2026-09-08 — agents read and act on the indexed NFT market

**Migration:** none. **Deploy:** api + worker (detached, one at a time).

## What changed

* 12 new capabilities registered in `packages/domain/src/agent-capabilities.ts` (ids in `packages/core/src/schemas.ts`): `nft_collection_detail`, `nft_price_history`, `nft_activity`, `nft_orderbook`, `nft_traits`, `nft_holders`, `nft_drops`, `nft_trending`, `nft_discovery`, `nft_snipe_status`, `nft_snipe_manage` (transaction risk), `nft_trover`. Registering them updates the planner prompt automatically.
* `agentNftEntitiesSchema` widened (window, interval, lifecycle, mode, eventTypes, maxRank, traitCriteria, budget, expiresInHours, trigger, snipeId, name); defaults keep older plans valid.
* Worker `apps/worker/src/nft-market-reads.ts` (new): API reads over `AGENT_INTERNAL_API_URL`, entity resolution (contract → slug → name search), one reader per capability returning `NftReadResult` with `freshness` and a ≤200-char `summary`. `readReply` in `agent-orchestrator.ts` gains a `channel` argument: X gets the summary, web gets summary + data. `nft_search` and `nft_market_snapshot` are DB-first; `market_chart` routes NFT entities to price history; `manageNftSnipe` arms/cancels plans with the route's rules.
* `@trover/domain` gains `NftReadResult`, `nftFreshnessFrom`, `compactNftSummary`, `nftSnipePlanSchema`, `delegatedExecutionWallet`, `nftSnipePlanJson` (the API route now imports them).
* MCP (`apps/api/src/mcp-routes.ts`): new ids in `nftCapabilities`, execution modes (reads `direct`, snipe manage `agent_run`), scope, typed inputs, deterministic messages; indexed reads answer through `app.inject` on the API's own routes.
* `apps/worker/src/contract-watch.ts` (new) + scheduler `contract-balance-watch` every 10 min: balances, `router.totalOwed`, `league.totalAttributed`, `eth.reservedByToken`; gauge `trover_contract_balance_eth`; warns when a Safe action is due. No-op until the stack addresses are set.
* Tests: `tests/agent-nft-reads.test.ts` (new), `tests/agent-planner.test.ts` (registry, risks, snipe-as-question refused). Docs: `docs/agent-orchestration.md`, `docs/customer-mcp.md`.

## Verify

Typecheck (I ran): core, domain, api, worker. Tests (you run): `pnpm vitest run tests/agent-planner.test.ts tests/agent-nft-reads.test.ts`.

Deploy:

```
ssh trevor-server 'cd ~/trover && nohup bash -c "set -x; git pull --ff-only && docker compose -f docker-compose.yml -f docker-compose.production.yml build api worker && docker compose -f docker-compose.yml -f docker-compose.production.yml up -d --force-recreate --no-deps api worker; echo DEPLOY_EXIT=\$?" > ~/trover/deploy-20260908-h.log 2>&1 < /dev/null & echo launched'
```

After: on the website chat ask "what's the floor and last mint of ponsguy" and compare with the terminal; the reply must carry the data age. Tweet the same at the bot: the reply is the one-line summary. `docker logs trover-worker-1 | grep "contract balance"` shows nothing until the addresses are configured.


---

# 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/verify-2026-09-08-agent-nft-reads.md?ask=<question>&goal=<endgoal>
```

`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.