Status
Current production surface
Expected signals
How to report an incident
Support workflow

Status

Current production surface

public docs: https://docs.secapi.ai
API: https://api.secapi.ai
hosted MCP: https://api.secapi.ai/mcp
API health: https://api.secapi.ai/healthz
API readiness: https://api.secapi.ai/readyz

Expected signals

every API response includes Request-Id
every API response includes traceparent
API keys are the primary authentication method for all plans; hosted MCP OAuth discovery is available through the WorkOS-backed .well-known endpoints. Enterprise OAuth/SSO is planned for 2026 Q3+.
billing, search, and event surfaces are live in production
launch-readiness and strict validation workflows are green for the shipped v3 surface
public site routes and API trust headers are part of the release posture, not afterthoughts
searchable filings and section history are release-gated for a 9-year public floor; deeper inventory remains provisional rather than an equal-density production guarantee

How to report an incident

include the failing endpoint
include the exact Request-Id
include the timestamp and org id if known
include whether the failure was API, webhook, stream, billing, or MCP related

Support workflow

first inspect https://api.secapi.ai/healthz
then inspect /v1/admin/orgs, /v1/admin/orgs/{org_id}, and request diagnostics
replay webhook deliveries when downstream delivery is the only failure mode