specification: API Commons Plans
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/Plans
provider: Corva AI
providerId: corva-ai
generated: '2026-09-05'
modified: '2026-09-05'
method: searched
source: >-
  https://www.corva.ai/ (site + sitemap.xml, 243 URLs, no pricing page),
  https://www.corva.ai/pricing (404), https://www.corva.ai/plans (404), and the vendor's own
  AWS Marketplace listing https://aws.amazon.com/marketplace/pp/prodview-fkatffbptqdn4
supersedes: >-
  REPLACES the scaffold written by the 2026-05-04 bulk sweep (method: generated), which invented
  three tiers — "Free" at 1,000 requests/month, "Professional" at 100,000/month with a TBD overage
  price, and "Enterprise" — together with per-tier rate limits, SLA targets, webhook subscriptions
  and sandbox access. Corva publishes NONE of that. It advertised a free tier for a product that
  has no self-serve signup at all. Removed rather than corrected. See roadmap#35.

plan_count: 0
public_pricing: false
pricing_model: enterprise / contact-sales

detail: >-
  Corva publishes no pricing of any kind. There is no pricing page (/pricing and /plans both 404),
  no plan or tier is named anywhere in the 243-URL sitemap, there is no free tier, no trial, and no
  self-serve signup — the site's conversion path is "Schedule a Demo" and "Contact". The AWS
  Marketplace listing, which is Corva's own transactable channel, states plainly: "Pricing is based
  on your specific requirements and eligibility. To get a custom quote for your needs, request a
  private offer." It publishes no pricing dimensions, no unit prices and no contract durations.

evidence:
  - url: https://www.corva.ai/pricing
    status: 404
  - url: https://www.corva.ai/plans
    status: 404
  - url: https://aws.amazon.com/marketplace/pp/prodview-fkatffbptqdn4
    status: 200
    finding: Custom pricing only; private offer required.
  - url: https://www.corva.ai/schedule-a-demo
    status: 200
    finding: The actual entry point — a sales-qualification form, not a signup.

api_access_gate: >-
  The gate is tighter than pricing alone. Corva's own authentication documentation states that
  API-key creation is NOT enabled by default and that most customer users lack permission to create
  or approve keys, directing them to "contact your Corva representative". So even an existing
  paying customer may not be able to self-provision API credentials. There is no developer tier and
  no public sandbox.
  source: https://dc-docs.corva.ai/docs/API/authentication

channels:
  - name: Direct / enterprise agreement
    url: https://www.corva.ai/contact
  - name: AWS Marketplace
    url: https://aws.amazon.com/marketplace/pp/prodview-fkatffbptqdn4
    pricing: private offer

plans: []
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com