DOCUMENTATION / USAGE & RATE LIMITS

Usage & rate limits

OpenAPI 3.1 ↗

Inspect CompanyProof usage, plan credits and request rate limits before building a production integration. Handle allowance and rate-limit responses.

BASE URLhttps://companyproof.ai/v2JSON · Bearer authentication

RATE AND USAGE LIMITS

Predictable allowances. No automatic overage.

PLANINCLUDED CLAIM CREDITSREQUESTS / MINUTEMONITORING
Registered · unpaid010Not included
Live evaluation · when granted250 total30Until evaluation expiry
Starter · US$99 / month250 / month30Included
Production5,000 / month60Included
Enterprise50,000 / month120Included

Each accepted verification claim consumes one credit, and each monitored claim recheck consumes one more. An accepted company search, profile retrieval or adaptive intelligence request consumes one credit. Requests stop at the plan allowance; CompanyProof does not create automatic overage charges.

X-RateLimit-Limit

Maximum requests allowed for the account in the shared 60-second window.

X-RateLimit-Remaining

Requests remaining in that window.

X-RateLimit-Reset

Unix timestamp when the rate window resets.

X-Usage-Limit

Claim-credit allowance for the active usage period.

X-Usage-Remaining

Claim credits remaining in the active usage period.

X-Usage-Reset

Unix timestamp when the active allowance resets: the Stripe period end for paid plans, UTC month-end for test, or evaluation expiry.

X-Request-Id

Request correlation identifier. For verification writes it currently equals proof_id; applications should still read the body field as proof identity.

CompanyProof REST 429 responses include Retry-After. The account-wide per-minute counter is shared by every API key and all REST and MCP tool calls for that account, so creating more keys does not multiply throughput. MCP tool failures are returned inside result.isError. Monitoring that reaches the allowance pauses until the active usage period resets. Upgrades and downgrades within the same Stripe period preserve credits already used.