​

Status

​

Current Endpoints

• public docs: https://docs.secapi.ai
• public status: https://status.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 documented .well-known endpoints.
• billing, search, and event APIs are live in production
• production checks are passing for the public API
• public site routes and API trust headers are part of the production contract
• searchable filings and section history support 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

​

First Checks

• first inspect https://status.secapi.ai
• then inspect https://api.secapi.ai/healthz
• then inspect https://api.secapi.ai/readyz
• if an API call fails, include the Request-Id when contacting support
• if a webhook delivery fails, include the event id, delivery id, destination status, and timestamp