Why it is different

Addresses, observations, server checkpoints and toolchain results give you evidence to inspect.

Last verified against production: . See current limits and availability.

Identity starts with an address

Several contracts can use the same ticker. Search CASHCAT in Markets and compare the separate addresses, pools, observed depth and available activity. A familiar name alone cannot establish which contract people trade.

Fletch checks Robinhood's published listings against bytecode, symbol and decimals. Other discovered tokens receive a community, lookalike or unknown verdict according to their recorded evidence. A lookalike warning includes the verified address it matches. Provenance describes identity; investment decisions and contract-risk assessment need further evidence.

Numbers have a source and an age

A DEX price comes from recorded pool state. A feed price comes from the specific feed Fletch reads. Compiler results come from Foundry. These sources answer different questions, and the interface labels them.

Unread means Fletch has no usable reading. Stale means a previous observation has passed its current-data window. Partial history means the indexer has not covered the requested interval. A dash keeps those cases visible; zero is reserved for an observed zero.

The watcher lives on a server

The Watch daemon checkpoints its block position in Postgres, reads logs in bounded ranges and places matched events in a delivery outbox. A process restart resumes from stored progress. Delivery failures retry with backoff, and duplicate event keys prevent repeated matching from creating a new alert.

Events are sequencer-confirmed. A chain reorganization can replace them. When a checkpoint hash changes, the poller rewinds up to 64 blocks and retracts pending deliveries above that point. Messages already sent remain in the recipient's chat. Treat an alert as an observation at that block, with the transaction receipt available to inspect.

The same data is available to agents

An agent can read llms.txt, call the scoped-key API or connect the MCP server. Ask for the relevant token and its freshness before using an address or price in generated code. The builder receives short endpoint guidance and fetches chain facts on demand, so unrelated prompts do not carry a market dump.