Data guide
How cost and usage collection works
A directory listing does not mean automatic cost collection. Support depends on the provider's billing API, authentication and dedicated cost-read permissions.
Reviewed: October 25, 2026
Distinguish charges from usage
API collection reads billing and cost records exposed by a provider. Request counts or tokens alone are not final invoice amounts.
Rate-based calculations are estimates. Credit balances, top-ups and subscription quotas are not added to spending totals.
Dedicated cost-read access only
onecloud permits only the read access needed for cost and billing collection. Direct connections requiring business data, administrator or write permissions, or unverified wider scopes are restricted.
Use a parent cloud billing account when it includes a product's charges. Do not record the same charges again as a separate product source.
External collectors and Open API
Use project-scoped Open API keys to import billing exports or records from an approved collector. Connect internal accounting tools and scheduled jobs this way.
Keep original IDs and retry keys consistent to avoid duplicates. Review import history and read APIs to confirm results.
Manual entries fill billing gaps
Where no automatic billing API exists, record a verified company, service, date, amount and currency. Re-entering API-imported charges double-counts them.
Check the directory's collection method and provider documentation. Anyone can request an integration; the form states a reply within 3 days.
Questions and answers
Does every listed company connect automatically?
No. Entries distinguish billing API collection, usage, balances, estimates, parent billing accounts, external collectors and manual costs.
Can usage exist without a cost amount?
Yes. If an API returns no amount, usage is preserved separately from actual charges. Balances and quotas are also not spending.