Skip to main content

​
Credit usage in an app

To see how many credits an app has used (including Build vs Chat), open Credit Usage in the app sidebar (admin or owner). For habits that reduce cost, see Controlling credits. That page keeps summary totals at the top, then uses three tabs:
  • Overview: credit periods, active build time, and spend by person
  • Activity: daily chart, day drill-down, and recent usage rows
  • Resources: cost by resource (build clusters)
You can deep-link a tab with ?tab=activity or ?tab=resources.

​
Dig into a day or a row

  • On Activity, click a day on the daily chart to see which conversations drove that spend, then open a conversation from the list.
  • On Resources, use Cost by resource to see build clusters (resources born in the same create turns) with create counted once per cluster. Expand a cluster for members and edit spend, or switch to Per resource.
  • Filter Recent usage by Build / Chat, Automation, MCP apply, Builder / User / Agent, or search by model and source. MCP apply rows are the flat fees for a successful change from a connected client (5 credits for a write, 10 for a check, one-off code run, or eval run). Those rows count as Build, not Chat. Lookups do not appear there. Model usage from those same applies (evals, capability runs, sub-agents) is listed separately and shows as the purple number on the MCP transcript. See GenieForge Builder MCP.
  • Search indexing rows (under Automation) are the credit cost of preparing searchable text after you add or change records, including knowledge collections. Looking up that search later does not add a separate charge.
  • Expand a usage row to see token counts (input, output, cache), resources created or changed in that turn, and a link to the conversation.

​
What a conversation produced

In a builder chat, the header shows credit amounts (yellow for an MCP apply fee, purple for model usage) and a Produced control. Click it to open the list of blueprint changes from that conversation (pages, forms, tools, and other capabilities), so you can connect spend to what was built. If something was both created and later updated in the same conversation, both actions are shown. That control stays visible in the builder even when an end-user agent hides credits in the portal.

​
Engineering history on resources

On a resource’s definition view (pages, tools, forms, views, agents, sub-agents, automations, hooks, libraries), Engineering history shows:
  • Engineering investment: create, evolution, and total credits on the turns that touched the resource
  • Age, how many conversations built it, and how long since the last change
  • Also created together: other resources born in the same create turns (click through to open them)
  • A timeline from Created through later Evolved conversations to Current
Those create-turn credits may include other work done in the same turns (for example a tool built alongside a page). That is expected: credits are billed per turn, not per resource. Account-wide balance and top-up live in your account billing settings, not on the app page. For cost-control guidance, see Controlling credits. For plans and current pricing, see Billing, plans, and credits or https://genieforge.ai.