Better Costing/Pricing Analysis

Focusing on Analytics, I appreciate the intent.

But because this Agent is brand new, I happen to know that, in reality, I am the only user, and that there has been only one “use”. Maybe the runs are page refreshes or something. But my point is that the actual use count right now is about 0.9, as I am almost done the first complete use of the Agent.

The may be room for another metric - “Completions” or similar, although LLMs have already usurped that word…“Deliveries”, maybe. The valuable parameter is - How many actual users reached their actual destination? A reasonable question, no?

I think this now (as of the last few months) counts uses in the builder as well. Are you sure you didn’t do any builder tests?

Oh, that’s informational. But it buttresses my point. Maybe an Exclude Builder activity checkbox?, which I think would become a default once the Agent is in production.

I still think that the current widget is dysfunctional, including “Users” must be counting anonymous/Builder anonymous users, because I am the only biological human using this Agent; and “Runs”, if I am not mistaken, actually means something very much like “Prompts”? The thing that is actually “Runs” is aka “Uses” in Pickaxe?

As I tell Claude, even badly named variables and fields are technical debt, which is forbidden- never to be purposefully created, at least.

During testing, I had a few Prompts that resulted in failed calls to my API, so those were not completed (no response) - I guess that should become vanishingly small in Production, but counting or not counting those might make the difference between .10 per Prompt and .20 - which has pricing implications, so a conditional toggle, Show Only Successes could work.

Maybe the widget should simply have or respect the Agent status - Dev or Production, and behave slightly differently?

Anyway, it should be better.

Per Wingman:

So you’re right — you’re the only real biological user. The 6 count comes from:

  • 3 anonymous API_GUEST sessions — these are almost certainly builder preview sessions (when you or someone opens the agent in the Pickaxe builder without being logged in as an end user)
  • 1 Pickaxe team member (danny@pickaxeproject.com) — probably a support/QA test
  • 1 mystery registered user (USERD2PJHCYUZBLTNT8TL7ZP) — worth investigating; could be another builder test account

**The Analytics widget counts all unique userId values, including anonymous builder previews, which inflates the number. It’s a known quirk of how Pickaxe tracks sessions.
**
Known quirks should be driven ruthlessly to zero.

Actually I think this represents a pretty amazing system. I mean, think about what happened here. You were able to get the exact answer from the Wingman. And it turns out support is actively helping you. We don’t really want to clutter the interface with more buttons, but give you the power with the wingman. But noted!

1 Like

Agree. Wingman is awesome, full stop.

I would love to be able to look at the Analytics block and actually know what my cost per completed run is. I thought that was the idea.

I also have this crazy idea as a native English speaker that using the right words for things is important.