Skip to content

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

Commit

Usage docs say what provider cost reports read, keep and leave out

Connecting a provider hands g1t an admin key for the whole organization, so owners need to know exactly what it reads, which key to make and where, what is stored and what never leaves billing, how often it is read, and that disconnecting deletes the key and the costs read with it. It also says the provider's figure already includes runs g1t made on the workspace's own key, so the two are never added together. Part of #157

G1t-Session:
ses_01m573jm1je4tv3wf6e9e2f7q4
syntaqxcommitted Parentb912f0cBrowse files
1 file+60−00/1 viewed
+60−0
10041004 and what covered it, for your own books. Invoices from Stripe remain the
10051005 record for what was charged to your card.
10061006
1007+## Provider cost reports
1008+
1009+g1t counts what its own runs cost. Your team's other agents (CI scripts,
1010+other tools, people's own sessions) are on your AI provider's bill too,
1011+and the provider's own cost report is the record of all of it. Connect
1012+the provider and g1t reads that report, day by day, at
1013+`g1t.sh/<workspace>/-/provider-costs` (**Provider costs**, under Money in
1014+the workspace's settings).
1015+
1016+**What it reads.** The provider's cost report for the whole organization
1017+the key belongs to, in US dollars, one line per day and line item:
1018+
1019+| Provider | Report | Line items |
1020+| --- | --- | --- |
1021+| Anthropic | The Usage and Cost Admin API's cost report (`/v1/organizations/cost_report`) | Each description, such as *Claude Opus 5.5 Usage - Input Tokens*, for each of the organization's Console workspaces |
1022+| OpenAI | The Costs API (`/v1/organization/costs`) | Each line item, for each of the organization's projects |
1023+
1024+**Which key.** An admin key, which only an organization's admins can make:
1025+
1026+- **Anthropic**: an Admin API key (it starts `sk-ant-admin`), made in the
1027+ Claude Console under **Settings**, **Admin keys**. An ordinary API key
1028+ or a workspace's key can't read the cost report. Individual accounts have
1029+ no Admin API: set up an organization first.
1030+- **OpenAI**: an admin key (it starts `sk-admin-`), made in the OpenAI
1031+ platform under **Organization settings**, **Admin keys**. A project or
1032+ user API key can't read the Costs API.
1033+
1034+Only an owner of the workspace can connect a provider, one key per
1035+provider. g1t checks the key with one small report request and says why
1036+when it doesn't work (the wrong kind of key, no permission), then reads
1037+the last 90 days.
1038+
1039+**What g1t keeps.** The key, sealed when it is saved; it is never shown
1040+again, never sent back to anyone and never written to a log. The page shows
1041+its last four characters, who connected it and when, when it was last read
1042+and what went wrong. And the costs: day, provider, line item, the provider's
1043+own workspace or project, and the amount. g1t uses the key for nothing but
1044+reading the report: never to run a model.
1045+
1046+**How often.** Once a day, around 04:17 UTC. Each read asks for the last
1047+seven days again, since providers revise recent days (and further back,
1048+up to 90 days, after reads have failed), and replaces what it had for
1049+those days. A provider that fails keeps its error on the page until a
1050+read works; the others are read as usual. The day in progress is
1051+incomplete at the provider too.
1052+
1053+**Not added to g1t's own figures.** Runs g1t made on the workspace's own
1054+key, such as Ask and sessions on [your AI providers](/guides/ai/), are on
1055+the provider's report as well. The provider's figure already includes
1056+them, so it is shown beside g1t's, never added to it.
1057+
1058+**Disconnecting.** **Disconnect** on the page deletes the key and every cost
1059+read with it. Replacing the key does the same and reads the last 90 days
1060+again, since a new key may belong to another organization. To stop the key
1061+working anywhere, also delete it at the provider.
1062+
1063+Members can see which providers are connected and what they reported;
1064+only owners connect, replace and disconnect them. Services read the figures
1065+with the billing service's `provider_costs` RPC.
1066+
10071067 ## For services: entitlements, reserve, settle
10081068
10091069 Every g1t service that starts something that costs money asks billing

Comments

Sign in to comment.