Our APIs perform complex, arcsecond-precision astrological mathematics in real-time. This requires significant computational power. This Fair Usage Policy is designed to prevent abusive query patterns, database scraping, and inefficient coding practices that degrade server performance for others.
1. Core FUP Parameters
Rate Limits (RPS)
Every subscription tier has a specific Requests Per Second (RPS) limit. You must throttle your application's outbound requests to stay within this limit. Bursting requests will trigger a 429 Too Many Requests error.
Concurrency
Opening too many simultaneous connections to our engine is prohibited. Batch processing must be queued sequentially on your server rather than executing concurrently.
Mandatory Caching
Data that does not change based on user input (like daily Panchang, planetary transits, or general horoscopes) MUST be cached on your server using Redis or Memcached.
2. Prohibited Abuse & Exploitations
No API Arbitrage or Wrapping
You may not create an "API Wrapper" to resell our endpoints to other developers. The data must be consumed by a front-end application, CRM, or software product serving end-users. Reselling raw API access is strictly prohibited.
Free-Tier Abuse & Trial Hopping
Creating multiple free-tier accounts, using temporary email generators, or utilizing proxy identities to circumvent API credit limits is a direct violation. All associated accounts and IPs will be permanently blacklisted.
Heavy Query Restraints
Astrological math is CPU-intensive. Looping through endpoints to calculate long-range data (e.g., 50 years of Muhurtas or daily transits for a decade) in rapid succession is forbidden. Such bulk operations require an Enterprise batch-processing license.
No Production Load Testing
Executing automated load tests, stress tests, or synthetic traffic generation (e.g., using JMeter, Locust, or Postman Runner) against our production API endpoints will result in immediate IP bans. Tests must be mocked locally on your end.
3. Examples of Fair vs. Unfair Usage
To avoid account suspension, please review these common implementation scenarios:
Scenario A: Fetching Daily Panchang or Transits
Your backend server runs a CRON job at 12:01 AM to fetch the Panchang data for the day from our API. You save this JSON response in your local database/cache. When 10,000 users visit your app's homepage that day, your app serves the data from your local cache.
You place the API call directly in your app's homepage load function. Every time a user opens the app, it hits our API for the exact same daily Panchang data. 10,000 app opens result in 10,000 redundant API calls. (Triggers instant rate-limit ban).
Scenario B: User Kundli / Report Generation
A real human user enters their Date, Time, and Place of birth into your form and clicks "Generate". Your server makes a single request to our API, renders the PDF/UI, and caches the result for that specific user session.
You write a Python/PHP loop that iterates through every day, hour, and minute from 1950 to 2025, sending millions of automated requests to our API in an attempt to scrape and clone our planetary calculation database. (Triggers permanent ban & legal action).
Scenario C: Handling High Traffic Spikes
Your marketing campaign goes viral. Instead of forwarding all requests to our API at once, you use a message broker (like RabbitMQ or AWS SQS) to queue the requests and process them sequentially, respecting your tier's RPS limits.
You blast 500 concurrent requests at our server. When our system returns a 429 Too Many Requests header, your application ignores the HTTP status code and instantly retries in an infinite loop, acting effectively as a DDoS attack. (Triggers automated IP block).
4. Enforcement & Penalties
Zero-Tolerance Enforcement Rule
Kundli.Click actively monitors API traffic via automated heuristic algorithms. You cannot exceed the Fair Usage Policy. If your account is found engaging in database scraping, ignoring rate limits, bypassing concurrency rules, or utilizing the API as a backend for an LLM/MCP server without an Enterprise MCP Plan/License, your account will be instantly suspended without prior warning.
Upon suspension for FUP violations, all remaining subscription validity, payments, account and API credits will be permanently forfeited. No refunds will be issued for accounts terminated due to abuse.
If you anticipate a legitimate traffic surge (e.g., a major app launch, TV feature, or New Year traffic), please contact our Enterprise team at least 96 hours in advance to temporarily lift limits or upgrade your infrastructure allocation.
Effective Date / Last Updated : August 25, 2026
Need to discuss a Custom Enterprise limit? Contact us here.