Rulebase Credit Plan Structure

Included credits

Before overage, the effective price per credit depends on the plan price and how many included credits the customer actually uses.

For example, if a plan is ??/month and includes ?? credits/month, then at full usage the included credits work out to:


?? / ?? credits = ?? per credit

That is roughly ?? per credit, or ?? per ?? credits, when the customer uses the full monthly allocation.

For comparison, overage is ?? per extra credit, or ?? per ?? credits.


?? / ?? = ??x

In this example, overage credits are roughly ??x more expensive than fully used included credits.

Included credits reset monthly. If a customer does not use all included credits, their realized price per used credit is higher because the monthly plan price is fixed.

Monthly plan	Credits used	Effective price / credit
??	??	??
??	??	??
??	??	??

The simple takeaway: included credits are most cost-effective when usage is consistent. Overage provides flexibility for occasional spikes.

Product structure

Customers pay for a Rulebase plan. That plan includes a fixed number of monthly credits.

Credits are the usage unit for running Workflows and the Agent:

Workflows are API2 agents that run from triggers, schedules, approvals, or workflow-style executions.
Agent is the interactive chat agent that answers users, reasons over context, calls tools, and can trigger workflows.

Credits reset each month on self-serve plans. Larger plans can include custom credit pooling or rollover terms.

Usage types

Product type	Rulebase term	Pricing behavior	Why
Workflows	API2 agents	Predictable credit cost	The same workflow graph should cost the same credits each run, assuming the same branches and data volume.
Agent	Chat agent	Variable credit cost	Cost depends on model choice, message length, conversation history, tool calls, and workflows triggered from chat.

Workflows have more predictable pricing: a base credit cost per workflow run, plus the cost of any paid steps. Basic integration, routing, formatting, and data-manipulation steps can be included or low-cost. AI, web scraping, enrichment, and custom-code steps use credits.

The Agent is more usage-sensitive. One user message can require multiple internal AI steps, tool calls, retrieval calls, or workflow executions. Tool-using chat sessions therefore cost more than simple question-answer turns.

Example credit costs

Action	Credit cost
Basic workflow run	??
Standard AI workflow step	??
Advanced AI workflow step	??
Expert AI workflow step	??
Web search or scraper step	??
Contact or company enrichment	??
Custom/code step	??
Agent chat turn	Variable
Workflow triggered by Agent	Workflow run cost + step costs

For teams that use their own model or provider key, Rulebase can reduce the AI portion of the credit cost while still charging for orchestration, tool execution, workflow runs, and platform usage.

Overage

If a customer runs out of monthly credits, they can enable overage.

Overage costs ?? per extra credit. A cap, such as ??x the monthly credit allocation, helps keep spend predictable during high-volume workflow runs, long Agent sessions, or heavier-than-expected usage.

Plan structure

Larger plans are not just larger buckets of credits. They are designed for teams that need predictable spend, stronger controls, and support for production-scale automation.

Component	What it means
Plan commitment	A committed platform plan instead of purely month-to-month usage.
Pooled credits	A larger credit allocation across the contract, team, or workspace.
Custom rollover	Credits may roll over within the plan period, depending on the agreement.
Volume-based overage	Additional usage can be priced with negotiated tiers or committed usage.
Seats and access	Higher seat limits, role-based access, SSO, and SCIM.
Security and governance	Audit logs, retention controls, model access controls, and data controls.
Deployment and networking	Private networking or deployment options where required.
Support	Shared Slack or Teams support, onboarding, and solution engineering.
Procurement	Security review support, DPA, MSA, and compliance documentation.

The main difference is that self-serve plans are optimized for simple monthly usage, while larger plans are optimized for control, predictability, and scale.