A Guth Labs publication ↗
Back to News

Cloudflare adds provider-key activity review to AI Gateway

Cloudflare added an activity view for stored AI-provider credentials in AI Gateway on November 6. The Provider Keys area groups credentials by provider and shows masked previews, aliases, last-use dates and last-update dates. A security section flags keys whose recorded activity is more than 90 days old. Announcement

Cloudflare says usage tracking begins in November 2026. That start date is important: the new panel should not be treated as a complete history of older credential use. The company frames the feature as support for reviewing keys before rotating or removing them, rather than automatic deletion. Changelog

AI Gateway’s bring-your-own-key documentation describes how credentials stored in Cloudflare’s Secrets Store can be used without passing the provider secret in every application request. The gateway still requires its own authentication. If an application supplies a provider authorization header, that value is forwarded instead of being replaced by the stored credential. BYOK documentation

The same documentation warns that deleting a stored key immediately stops requests depending on it. Multiple keys and aliases can support a gradual migration, but alias behavior differs between direct provider requests and Unified Billing endpoints. The latter consult the default alias, with a possible fallback to Unified Billing when that default is absent. Key-management and alias rules

For operators, the useful outcome is a better starting point for a dependency review. A key that appears quiet may still support an infrequent scheduled task or a fallback route. Conversely, a frequently used credential may still have broader access than its application needs. Neither question can be settled from a last-used timestamp alone.

A careful review would connect each credential to an owner, a purpose and a tested replacement path before removal. This reporting did not inspect any customer credentials, change a configuration or test a migration. The feature adds visibility to an existing control point, while the consequences of rotation still depend on how each application is routed.

Sources

Sources and citations

Revision history

Published .