Overview

When your team brings its own AI key, platform-tool connection, or MCP server, every call burns that account's quota with the upstream provider. The BYOK activity page lists each of those calls so you can see what is being billed to your provider — and which surface inside FlowFn triggered it.

Find the page

Open Teams, find the team you administer, and click BYOK activity on the team card. Owners and admins of the team can view it.

What appears in the list

When – the call's start time and duration.
Surface – agent run, workflow run, playground action, or playground chat.
Kind – platform action, AI model call, or MCP tool call.
Resource – the action name (e.g. stripe.create_charge), the model identifier, or the MCP server and tool that were called.
Tokens – input + output token totals when the upstream returns usage (AI model calls only).
Status – whether the call succeeded or failed at the upstream provider.

What is never logged

Request bodies, response bodies, prompts, completions, and API keys are never recorded. The audit captures metadata only, by design — your data is yours, not ours to retain.

Retention

Audit rows are kept for 90 days on every plan tier — this is a fixed window, not a plan setting. After 90 days a daily cron permanently removes the row. Your self-service data export includes BYOK audit rows tied to your own agent or workflow runs.

System-key calls

Calls that FlowFn makes on its own AI key (the platform-default option, billed in credits) are tracked in the credits ledger instead — those are not in BYOK activity to avoid double-counting.