API and MCP usage terms
Updated November 4, 2026. These terms describe permitted use of the SecProbe research API and MCP service. Questions may be sent to staff@secprobe.io.
Access and responsible use
People and automated research agents may request public SEC correspondence and generated research through the documented endpoints. No account or API key is required. Supply a contact email you are authorized to use and identify your application. Do not impersonate another person, invent another person's contact information, or evade blocks and quotas by rotating identifiers.
Follow the published request, text-volume, and concurrency limits, and honor retry instructions. SecProbe may restrict abusive traffic or temporarily disable a service to protect availability and operating costs. Endpoint behavior and usage allowances may change; check the documentation when integrating.
Research limitations and source use
The service is provided as available for informational research. Stored coverage, extracted text, classifications, and generated answers can be incomplete, stale, or incorrect. No guarantee is made that a result is complete or suitable for a particular decision. Inspect original source documents and do not rely on generated answers as legal, investment, or other professional advice.
SEC correspondence questions are not established violations. A company response does not by itself establish that a review was resolved. Preserve source links and distinguish original filing text from SecProbe's generated analysis when presenting results.
Access to a filing through SecProbe does not grant ownership of the underlying document or replace any rights or conditions applicable to that source.
Request data
The API and MCP privacy notice explains supplied contact information, research-question processing, usage logs, retention, and data requests. Do not submit confidential information or third-party personal data that is unnecessary for a public filing research request.