CS: Expose API Usage Data (by Object, Source, User) in Report Builder

We'd love to see API usage exposed as a reportable object in Report Builder.

A 50,000 daily API limit is shared across every consumer - connectors, integrations, and now the MCP Server, which uses unpredictable, natural-language user prompts. As it stands, we have no way to see which source is driving usage before we hit the ceiling.

A reportable object with object queried, call source, user/service account, and timestamp/rolling count would let admins build their own dashboards and alerts; No new UI needed, and consistent with how rule run history and connector job logs already work.

A small ask resulting in real impact for anyone managing usage at scale.

This should be an absolute priority for Gainsight given the MCP push & upcoming Agent Studio, which I imagine will continue to pull from the same usage pool as the other tools that ​@darkknight pointed out.

At the very least, if a full reporting object would be too intensive to build out quickly, I’d support a section within the Application Settings that simply displays the number of calls made in the last 24 hours vs. that 50,000 call max. This is no different than how Salesforce and other tools surface the information and should be accessible by admins regardless.

FYI ​@Ritika Jindal ​​

This is desperately needed. 

Now the MCP exists we are at our end-users mercy for API calls.

As a real-world example of the impact this black hole has, I’ve been trying to debug a skill/dashboard someone wrote and found it would sometimes, seemingly randomly, return 0 results despite me knowing there should have been records that qualify. I can’t (and neither can Claude) find a reason for this, and one thing I’d like to be able to review is whether we are hitting API limits. 

I’m particularly worried that our MCP usage will impact on key operational components that we need to keep API calls available for, like our connectors and certain rule actions. We just have no way of knowing right now and that is troublesome (please read that as intended → in a British-understated-kind-of-way). 

Even something like what Claude does… but we definitely need to be able to see usage per call source. Surely this data is already available. Let’s get it available in report builder!