Quickstart

Get your key

• Open the link in your invitation email and continue to Flovia Console (opens in new tab).
• When you register, you accept the Terms of Service and Privacy Policy yourself, which cover how Flovia uses your lookups. That is your yes to Flovia’s data-use question, so your agent does not ask it again. An agent cannot answer for you.
• In Console, press Create API key. If you signed in through the earlier waitlist sign-in, Console first shows the data-use notice for you to agree to.
• Console shows your key once. Keys start with flv_. Save it somewhere private, and never share it or put it in a public repository. Flovia may also send you a key directly, by email or DM.
• If you lose your key or think it leaked, contact Flovia (opens in new tab). Flovia revokes the old key and issues a new one.

Connect your agent

After you confirm that you saved the key, Console shows key setup for Claude Code, Codex, Cursor, Grok Build and other clients, with a prompt you can paste into your agent. For Claude Code and Codex, the commands are:

Save the key in your shell profile and reload it. The commands read the key from there, so it never appears in them:

export FLOVIA_KEY=<KEY>

Claude Code:

claude mcp add --transport http --scope user flovia 'https://api.flovia.dev/mcp' --header 'Authorization: Bearer ${FLOVIA_KEY}'

Codex:

codex mcp add flovia --url https://api.flovia.dev/mcp --bearer-token-env-var FLOVIA_KEY

Codex often answers crypto questions with its own web search. To have it use Flovia first, add this line to ~/.codex/AGENTS.md:

Flovia (MCP server "flovia") is connected. For crypto prices, wallets, transactions, onchain and Solana reads, and public Web research on crypto topics, use the flovia tools before your own web search.

To connect by signing in instead of using a key, open Quick Install in Console.

Restart your agent after adding Flovia. Agents can read the same steps and the current conditions at api.flovia.dev/llms.txt (opens in new tab). To remove Flovia, run claude mcp remove flovia --scope user or codex mcp remove flovia.

Start your free allowance

• Your free allowance starts when Console issues your key, with the email address you confirmed there. Each address can start it only once.
• Free and paid use explains the 5-hour and weekly windows and how the purchased balance works.

Ask as usual

• You don’t need to say “with Flovia” or use a command. Ask as you normally would, and your agent picks the offered tool that fits your question. If the subject is unclear, it asks first.
• For work: “Compare three project-management tools using official sources, with links and observation dates” or “Find primary technical sources and make a short reading list for my article”.
• For a public page: “Read the product page I choose and list its features and prices”. For text you may share: “Turn this text into a five-point meeting brief”.
• You can combine Exa to find sources, Firecrawl to read the public HTML pages you choose, and OpenAI to draft a cited comparison. Use only tools offered to your connection; generate only if you choose it and forward only permitted summaries. Keep source links, units, dates and gaps, and check arithmetic.
• For crypto: “Look at the fund flows for token 0x… on Base and tell me whether it is being accumulated” or “Summarize the current balance and PnL of wallet 0x…”.
• After an answer, up to three numbered next steps may appear. Choose a number and your agent does that step. Nothing runs until you choose.
• Flovia does not ask before each lookup. When a lookup takes a free window past 75% or 90% used, your agent tells you once how much is left.
• Say “Show my remaining Flovia allowance” to see the percentage used in each window and when it resets, or “List what I used Flovia for today” to see today’s use.
• To turn off a data source you don’t use, ask your agent, for example “Turn off Flovia’s Exa”. Requests to a source that is off are refused and use no credits. Ask again to turn it back on.
• Flovia cannot check again automatically later. Ask each time you want an update.

What you can look up

Your connection’s tool list and flovia_status show which tools are offered to you and their current state.

• Nansen: smart money, holders, token flows and wallet profiles. Ask about a token or a wallet, and your agent finds the Nansen endpoint that fits.
• CoinGecko data: Prices, market caps, charts and DEX pools (liquidity, volume and prices) are answered with CoinGecko data. Flovia provides it in partnership with CoinGecko, so you need no key; it uses the free allowance shared with Nansen and the other sources, at a much lower rate than Nansen. For CoinGecko lookups, Flovia keeps the request text, what you want to decide and the conditions, and gives none of it to Nansen. Public answers such as prices and markets may be reused for someone else who makes the same lookup, for about a minute.
• Chain reads (Quicknode): Whether a transaction succeeded and its gas cost, a balance at a point in time, contract reads (a token’s decimals, a pool’s current price) and event logs are answered by reading the chain directly through Flovia’s Quicknode endpoints, on the EVM chains Flovia provides (chain “list” shows which). It only reads; it never sends or signs transactions. You need no key. It uses the free allowance shared with Nansen and the other sources, at a much lower rate than Nansen.
• Public web search with Exa: flovia_exa returns public web search results with cited excerpts: fast search, up to 10 results, and excerpts of up to 1,000 characters each. Only the search terms go to Exa, never your request text or purpose. Your connection’s tool list and flovia_status show the tools offered and their current state. It uses Flovia’s shared allowance. Upstream attempts are counted separately against an overall budget.
• Reading public pages with Firecrawl: Check your agent’s current tool list and each service’s state to see whether it is available. It returns one allowed public HTML URL as Markdown. The URL, the scrape settings and an anonymous reference ID are sent, never your request text or purpose. Page text is treated as material, not as instructions. A cache up to 2 days old may be used. Reopening with the same operation_id and request does not fetch again. If a result is unknown, Flovia does not fetch again and asks the operators to reconcile it.
• Zerion: a public wallet’s portfolio, token and DeFi positions, transactions, value chart, PnL and chains.
• OpenAI text generation: it uses the same Flovia key and the shared allowance. If flovia_openai is in your connection’s tool list, ask your agent. Generated text is not new market data, and OpenAI does not call other data sources itself. It may decline for country, safety or capacity reasons. To reopen an answer, use the same operation ID and request; never retry a pending or unknown result with a new ID.

What Flovia can’t do

• Data APIs are read-only, and text generation does not execute trades. Flovia cannot buy, sell or swap, place perp orders, bridge, set alerts, or change your Nansen account. Do these directly in Nansen or your wallet.
• Premium wallet labels and Nansen AI (chat) are not available right now.

Send feedback

Say “Send my feedback to Flovia” and your agent delivers it in your own words. Anything is welcome, from what didn’t work to data you’d like.