Skip to main content

​
Plans

  • sandbox_grant: renewable monthly free allowance for low-volume testing
  • payg: self-serve metered usage with prepaid credits
  • personal: Pro self-serve subscription for one seat, included credits, and discounted API/CLI/MCP/add-in usage
  • team: self-serve subscription for shared organization usage, pooled included credits, five included seats, and ten included API keys
  • commercial: contract plan for redistribution rights, higher-volume commitments, an SLA, Bulk Factor Export, custom factor models, priority support, and twenty-five included API keys

​
Redistribution posture

SEC API separates public SEC source records from SecAPI’s indexing, normalization, extraction, factor, entity-resolution, and enrichment layers. Self-serve plans are for evaluation and internal use. They do not allow you to operate a public mirror, replay layer, substitute dataset, standalone data feed, bulk export, or resale service built from SEC API outputs. Commercial is the plan family for external-facing product use. Use a commercial agreement before redistributing SEC API-derived output, embedding it in a customer-facing product, white-labeling it, reselling it, or using Bulk Factor Export. Do not use normalized or enriched SEC API outputs to train, fine-tune, or improve AI or machine-learning models without written permission.

​
Fund-letters dataset terms

Fund-letters content — letter records, extracted theses and narratives, and served letter documents — is licensed for use inside your own applications and research workflows. Bulk redistribution or resale of the corpus or of the extracted thesis dataset is not permitted on any self-serve plan, and per-plan daily quotas on the fund-letter meters enforce that boundary operationally. Letter documents are additionally rights-tiered by their distribution field: SEC-filed and fund-published letters serve in full, while third-party-sourced letters serve metadata, theses, and excerpt-length quotes with a link to the original source. Redistribution of fund-letters output in an external-facing product requires a commercial agreement, and document-level rights follow the tier of each letter regardless of plan.

​
Commercial boundaries

  • The runtime exposes the effective plan and billing state through GET /v1/billing, GET /v1/billing/rates, GET /v1/limits, and response headers.
  • Billable responses can include billing and metering headers such as SECAPI-Meter-Class, SECAPI-Plan-Key, SECAPI-Billing-State, SECAPI-Billing-Status, SECAPI-Free-Grant-Remaining, SECAPI-Token-Count, and SECAPI-Estimated-Cost.
  • Pay As You Go uses prepaid credits. Credit top-ups, auto-top-up, refunds, saved payment methods, and billing portal sessions are billing-control actions.
  • Pro, Team, and Commercial use the usage-credit ledger for included credits, discounted overages, and budget gates.
  • Commercial starts from the public contract floor in the pricing catalog, then final scope, rights, and billing terms are set in the commercial agreement.

​
Auth and billing permissions

  • Use the x-api-key header for REST, SDK, CLI, and server-to-server MCP traffic. Do not send SEC API keys as Authorization: Bearer.
  • Dashboard billing changes use a WorkOS browser-session bearer token, not an API key.
  • Billing mutations require billing:manage, admin:operator, or *. This covers checkout, billing portal creation, PAYG activation, starter-grant reset, credit top-ups, refunds, auto-top-up configuration, saved payment methods, and budget updates.
  • Paid billing and payment setup require acceptance of the current Terms of Service and Privacy Policy.
  • GET /v1/billing, GET /v1/limits, and POST /v1/billing/quote are safe preflight calls for an authenticated organization. Agents should call them before repeated or expensive workflows.

​
Choosing Commercial

Choose Commercial when your workflow crosses any of these boundaries:
  • customers, partners, or public users see SEC API-derived output
  • your product redistributes, embeds, white-labels, or resells SEC API-derived data
  • you need Bulk Factor Export, custom factor models, a contracted SLA, or priority support
  • your expected usage needs a negotiated rate card or committed-volume terms
  • your legal, procurement, or security process requires a signed agreement
For internal research, private tools, notebooks, and agent workflows that do not redistribute output, start with Pay As You Go, Pro, or Team and use GET /v1/billing plus POST /v1/billing/quote to size usage before scaling.