The rules for using the Profin API: what's allowed, what your tier gets you, and what happens if either side needs to stop. Plain-language, matched to what the code actually enforces.
Last updated: 2026-07-11 (draft)
By signing up for an API key or otherwise calling the Profin API, you agree to these terms. If you don't agree, don't use the service. These terms apply to the hosted API and the documentation/marketing site you're reading now; they don't apply to the underlying SEC data itself, which is separately in the public domain (see Data source & methodology).
Profin is a REST API that normalizes public SEC structured filings -- income/balance/cash-flow statements, insider transactions (Forms 3/4/5), and institutional ownership (13F holdings and derived activity, Schedule 13D/13G) -- into one consistent JSON schema, plus derived fundamental metrics and peer rankings.
What the service is explicitly not:
POST /v1/signup issues one API key per email address; signing up again with an already-registered email is rejected. There is currently no email verification -- any syntactically valid email address is accepted. You're responsible for keeping your API key confidential; it's shown to you exactly once at signup (we store only a one-way hash) and there is no self-serve reissue flow today -- if you lose it, you'd need to sign up again with a different email.
Published tier limits, matched exactly to what auth/tiers.py enforces in the running API:
| Tier | Rate limit | Daily quota | Price |
|---|---|---|---|
| free | 5 req/sec | 1,000 req/day | Free — stays free after beta |
| basic | 20 req/sec | 25,000 req/day | Free during beta · planned $19/mo |
| pro | 100 req/sec | 250,000 req/day | Free during beta · planned $79/mo |
Pricing note (decided 2026-07-14, recorded in docs/product/PRICING.md): all tiers are free during the beta period. The planned prices when billing goes live are $19/mo for basic and $79/mo for pro; the free tier's limits are a standing promise and won't be reduced. There is no self-serve payment yet — every signup gets the free tier, and moving to basic/pro is a manual, admin-gated action. Keys issued during the beta keep working when billing starts; paid tiers will get explicit notice and a migration window before any charge, and prices will never change silently.
You may use the API for any lawful purpose consistent with these terms, including building applications, research, and internal tools. You may not:
caveats our API attaches to that data when you republish it.We do not claim ownership over the underlying SEC facts (they're public domain -- see methodology); this section is about fair use of our service and infrastructure, not a claim on public information.
The service is provided without any uptime, support-response, or data-accuracy SLA at launch. This is a small, early-stage operation, not an enterprise vendor. We aim to keep the API available and correct, and we monitor for outages, but we make no contractual guarantee about uptime, response time to support requests, or turnaround on bug fixes. If you need a contracted SLA, this service isn't the right fit yet -- talk to us before relying on it for anything mission-critical.
We may disable an API key for violating acceptable use, for abuse (e.g. quota-evasion via throwaway signups), or for operational reasons, with or without notice. Today that's a manual, admin-gated action on our side -- self-serve key revocation/rotation is not yet built (tracked as a launch-readiness item), so if you need your own key disabled, contact us.
You may stop using the service at any time. Since there is no self-serve billing yet, there is nothing to "cancel" -- simply stop calling the API. If self-serve payment ships later, this section will be updated with a real cancellation path.
The service and the data it serves are provided "as is" and "as available," without warranties of any kind, express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, or non-infringement. We do our best to normalize SEC filings accurately (see methodology for how, and for the honest limitations we already know about -- bank statement shapes, coverage floors, restatement handling), but errors can exist in any data pipeline, and you're responsible for validating anything you rely on for a material decision.
To the fullest extent permitted by law, we are not liable for any indirect, incidental, special, or consequential damages arising from your use of the service, including decisions made using the data. Nothing on this site or in this API is investment advice -- see the full disclaimer.
[Placeholder: governing law / jurisdiction clause -- needs an operator/legal decision before this is final.]
We'll update the date at the top of this page when these terms change. Material changes (e.g. real pricing replacing the "free during beta" note, or a new acceptable-use restriction) will be called out here, not buried in a silent edit.
Questions about these terms: [support contact -- placeholder, set a real address before launch], or open an issue on our GitHub repository [repo link -- placeholder].