SEBI Rules for Retail Algo Traders: What Changed in 2026
For years, retail traders used broker APIs with little oversight. SEBI’s circular of 4 February 2025, “Safer participation of retail investors in algorithmic trading”, changed that. The rollout was delayed and phased, and the framework became fully mandatory on 1 April 2026.
The timeline
- 30 November 2025: exchange registration of retail algo products to be complete.
- 3 January 2026: brokers take part in a full mock trading session.
- 5 January 2026: brokers that missed milestones cannot onboard new retail API clients.
- 1 April 2026: the framework binds every broker.
What it means for you
1. A static IP for API orders. Orders sent through a broker’s API must come from a fixed IP address you have whitelisted with that broker. Orders from any other address are rejected. Retail clients can provide one or two IPs, and the whitelisted address can change at most once a week.
2. Every algo order is traceable. Orders carry an exchange-issued identifier. Below 10 orders per second per exchange, you do not register your own strategy; above that, it must be registered with the exchange through your broker.
3. Brokers carry the responsibility. They supervise API access, keep audit trails and end API sessions daily, which is why you log in again every trading day.
4. Black-box strategies need extra licences. Providers who sell strategies whose logic you cannot see are expected to hold exchange empanelment and SEBI Research Analyst registration. Ask for the numbers.
5. Manual orders are untouched. Placing an order by hand in the broker’s app or website does not need a static IP.
Details vary by broker, so read your broker’s own notices.
What to do now
- Check whether your tool or script sends orders through an API. If it does, you need a static IP.
- Ask your broker where to whitelist it.
- Confirm that any third-party platform is an exchange-empanelled vendor.
- Keep the IP stable. A weekly change limit means a rushed swap can lock you out.
How Cirrus handles it
Cirrus gives each broker account its own dedicated static IP. You copy it from the app, paste it into your broker’s API settings once, and trade. Routing adds 5–30 ms per order. The static IP costs ₹0 extra on IPv6 brokers (Zerodha, Upstox, 5paisa, Groww, Dhan, Fyers, Alice Blue, Nubra, Kotak Neo) and ₹350 a month on IPv4 brokers, on top of the ₹499 account fee. See how static IP works.
At a glance
- SEBI’s retail algo framework became fully mandatory on 1 April 2026, after a circular dated 4 February 2025.
- API orders must come from a static IP your broker has whitelisted; the IP can change at most once a week.
- Below 10 orders per second per exchange, you do not register your own strategy.
- Black-box strategy providers are expected to hold empanelment and SEBI Research Analyst registration.
- Orders placed by hand in a broker’s app are not affected.
- On Cirrus the static IP is ₹0 on IPv6 brokers and ₹350 a month on IPv4 brokers.
FAQ
Do manual orders need a static IP?
No. The rule covers orders sent through a broker’s API.
Why do I log in every day?
Brokers end API sessions daily, so you sign in again each trading day.
How much delay does Cirrus’s static IP add?
5–30 ms per order, as measured by Cirrus. Your results depend on your broker and network.
Which brokers are IPv6 on Cirrus?
Zerodha, Upstox, 5paisa, Groww, Dhan, Fyers, Alice Blue, Nubra and Kotak Neo. Motilal Oswal, Tradejini, Angel One and ProfitMart use IPv4.
Disclaimer: Investments in securities markets are subject to market risks. Read all related documents carefully before investing. This article is for general information only and is not investment advice. Market timings may change, so please check the latest exchange circulars. Cirrus does not guarantee any outcome from automated execution.