# Billing-read OAuth for API cost dashboards

**URL:** <https://community.perplexity.ai/t/billing-read-oauth-for-api-cost-dashboards/6004>\
**Category:** Feature Requests\
**Tags:** api\
**Created:** [September 3, 2026, 10:23pm UTC](https://community.perplexity.ai/t/billing-read-oauth-for-api-cost-dashboards/6004 "2026-09-03T22:23:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Avanderheyde](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/avanderheyde/32/3526_2.png) [@Avanderheyde](https://community.perplexity.ai/u/Avanderheyde)\
**Post date:** [September 3, 2026, 10:23pm UTC](https://community.perplexity.ai/t/billing-read-oauth-for-api-cost-dashboards/6004/1 "2026-09-03T22:23:39Z")

</div>

Hi Perplexity team,

I’m building Vibe Costs, a dashboard that lets developers monitor live software and AI infrastructure spend in one place.

Perplexity’s API console already shows billable usage and credits. Today, users can trace spend to an API key by matching the key suffix in invoices, but I could not find a documented customer-authorized billing integration.

Would you consider a billing:read OAuth scope for third-party apps? The useful fields would be current accrued API spend, prepaid credits remaining, auto-top-up charges and status, billing period, usage by product or model and by a stable, display-safe API key identifier, invoices, and data freshness. It should not allow inference, key management, or billing changes.

Our proposed response shape and authorization requirements are here:

> **[Open Cost Read API documentation](https://vibecosts.app/cost-api/docs)**
>
> Implementation guide for providers adding customer-authorized, read-only access to live incurred costs.

If this is already possible through a documented authorization path, I would appreciate a pointer. Otherwise, I would be happy to test an early version.

Thanks,  
Alderik  
Vibe Costs

---

<div class="post-metadata">

**Author:** ![andrewmadson-pplx](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/andrewmadson-pplx/32/3428_2.png) [@andrewmadson-pplx](https://community.perplexity.ai/u/andrewmadson-pplx)\
**Post date:** [September 3, 2026, 10:51pm UTC](https://community.perplexity.ai/t/billing-read-oauth-for-api-cost-dashboards/6004/2 "2026-09-03T22:51:53Z")

</div>

Hello @Avanderheyde ,

Thank you for your feature request suggestion! I have shared it with the team. I appreciate your detailed proposal and will let you know if there is an update.

Andrew

---

<div class="post-metadata">

**Author:** ![Avanderheyde](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/avanderheyde/32/3526_2.png) [@Avanderheyde](https://community.perplexity.ai/u/Avanderheyde)\
**Post date:** [October 20, 2026, 1:23pm UTC](https://community.perplexity.ai/t/billing-read-oauth-for-api-cost-dashboards/6004/3 "2026-10-20T13:23:13Z")

</div>

Hi Perplexity team,

Checking back now that this request has had some time with the team. Is there any update on customer-authorized billing-read access for API spend and credits, or a product or API owner I should stay in touch with?

Totally fine if it is still under review. I would be happy to test an early version against my own API account.

Thanks,  
Alderik