Skip to content

Legal

API Usage Policy

Effective 19 May 2026 · Last updated 19 May 2026

This API Usage Policy governs your use of any application programming interface, data export, webhook, automation hook, or programmatic access mechanism offered by PAI (paitrade.in) — including REST endpoints under /api/, data feeds, scheduled exports, and any user-controlled automation utilities. It supplements the Terms of Service, Disclaimer, and Risk Disclosure — read all three together.

1. Scope & positioning

PAI's API surface is an educational and utility tool, not a managed execution service. The API returns market-structure research data (demand zones, scoring metrics, LTP snapshots, computed risk/reward inputs, etc.) for you to study or feed into your own downstream tools.

The API does NOT:

  • place orders at any broker on your behalf
  • act as a "signal subscription" or "trade copier"
  • execute discretionary trades — you alone control every order
  • guarantee any output is accurate, complete, timely, or profitable to act on

2. Access credentials are your responsibility

Where the API requires authentication, you are solely responsible for:

  • generating, storing, and rotating any API key, bearer token, or access secret issued to you
  • scoping which scripts, servers, devices, or third-party tools hold the credential
  • revoking compromised credentials immediately via the account portal
  • any broker access token, TOTP secret, client ID, or third-party credential you choose to configure with a PAI-provided utility — these never reach PAI servers, but their security is wholly your concern

If you suspect a credential has been compromised, revoke it immediately and email [email protected]. PAI is not liable for any usage occurring under your credential prior to revocation.

3. Rate limits & fair use

PAI enforces rate limits to keep the Service responsive for all users. Limits are subject to change based on infrastructure capacity and your subscription tier. You agree to:

  • respect documented rate-limit headers and back-off responses
  • avoid polling patterns that exceed reasonable consumption for educational use (for example, fetching the entire dataset every second)
  • not run automated scrapers, bulk-export crawlers, or scheduled jobs that exhaust shared resources
  • cache data on your side rather than re-fetching the same payload repeatedly

Persistent abuse of rate limits, or any usage pattern that materially degrades the Service for other users, may result in temporary throttling, IP-level blocks, or account suspension without refund.

4. Third-party dependencies

The API depends on third-party infrastructure (market data vendors, NSE / exchange feeds, Cloudflare, Razorpay, hosting providers, and others). When a third-party dependency is degraded, delayed, or unavailable, the API may return stale, incomplete, or error responses. PAI does not guarantee third-party uptime and is not liable for any consequence of third-party failure.

5. Order execution delay & slippage

If you use the API to feed an automation that places orders at your own broker under your own credentials, you accept all execution-timing risk. The chain from PAI's response → your script → your broker's order gateway → the exchange involves multiple network hops, each adding latency. Slippage, missed fills, partial fills, late cancellations, and rejected orders are your risk alone. PAI is not party to any order and is not liable for execution outcomes.

6. No discretionary trading via PAI's surface

PAI does not place discretionary trades on behalf of users. All orders are initiated, authorized, and controlled by the user through their own broker account. The API is a research/utility surface — it returns data; you decide what to do with it. Any automation you build on top of the API is your own software acting under your own authority.

7. Data accuracy & "as is" provision

All API responses are provided "AS IS" and "AS AVAILABLE" without warranty of accuracy, completeness, or fitness for any particular purpose — including trading. Zone scores, freshness ratings, MTF alignment flags, prices, and any computed metric are educational/research outputs. Verify independently before relying on any value for a trading decision.

8. Acceptable use

When using any PAI API surface, you agree NOT to:

  • resell, sublicense, or commercially redistribute API responses to third parties
  • use the API to operate a tipster service, signal channel, or "calls" group
  • scrape or harvest data beyond your documented rate limit
  • reverse-engineer the scoring algorithms via brute-force probing of the API
  • use the API to build a product that misrepresents PAI as an investment adviser or research analyst
  • circumvent tier-based feature gates via API abuse
  • store, log, or transmit broker credentials or TOTP secrets through PAI servers

9. Service availability & suspension

We may suspend, throttle, or modify the API at any time — including in response to regulatory developments, infrastructure incidents, security findings, or abuse. Where reasonably practicable we will provide advance notice via email to active API users and via the status page. We are not liable for losses arising from such changes.

10. Logging & abuse monitoring

We retain server-side request logs (IP, timestamp, endpoint, response code, latency) for operational, security, and abuse-detection purposes. We do not log request bodies that would contain personal information beyond what is necessary to operate the API. Log retention is governed by our Privacy Policy and DPDP-Act obligations.

11. No SLA at standard tiers

Standard subscription tiers (Free / Pro / Elite) do not include a contractual service-level agreement for API availability or response time. The status page shows operational health on a best-effort basis. If a custom SLA is needed for institutional or research use, contact [email protected].

12. Liability cap & indemnity

Your use of the API is subject to the limitation-of-liability and indemnification clauses of the Terms of Service. Aggregate liability for any claim arising from API use will not exceed the amount you paid PAI in the six (6) months preceding the claim. Indirect, consequential, and trading-loss damages are excluded in full.

13. Changes to this Policy

We may update this API Usage Policy at any time. Material changes are announced on the changelog and on the status page. Continued use of the API after the effective date constitutes acceptance.

14. Contact

API support, abuse reports, and credential-compromise notifications: [email protected].