Plans and limits
CiteProof has a free starting point and two paid plans. Prices, allowances and limits are served from the live plan catalog, so the pricing page and your account are always more current than any table copied into a guide.
Plans
| Plan | Price | Built for | Notes |
|---|---|---|---|
| Free | ₹0 | Trying CiteProof on a real research question. | Cited DeepSearch and Research Mode reports, one account, allowance resets automatically. |
| Pro | ₹999 per month | Students and individual researchers. | Higher allowances and export access. Billed monthly in Indian rupees. |
| Research Lab | ₹2,999 per month | Researchers with regular, heavier workloads. | Priority concurrency and the largest allowances. Billed monthly in Indian rupees. |
The pricing page renders the current catalog, including the exact monthly allowance for each mode. DeepSearch and Research Mode each have their own allowance; one does not consume the other.
Paid checkout is not open yet. Use the Free plan and send an upgrade request from the app or contact us; we will confirm the current price and allowance before anything is charged.
Allowances and resets
- Free accounts reset on the first day of each UTC calendar month.
- Paid subscriptions reset on the billing renewal date.
- Two separate pools. DeepSearch and Research Mode have their own allowance, concurrency limit and hourly start limit.
- Starts per hour protect shared search and model capacity. Hitting a concurrency limit waits; hitting an hourly limit means starting later.
Your remaining allowance and the reset date appear in the app and on the pricing page. A run that fails before completion should not consume a unit; if you think it did, contact support with the run id.
Bring your own API key
You can add your own model-provider API key on every plan. Runs that use your key do not consume the monthly allowance, so there is no monthly cap on those runs. Hourly start limits still apply; on the Free plan the limit is one run per hour.
The key is encrypted before it is stored. It is decrypted only in server memory while one of your runs needs it, it is never shown again after you save it (you see the last four characters), it is never written to logs and it is never sent to your browser. You can delete it at any time.
Never paste a provider key into a support email, a prompt or a shared document. Add it in account settings so it goes through the encrypted storage path.
Claude Science and MCP limits
CiteProof MCP is a separate local server. It has no model and no CiteProof account requirement. Review records stay in SQLite under CITEPROOF_MCP_HOME (default ~/.citeproof-mcp), and the only network calls are DOI checks to Crossref and doi.org.
- The server runs as a local stdio process. There is no hosted endpoint: the Claude Science path builds a bundle into the connector workspace, and the other paths start the same server through npx or the Claude Desktop extension.
- The local install keeps data on your machine and is the right choice for private or unpublished material. Nothing is uploaded to CiteProof.
- The server's input caps are limits on a single call, not a plan quota. They are listed in the MCP limits section.
What is not included
- Model-provider charges when you use your own key. Those are billed by the provider, not by CiteProof.
- Third-party search or registry availability. OpenAlex, Crossref and the other sources have their own rate limits and outages.
- GST treatment. It is still to be confirmed and will be shown at checkout before payment.
- Any guarantee of a scientific conclusion. CiteProof assists a review; it does not certify one.
Billing questions
Start with the pricing page for the current catalog and the FAQ, and the refund policy for cancellation and refunds. For anything account-specific, contact support with the email on the account and the relevant run or invoice id. Do not send API keys or full card numbers.