Pricing

Simple, transparent pricing

One credit per model call. No seat tax, no agent caps you'll actually hit.

Most Popular
Team
$99 / month
For teams collaborating on AI agents
  • 20,000 credits per month
  • 5 builders
  • Slack, Discord & Microsoft Teams
  • MCP actions & tool integrations
  • Personal agents & multi-agent selection
Business
$399 / month
For companies deploying AI agents across teams
  • 100,000 credits per month
  • 10 builders
  • All channels + HubSpot & Zendesk
  • Bring your own LLM key (BYOK)
  • CRM integrations (HubSpot, Zendesk)
Security & compliance
  • SOC 2 Type II report on request
  • Audit log of every prompt, tool call, and reply
  • Per-user auth on shared agents
  • SAML/SSO
Enterprise
Custom Pricing
Built for large organizations scaling their AI workforce
  • Custom credits
  • Custom builders
  • Custom interactors
  • Priority support SLAs
  • Custom implementation
Security & compliance
  • Everything in Business
  • SCIM provisioning
  • HIPAA Compliance (BAA on request)
  • Signed DPA

Available to eligible Enterprise customers with a BAA and supported configuration. External services need separate review. View requirements

Contact Us
Credits

Credits track the work, not the seat. Heavier tasks cost more.

A credit reflects the model work a task actually uses — quick questions sip a few, deep reports draw hundreds.

Quick answers
~5 credits
  • • Knowledge-base Q&A ("What's our refund policy?")
  • • Summary of a Slack thread
  • • No tool calls
Workflows
20 – 50 credits
  • • CRM lookupdrafted follow-up
  • • Calendar check + scheduling proposal
  • • A few tool calls
Deep work
300 – 1,500 credits
  • • Multi-page research or competitive analysis
  • • Cross-source report with citations
  • • Long-context synthesis

One unit, every model

Whatever model an agent runs, its usage lands in the same unit — no per-model token math to compare or forecast.

Provider chosen per agent

Claude, GPT, or Gemini per agent; the credit rate follows the model you pick.

Bring your own key

On Business and Enterprise, pay your provider directly and credits become a thin processing fee.

Teams already running Runbear

SOC 2 Type II
in production
Per-user auth
on shared agents
Cancel anytime
no annual lock-in
HIPAA Compliance (BAA on request)
Eligible Enterprise customers
FAQ

Frequently asked questions

Everything you need to know about the product and billing.

Credits are the currency agents use for billing. Credit consumption depends on:

  • Task complexity: Simple Q&A using knowledge bases consumes fewer credits, while complex tasks using tool integrations (MCP) consume more
  • AI model: You choose the provider and model per agent. A more capable model improves accuracy and costs more credits per call.

Monthly plan credits reset each billing cycle. Bonus credits (e.g. from a referral or onboarding promo) never expire — they sit in your account until used.

Your agents pause until you top up. You have two options:

  • Enable pay-as-you-go: automatically purchase additional credits beyond your plan's included amount, billed at the same rate.
  • Upgrade your plan: bump up to a plan with more monthly credits.

We send email notifications as your balance gets low so you can avoid interruptions.

Runbear supports HIPAA compliance for eligible Enterprise customers with a BAA and supported configuration. Before processing PHI, confirm the agreement, organization access, and each agent's configuration with Runbear. Review connected channels, knowledge sources, model providers, and tools separately for your workflow and any required agreements. With your own API key (BYOK), you are responsible for the provider BAA. A supported Runbear configuration does not automatically cover every connected service.

Discuss HIPAA compliance with SnowRead the HIPAA guide

Contact the Enterprise team to request a Business Associate Agreement (BAA) and review your intended workflow. A BAA is on request for eligible Enterprise customers; it is not included automatically with signup. Confirm the agreement and supported configuration for each agent before processing PHI.

Discuss HIPAA compliance with SnowRequest a BAA

No, Runbear only accesses messages necessary for running LLM applications. For instance, it reads messages in a thread where users ask for a response by mentioning @Runbear. It does not access any other messages.

Runbear encrypts data at rest and in transit and provides access controls. Review the HIPAA guide and confirm the applicable data handling and retention terms for your qualifying workflow with the Enterprise team before processing PHI.

No. Runbear does not use your data to train any AI models, and we never sell or share your data with third parties. Your data is used solely to operate the service — processing messages through LLM providers and returning responses to your communication channels. The LLM providers we integrate with (such as OpenAI and Anthropic) also do not use API data for model training.

Compare features

Start free. Upgrade when your team's hooked.

Bring a real workflow. We'll wire it live, ship it to your Slack by end of call.

Book a Demo