Credits & Usage
Credits are TinyCommand's unit for automated work. Every workflow step uses 1 credit, and a few data-heavy steps (AI agents, search, scraping, SEO and enrichment) use more. One credit pool covers every product in your workspace.
What uses credits
| Category | Feature | Credits |
|---|---|---|
| Workflows | Any workflow step (logic, integrations, database steps, Send Email to Yourself) | 1 per step, even if the step errors |
| AI | Agent, Tiny Scout, Tiny Composer steps | 10 per step |
| AI | Tiny Search | 10 per step |
| AI | TinyGPT, Tiny GPT Writer, Tiny GPT Researcher | At least 1 per step |
| Scraping | Scrape Page, Extract Data, Map URLs | 2 per step |
| Scraping | Crawl Site | 2 per page crawled |
| Scraping | Web Search | 2 per result returned |
| Vision | Extract Text (OCR), Read PDF, Extract Table, Extract Fields, Ask Document, Classify | At least 1 per step |
| Enrichment | Company Enrichment, Email Enrichment (workflow steps) | 10 per step |
| Enrichment | Person Enrichment (workflow step) | 20 per step |
| SEO | TinyKeyword, TinyRank, TinySERP, TinyMeta, TinySchema, TinyCluster, TinyBacklink | From 1 to 20 or more, see Billing & Plans |
| TinyTables | Company look-up, person look-up, find email, verify email | 10, 20, 10 and 5 per row, only when data is found |
| TinyTables | AI column | Nano 1, Mini 5, Pro 10, Max 20 per cell |
| Discovery | New companies, new people | 20 per company, 10 per person that lands in your table |
| Agents | Conversations with an agent that runs on TinyGPT | Uses credits |
What never uses credits
- Building forms and collecting form responses
- Building tables and storing records
- Designing email templates in TinyEmails
Credits by plan
| Plan | Monthly credits |
|---|---|
| Free | 1,000 |
| Basic | 10,000 |
| Professional | 50,000 |
| Agency | 250,000 |
See Billing & Plans for prices and what each plan includes. Paid plans (Basic and up) also include bulk credit purchase.
Monitoring usage
Go to Monitor → Credit Usage to see:
- Remaining: credits left in your balance
- Used: credits consumed so far
- Forecast: how long your balance lasts at your current daily average
- Usage by Product: which products used your credits
- Daily Credit Consumption: a chart of usage over time
- Recent Credit Activity: the latest credit charges
The credits card in the sidebar also shows your balance and warns you when you're running low.
Reducing credit usage
| Strategy | Details |
|---|---|
| Filter before expensive steps | Add If-Else or Filter steps before AI agents, enrichment and scraping. Skip records that don't need them. |
| Cache results | Store AI and enrichment results in a table. Before calling again, check whether you already have the answer. |
| Keep workflows short | Every step uses at least 1 credit, so remove steps that don't change the outcome. |
| Batch with limits | In For Each loops, set a limit during testing. Process 5 items, not 500. |
| Check your schedules | A schedule that runs more often than needed multiplies every step's cost. |
Credit usage in test runs
Test runs use credits the same way production runs do. When testing workflows with credit-heavy steps:
- Use the individual node Test tab (runs one node, costs credits once)
- Don't run the full workflow repeatedly during development
- Use small sample datasets for testing
A For Each loop with 1,000 items that runs a Person Enrichment step can use about 20,000 credits (20 credits x 1,000 iterations), plus 1 credit for every other step in each iteration. Always add a limit during development to avoid using your entire monthly allowance by accident.
The most common cause of unexpectedly high credit usage is a scheduled workflow running more often than intended. A workflow scheduled every 5 minutes runs 288 times a day, and each run uses at least 1 credit per step.