# Check the same things every day and see what changed

Requests to repeat every day: a market brief, a watched wallet, and news on a topic, each compared with your last run.

Some questions are worth asking every day: how the market moved, what a wallet you watch did, and what is new on a topic you follow. Each request below gives the same kind of answer each time, and compares it with your previous run when your agent has that run. Your agent answers with CoinGecko, Zerion, Nansen, Exa and Firecrawl data.

## Ask your agent

Copy one request into the agent you already use, and fill in the part in parentheses at the end.

### CoinGecko: a morning market brief

```text wrap
Give me a short morning market brief in US dollars: the price and 24-hour change of the 10 largest coins by market cap, the total crypto market cap, Bitcoin's market share, and when CoinGecko last updated the data. If you have the brief from my previous run, list what changed since then. If you do not, say this is the first brief and give today's values only.
```

### Zerion: a wallet's latest activity

```text wrap
Check the public wallet address at the end of this request. Give its total value across all chains, with the currency and time of the value, and list its most recent transactions with their dates. If you have the total from my previous run, say how much it changed. If you do not, say this is the first check. Address: (paste a public wallet address here)
```

### Nansen: one chain's last 24 hours

```text wrap
Check the public wallet address and chain at the end of this request. List its transactions on that chain over the last 24 hours, with their dates, tokens and amounts. If there are none, say so. Address and chain: (paste a public wallet address and its chain here)
```

### Exa: what is new on a topic

```text wrap
Find up to five public pages about the topic at the end of this request that were published in the last 24 hours. List each with its title, link, publication date and one line on what it says, newest first. If you find none, say so instead of widening the dates. Topic: (write your topic here)
```

### Firecrawl: one page you follow

```text wrap
Read the public HTML page at the end of this request and summarize it in five lines, with the date you read it. If you have the summary from my previous run, list what is new since then. If you do not, say this is the first reading. If the page cannot be read, say so and stop. Page: (paste the URL of one public HTML page here)
```

## What your agent uses

- `flovia_coingecko` reads prices, market caps and the whole market's size from CoinGecko.
- `flovia_zerion` reads a public wallet's portfolio and recent transactions from Zerion. Only the address and filters go to Zerion.
- `flovia_endpoints` finds the Nansen endpoint, and `flovia_nansen` fetches an address's transactions on one chain from Nansen.
- `flovia_exa` searches the public web with Exa. By default, Exa returns up to 10 search results, each with cited excerpts of up to 1,000 characters. If your agent sets `text_max_characters` (1 to 12,000), each result comes with up to that many characters of its page's text instead. Page text can be cut short or missing, and Flovia does not check that it is complete. A date range can leave out pages that have no publication date or a wrong one. Only your search terms and search settings go to Exa, so keep private or personal information out of them.
- `flovia_firecrawl` reads a page as Markdown. Firecrawl reads one public HTML page, or the text of a public PDF (its first 10 pages), at a time, only from sites Flovia allows.

Flovia does not keep your earlier replies for the next run to compare with. Save each reply where your agent can read it next time, such as a note or a file.

To repeat a request every day, add it to your agent's own scheduling feature, if your agent has one. Otherwise, paste it in yourself each day.

Use a source that appears in your agent's current tool list. A source that is not listed is unavailable. Each run uses a little of your free allowance, or of your purchased balance when the free allowance cannot cover it. [Free and paid use](/usage.md) explains both.

## Example reply

The reply below is made up for illustration. Your replies carry your own values.

> Morning brief in US dollars, from CoinGecko data updated 07:55 UTC:
>
> - Bitcoin: $12,345.67, 24-hour change +1.2%
> - Ethereum: $1,234.56, 24-hour change -0.5%
> - Total crypto market cap: $1.23 trillion, Bitcoin's share 51.2%
>
> Since your previous brief: Bitcoin is up 2.1%, Ethereum is down 0.8%, and the total market cap is up 1.0%.
>
> Data provided by CoinGecko.

### Wallet change

> Wallet check for the made-up address 0xEXAMPLE (Zerion data read 2026-01-02 08:00 UTC):
>
> - Total value across all chains: $1,234.56 USD
> - Recent transactions: 2026-01-02 a transfer in of 10 EXAMPLE tokens; 2026-01-01 a transfer out of 5 EXAMPLE tokens
>
> Since your previous check: the total is up $34.56 (2.9%). If you had no earlier total, the reply would say this is the first check and give today's values only.
>
> Data provided by Zerion.

### New on a topic

> Pages about your topic published in the last 24 hours (Exa search run 2026-01-02 08:00 UTC):
>
> 1. "Example headline one" (example.com/one, published 2026-01-02): one line on what it says.
> 2. "Example headline two" (example.org/two, published 2026-01-01): one line on what it says.
>
> Only two pages matched, so the list has two items. If none had matched, the reply would say so.

## Next steps

- For a one-off check, see [Get a quick market summary](/use-cases/market-summary.md), [Check what a wallet holds before you send](/use-cases/wallet-check.md) or [Get a cited answer from the public web](/use-cases/web-research.md).
- [Data use](/data-use.md) says what each source receives.
- See every request in [Use cases](/use-cases.md).

Anyone can create a Flovia account. If you have not connected yet, start with the [Quickstart](/get-started/quickstart.md).
