Billing, Credits, and Usage

DevJock pricing is designed to be readable. There are no hidden multipliers and no estimates you cannot check against the underlying activity.

How credits and pricing work

A credit is one US dollar. You buy credits up front, and a flat fee is charged at the time of purchase. That fee is the only markup: DevJock does not add a margin on top of token usage. When an agent or chat consumes tokens from a model provider, the cost is passed through and drawn from your credit balance at the provider's rate.

Because model usage is passed through without markup, the number you see for a run is the number the provider charged for it.

Auditing usage

Usage is auditable down to the individual task. Every unit of work that spends tokens is attributed, so you can answer questions like "what did this task cost," "which agent spent the most this sprint," or "what has this user run this month."

To review usage:

• Open the Account area from the user menu and go to My Account for your personal balance and history, or My Organizations for organization-level totals.
• Drill into a task in the brain to see the token cost attributed to work done on that task.
• Group spend by the agent or user that ran the work, where the account views support it.

Drilling into token cost

Each spending event records the model used and the tokens consumed, so a task's total cost breaks down into the individual runs behind it. This lets you trace an unexpected charge back to the specific agent call or chat session that produced it, rather than reconciling against a single monthly total.

For per-endpoint accounting and programmatic access to usage records, use the live interactive API references reachable from the app's user menu.