Pricing

Credits that map cleanly to product value.

Cerul prices the same public API surface used by direct clients, docs, and installable skills. Start with evaluation credits, then scale into predictable operator workflows.

Free

$0

for early evaluation

Best for trying the public API surface and validating early demo integrations.

  • 1,000 monthly credits
  • B-roll and knowledge search access
  • Single API key
  • Community support
Most Popular

Builder

$20

per month

For teams building agent workflows that need predictable usage and more active keys.

  • 10,000 monthly credits
  • 5 active API keys
  • Usage insights and search logs
  • Priority email support

Enterprise

Custom

volume and support matched

For production deployments with private ingestion pipelines, SLA expectations, and compliance review.

  • Custom credit limits and rate policies
  • Private indexing workflows
  • Dedicated onboarding and review
  • Enterprise security and billing coordination

Commercial stance

Open core. Operational leverage in the service.

The repository stays infrastructure-oriented and public-safe, while the hosted product compounds through indexing assets, tuning, and operator workflows.

FAQ

Why start with credits instead of raw request counts?

Credits let Cerul price different workloads fairly across b-roll search, knowledge retrieval, and optional answer generation without exposing all internal execution details.

Will agent skills use the same pricing model?

Yes. Skills are thin clients over the same HTTP API, so usage should map to the same credits and key model.

When does enterprise make sense?

Once a team needs private ingestion, multiple administrators, security review, or predictable throughput guarantees, the enterprise path becomes the cleaner fit.