How to Generate and Manage API Keys on the Tavily API Platform

Updated

The Tavily API Platform (app.tavily.com) is where you generate and monitor API keys, track usage, and manage Extract/Crawl endpoints in one place. To get a key, sign in to the platform, open the API key section of your dashboard, and create a new key; from the same dashboard you can then monitor usage and manage the endpoints that key is used with. The exact button labels and menu locations are not documented in the available source material, so treat the steps below as the general flow rather than a literal click path.

What the platform covers

According to the platform's own description, app.tavily.com lets you:

  • Generate and monitor API keys
  • Track usage
  • Manage Extract and Crawl endpoints

That means key creation and key oversight live in the same place, so you don't need a separate tool to see how a key is being consumed.

Generating a key

  1. Sign in to app.tavily.com with your account.
  2. Open the API keys area of the dashboard. This is the section dedicated to generating and monitoring keys.
  3. Create a new key. The platform generates the key for you; copy it at creation time and store it in a secret manager or environment variable rather than in source code.
  4. Confirm the key appears in your list so you can monitor it later.

Expected result: a working key tied to your account that you can use against Tavily's Extract and Crawl endpoints.

If you can't find the option

The source material doesn't specify the exact navigation labels. If the key section isn't obvious after sign-in, look for wording around "API keys," "keys," or "usage," since those are the functions the platform advertises.

Managing and monitoring keys

Once keys exist, the platform is built to help you:

  • Track usage — see how much of your activity is attributed to your keys.
  • Monitor keys — keep an eye on which keys are active.
  • Manage Extract/Crawl endpoints — the same dashboard handles these endpoints, so endpoint management and key management are related tasks.

A practical routine:

Task Why it matters
Review usage regularly Spots unexpected spikes early
Keep one key per app or environment Limits blast radius if one key leaks
Retire keys you no longer use Reduces the number of live credentials

Security notes

  • Treat every API key as a secret. Don't commit keys to repositories or paste them into client-side code.
  • Store keys in environment variables or a secrets manager, and load them at runtime.
  • Rotate a key if you suspect exposure, and revoke the old one.
  • Because the platform tracks usage per key, separate keys per project make it easier to tell where traffic is coming from.

What isn't covered here

The available source material doesn't state pricing, free-tier limits, or whether sign-in is required beyond the fact that this is an account-based platform. Check the platform itself for current terms before relying on any assumption about cost or access.