Documentation

Plans, Credits, And Billing

Choose between subscriptions and pay-as-you-go credits based on scan volume and workflow depth.

Who This Topic Is For

Buyers and operators matching cost model to security workflow needs.

Before You Start

Use this checklist to make sure the workflow guidance applies cleanly to your current task.

  • Expected monthly scan volume is roughly estimated.
  • You know whether recurring credits or flexible purchases fit your workflow.

Step-By-Step Guidance

Follow these steps in order for a reliable and repeatable outcome.

  1. Map usage pattern to plan type.

    Use subscriptions for predictable recurring workflows and credit packs for flexible or supplemental usage.

  2. Compare included capabilities.

    Review feature and workflow differences across tiers before selecting where automation or team features are required.

  3. Account for rollover and non-expiry behavior.

    Use rollover limits on subscriptions and non-expiring purchased credits to avoid unnecessary workflow interruption.

  4. Understand API spec trial and fixed-credit usage.

    The first API spec scan is available as a one-time free trial per user. After that, each API spec scan uses 18 credits.

    Headless crawl preview remains free, so teams can separate lightweight previewing from billable imported-spec review.

Validation Checklist

Use this checklist to confirm the workflow was completed correctly.

  • Selected model matches forecasted monthly usage.
  • Required team or automation features are available at chosen tier.
  • Credit lifecycle behavior is understood before purchase.
  • Users understand when API spec trial usage ends and when 18-credit API spec runs begin.

Common Problems And Fixes

If something does not match expectation, check these common failure modes first.

Common failure mode

Choosing by price alone

Plan selection should combine cost, required features, and scan cadence rather than headline monthly price only.

Common failure mode

Ignoring rollover limits

Track recurring usage against rollover constraints so credit planning remains predictable.

Common failure mode

Expecting API spec scanning to follow website depth pricing

API spec scanning is billed as its own workflow. The first run is a one-time free trial, and later runs use 18 credits each rather than reusing Quick, Standard, Deep, or Comprehensive depth pricing.

Plans, Credits, And Billing FAQs

Yes. Pay-as-you-go credit packs can be purchased and used alongside active subscriptions.

Next Recommended Action

Continue to the best next page based on where you are in your workflow.