Skip to main content
Pricing

Usage-based plans that scale with your traffic.

Choose a monthly request allowance that fits your current traffic. Move to a larger tier as your evaluated volume grows.

Botless plans

Basic

1M

requests per month

For teams evaluating traffic quality in a focused production workflow.

Usage-based pricing
Get a quote
  • Up to 1 million evaluated requests
  • One production integration
  • Traffic classification and findings
  • Monitoring and decision modes
  • Email support

Enterprise

Custom

monthly request volume

For platforms with higher volume or complex partner structures.

Usage-based pricing
Get a quote
  • Custom evaluated request allowance
  • Multiple environments and integrations
  • Advanced policy requirements
  • Data export options
  • Technical account support

Request allowances reset monthly. Final features, overage handling, limits, and commercial terms are confirmed in your proposal.

A useful quote

Bring three details to the conversation.

A rough range is enough to start. We will clarify assumptions before proposing a scope.

01

Daily or monthly request volume

02

Where the verdict enters your traffic flow

03

The sources, placements, or partners you need to segment

Pricing questions

The commercial model should be as understandable as the product decision.

Traffic volume and integration scope can vary substantially. A scoped quote avoids presenting a price that does not match the capacity, support, or workflow required.

Yes. A monitoring phase is the recommended way to compare classifications with your own outcomes before introducing active filtering.

The proposal will define the billable event, expected volume, and any limits. Ask us to model unusual spikes or seasonal traffic when discussing scope.

A limited evaluation may be included in an agreed rollout. Its duration, traffic allowance, success criteria, and support are confirmed before testing begins.