specification: API Commons Plans
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/Plans
provider: Crawlee
providerId: crawlee
generated: '2026-09-07'
created: '2026-05-04'
modified: '2026-09-07'
method: searched
source: >-
  https://crawlee.dev/ (200), https://crawlee.dev/js (200), https://crawlee.dev/python (200),
  https://github.com/apify/crawlee/blob/master/LICENSE.md (200),
  https://registry.npmjs.org/crawlee (200, license Apache-2.0)
plan_count: 0
tags:
  - Apache 2.0
  - Apify
  - Open Source
  - Scraping
  - Web
description: >-
  Crawlee publishes no plans and no pricing, and that is the correct and complete finding.
  It is an Apache-2.0 open-source library distributed free through npm and PyPI. There is
  no account, no key, no metered surface and no paid tier, because nothing is hosted on the
  consumer's behalf — the code runs in the consumer's own process on infrastructure they
  already pay for.
plans: []
note: >-
  SUPERSEDES A FABRICATED ARTIFACT. Until this pass, this file carried three invented
  tiers — "crawlee-free" at 1,000 requests/month, "crawlee-pro" at 100,000/month with a TBD
  overage price, and "crawlee-enterprise" with negotiated volume and a contractual SLA —
  written by the 2026-05-04 bulk sweep and self-declared in its own description as
  "scaffold defaults". None of it was ever published by Crawlee: there is no request quota
  to meter because there is no request to make. The scaffold has been removed rather than
  annotated, because a plan a provider never offered is a false claim made on their behalf.
related:
  commercial_context: >-
    Apify, which maintains Crawlee, does sell a hosted platform with paid plans at
    apify.com. Those plans belong to the Apify provider record and are deliberately not
    mirrored here — Crawlee runs standalone with no Apify account and no Apify dependency.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com