Skip to main content

​
Plans

  • sandbox_grant
    • evaluation and low-volume testing
  • payg
    • default self-serve paid path with per-unit pricing
  • personal
    • self-serve API, CLI, and MCP workflows
  • team
    • higher-throughput shared usage
  • commercial
    • custom commercial handling and higher-volume deployment

​
Redistribution posture

  • SEC API is sold as a provenance-rich derived-data and workflow product.
  • Raw SEC rehosting or unrestricted redistribution is not the default product posture.
  • Commercial discussions are where redistribution rights, dedicated infrastructure, and custom support terms belong.

​
Commercial boundaries

  • compare workflows, artifacts, webhooks, and streams are paid features
  • usage enforcement is visible through SECAPI-Plan-Key, SECAPI-Meter-Class, and SECAPI-Billing-Status
  • billing incidents should always include a Request-Id and the current /v1/billing snapshot

​
WorkOS and SSO posture

  • API keys are the primary machine-auth method for all plans
  • WorkOS powers dashboard login and enterprise SSO
  • hosted MCP uses x-api-key for server-to-server access and exposes WorkOS discovery metadata where clients need it
  • contact the SEC API team to coordinate enterprise SSO requirements

​
Escalation path

  • admin and platform incidents: use the support bundle flow
  • billing and entitlement issues: use the Stripe billing runbook
  • enterprise/commercial questions: reference the current plan catalog and account posture docs