Credit Usage

Credits are consumed in your Fetch Hive account when you run interactions in both the Dashboard and the API. The amount of credits you consume will change, depending on whether you set an interaction to either "Personal" or "Hosted" charge type,. You can view your current credit usage by navigating to the Settings in your dashboard:

Navigate to Settings in your dashboard

Then click Billing in the left hand sidebar to view your current credit usage:

Navigate to Billing in Settings

Example of credit usage

If I run the following workflow with "Hosted" charge type, the charge breakdown will be the following:

• Google Search / 3 credits

• AI Prompt / 5 credits (Credit usage will vary depending on the prompt)

• Exa Search / 15 credits

Total of 23 credits.

If I run the following workflow with "Personal" charge type (using your own API keys), the charge breakdown will be the following:

• Google Search / 1 credit

• AI Prompt / 1 credit

• Exa Search / 1 credit

Total of 3 credits.

Sync vs. Async Workflow credit usage

LIVE Workflows in your Fetch Hive account can be run either as "sync" or "async" (default is "sync"). This indicates whether your workflow should run immediately, or be queued up to run later on (usually occurs within 30 seconds of their trigger). The advantage to running "async" Workflows, is the reduction in credit usage, as any "sync workflows adds an additional 1 credit PER step in the workflow. If I run with a workflow with a "sync" workflow setting using "Personal" charge type:

• Google Search / 2 credits

• Exa Search / 2 credits

• AI Prompt / 2 credits

If I run with a workflow with a "async" workflow setting using "Personal" charge type:

• Google Search / 1 credit

• Exa Search / 1 credit

• AI Prompt / 1 credit

Please note, when setting up a Workflow to be "async", you are required to specify a "callback_url" which indicates where the completed Workflow output data should be delivered for your app. See Workflow Execution for more details.