ENTRY № 18 · STATUTORY READING · SEBI RETAIL ALGO
PUBLISHED 2026-05-09 · ~12-MIN READ · WARRANT COMPLIANCE

SEBI Retail Algorithmic Trading Framework, line by line.

One six-page circular of 4 February 2025. One three-page extension circular of 30 September 2025. Together they pull retail algorithmic trading inside a perimeter of broker-as-principal, exchange-empanelled algo providers, and exchange-issued unique identifiers on every algo order. Universal application to all stock brokers from 1 April 2026. The framework is operational in May 2026.

Warrant is regulator-grade evidence infrastructure for AI agents in regulated industries: drop an agent's execution trace, get a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.

CIRCULAR
2025/0000013
SEBI/HO/MIRSD/MIRSD-PoD/P/CIR · extended 2025/132 · brokers, exchanges, algo providers.
IN FORCE
2026-04-01
Universal applicability to all stock brokers. Glide path opened 2025-10-01 for ready brokers.
SCOPE
API algo· retail
Every algo order through broker API, every broker-empanelled vendor, every exchange-registered algo.
01 · § 1 · THE FRAMEWORK

The framework in one paragraph.

There has been an increasing demand for algo trading by retail investors. In order to facilitate safer participation of retail investors in algo trading, with Stock Brokers (hereinafter referred to as Brokers) and Stock Exchanges (hereinafter referred to as Exchanges) playing the required roles in risk management, it has been decided to review and refine the existing regulatory framework to ensure proper checks and balances, to safeguard investor interest as well as integrity of the market. SEBI · circular 2025/0000013 · paragraph 3 · 4 February 2025

SEBI did three things in this paragraph that the older 2012 framework on broad guidelines for algorithmic trading did not. It named retail demand as the trigger. It named brokers and exchanges, in that order, as the load-bearing actors. And it conceded the existing framework needed review, not extension. The 2012 circular CIR/MRD/DP/09/2012 covered institutional algo trading via direct market access. The 2025 circular covers a different population entirely: retail investors using broker APIs, with third-party algo providers in the loop.

The distinction matters because retail algo trading exposes a different risk surface. An institutional desk has compliance, controls, and a regulated balance sheet. A retail trader using an algo bought from a fintech vendor has none of those. The framework solves the problem by making the broker the principal and the algo provider the agent. The agency relationship is not a metaphor in the circular. It is the operative legal device that pulls every algo order back inside a SEBI-supervised perimeter.

"Brokers shall be the principal while any algo provider or fintech/vendor shall act as its agent, while using the API provided by the broker."SEBI · circular 2025/0000013 · paragraph 5(I)(a)

The four sub-clauses of paragraph 5(I) of the 4 February 2025 circular, paraphrased and indexed:

5(I)(a)
Brokers as principal, algo providers as agents, using the broker-issued API. IMPLICATION · the broker carries vicarious liability for algo provider conduct.
5(I)(b)
All algo orders flowing through the broker API are tagged with a unique identifier provided by the stock exchange. IMPLICATION · every order is traceable end-to-end · investor → broker → algo → exchange.
5(I)(c)
Self-developed retail algos cross a specified orders-per-second threshold register with the exchange through the broker, usable only by family. IMPLICATION · the threshold is set by the Broker's Industry Standards Forum, not SEBI directly.
5(I)(d)
No open APIs. Unique vendor-client API key, static-IP whitelist, OAuth-only authentication, two-factor, empanelled providers only. IMPLICATION · this is where the framework stops being a policy and starts being a system specification.
02 · REGISTRATION QUESTION

Registration, pre-approval, or self-attestation.

The single most-asked question on this circular in May 2026 is whether SEBI requires pre-approval, registration, or self-attestation for retail algos. The answer is two answers, because the framework operates on two different registers at once.

Algos themselves are pre-approved. Paragraph 5(II)(a) reads: The facility of algo trading shall be provided by the broker only after obtaining requisite permission of the stock exchange for each algo. The verb is obtaining requisite permission, not notifying. Each algo. Not each algo provider. Not each strategy family. Each algo. Paragraph 5(II)(b) extends the requirement to modifications: the broker shall seek approval from the Exchange for any modification or change to the approved algos. A version bump that changes the logic is a re-approval event.

Algo providers, by contrast, are empanelled, not registered with SEBI. Paragraph 5(III)(a) reads: While algo providers shall not be regulated by SEBI, for better oversight, any algo provider, providing the facility to place algo orders with Brokers through API, shall require to be empaneled with Exchanges in a manner as stipulated by Exchanges. Paragraph 5(III)(b) leaves the empanelment criteria to the exchanges. Paragraph 5(III)(c) puts the broker on the hook for due diligence before onboarding any empanelled provider.

The third register sits inside paragraph 5(V). Black-box algos, where the logic is not known to the user and is not replicable, attach an extra obligation: the algo provider shall register as a Research Analyst under the SEBI (Research Analysts) Regulations, 2014, and shall maintain a detailed research report for each such algo. A change in the logic re-registers the algo as a fresh algo with a fresh research report. White-box, replicable execution algos do not pull in the Research Analyst registration.

So the layered answer to the registration question · algo · exchange permission per algo. Algo provider · exchange empanelment plus broker due diligence. Black-box algo provider · SEBI Research Analyst registration on top. Self-attestation by the broker is not a permitted route at any of the three layers.

03 · SEPTEMBER 2025 EXTENSION

The September 2025 extension circular.

The original 4 February 2025 circular set two implementation dates in paragraph 7. Implementation standards by 1 April 2025, formulated by the Broker's Industry Standards Forum under the aegis of the stock exchanges and in consultation with SEBI. Provisions of the circular applicable from 1 August 2025.

Neither date held. SEBI extended the implementation-standards date in April 2025. The exchanges issued the detailed operational modalities only on 22 July 2025. SEBI then extended the applicability date to 1 October 2025 by a further circular dated 29 July 2025. In the second fortnight of September 2025, the exchanges issued additional clarifications and modifications to the operational modalities. The 30 September 2025 circular records the path and resets the clock.

In order to ensure smooth implementation of the framework, SEBI has been engaging with exchanges, broker associations and algo vendors. During the discussion, it was informed that majority of the stock brokers require more time to carry out the necessary changes in their systems on the basis of clarifications/modifications specified in operational modalities. SEBI · circular 2025/132 · paragraph 3 · 30 September 2025

Paragraph 4 of the September 2025 circular sets a glide path. Paragraph 8 sets the universal applicability date. Verbatim: W.e.f. April 01, 2026, algo framework specified in circular dated February 04, 2025 along with implementation standards and detailed operational modalities (issued by exchanges) will be applicable for all stock brokers.

Three milestones inside the glide path, all inside paragraph 4 of the September 2025 circular:

31OCT
MILESTONE 1 · 2025
Retail algo product through API (in-house and through vendors) and at least one algo strategy applied for registration with the exchange.
30NOV
MILESTONE 2 · 2025
Registration of retail algo products through API and few algo strategies for retail algo with the exchange completed.
03JAN
MILESTONE 3 · 2026
Stock broker participates in at least one mock session with the new functionality complete in all aspects. Evidence of participation provided to the exchange.
05JAN
SANCTION GATE · 2026
Brokers who fail to adhere to the milestones shall be barred from onboarding new retail clients for API-based algo trading from this date. Paragraph 5 of the September 2025 circular.

The reason SEBI extended is recorded inside the circular itself, not inferred. It is system-readiness, not policy-disagreement. Brokers needed time to implement the operational modalities the exchanges had only finalised in late September 2025. SEBI did not soften any obligation in the underlying February circular. It softened the calendar.

04 · DOCUMENTATION

Documentation and audit trail.

The 4 February 2025 circular does not centralise the documentation requirement. It distributes it across paragraphs 5(I)(b), 5(II)(b), 5(III)(c), and 5(V)(a)(ii). Read together, three categories of evidence become mandatory.

Per-order. Paragraph 5(I)(b) requires the unique exchange-issued identifier on every algo order flowing through the API. Paragraph 5(II)(b) repeats and adds the audit trail purpose: All algo orders shall be tagged with a unique identifier provided by the Exchange in order to establish audit trail. The order ledger therefore must carry the algo identifier alongside the order identifier. A trade blotter without the algo identifier does not satisfy the framework.

Per-algo. Each algo carries an exchange permission. Each modification is approved before it goes live. The broker's algo register therefore needs three fields per algo: the exchange permission reference, the version-controlled logic record, and the modification-approval reference. Paragraph 5(II)(b) is explicit: the broker shall seek approval from the Exchange for any modification or change to the approved algos.

Per-algo-provider. Paragraph 5(III)(c) places due diligence on the broker before onboarding an empanelled algo provider. Black-box algos add the Research Analyst report requirement under paragraph 5(V)(a)(ii). The algo-provider register therefore needs the empanelment confirmation, the broker due-diligence record, and, for black-box algos, the Research Analyst registration plus the per-algo research report confirmation.

The retention period is not stated in the February 2025 circular. SEBI's master circular on stock brokers and the SEBI (Stock Brokers) Regulations, 1992 set the retention floor at five years for order records and broker books. Exchange-level operational modalities, issued 22 July 2025 and clarified in late September 2025, set the retention floor for API logs at five years on Indian-located servers. A six-month rolling log destroyed twelve months ago is not an answer to a SEBI inspection a year and one day after a disputed order.

05 · POST-1-APRIL ENFORCEMENT

The enforcement signal since 1 April 2026.

Paragraph 8 of the September 2025 circular makes 1 April 2026 the universal applicability date for all stock brokers. Today is 9 May 2026. Five weeks of operational application have run.

Three observable enforcement vectors. First, the 5 January 2026 sanction gate under paragraph 5 of the September 2025 circular barred non-compliant brokers from onboarding new retail clients for API-based algo trading. The bar is automatic. It does not require a SEBI adjudication. Brokers who failed to hit milestones 1 through 3 lose new-retail onboarding by operation of the circular itself.

Second, exchange-level monitoring under paragraph 6 of the September 2025 circular. Stock exchanges shall monitor the compliance of stock brokers with the above stated milestones. NSE and BSE both issued follow-up circulars in late November 2025 setting out the adherence-and-milestones reporting format. The monitoring runs continuously, not at quarter ends.

Third, the algo identifier itself is the enforcement instrument. Every algo order on every Indian exchange after 1 April 2026 carries an exchange-issued algo identifier. An exchange surveillance team can pull every order generated by a single algo across every broker that runs it, in seconds. An algo that misbehaves is identifiable, addressable, and switchable off via the kill switch contemplated in paragraph 5(IV)(a)(iii) of the February 2025 circular.

06 · BROKER VS VENDOR

Who carries the obligation.

The framework solves the broker-vs-vendor split with the agency device. The broker is principal. The algo provider is agent. The retail trader is the customer of the principal. Three downstream consequences.

Liability runs to the broker. Paragraph 5(II)(c) reads: Brokers shall be solely responsible for handling investor grievances related to algo trading and the monitoring of APIs for prohibited activities. The retail trader does not chase the fintech that built the algo. The retail trader chases the broker. The broker, in turn, has its own contractual recourse against the algo provider, but the customer-facing obligation is non-delegable.

Conflict of interest is broker-managed. Paragraph 5(III)(d) permits revenue sharing between broker and algo provider on subscription charges and brokerage. However, prominent and complete disclosures of all the charges shall be made to the client. The broker shall also ensure that such arrangements do not result in any conflict of interest. The disclosure-and-conflict obligation sits with the broker, not the algo provider.

API access is broker-controlled. Paragraph 5(I)(d) prohibits open APIs, requires unique vendor-client API keys, static-IP whitelisting, OAuth-only authentication, and two-factor authentication, and limits broker dealings to empanelled algo providers. All four controls are broker-implemented. None of them is a vendor obligation. A vendor without a broker relationship cannot route a single retail algo order to an Indian exchange after 1 April 2026.

07 · FIELD MAPPING

How SEBI clauses map to evidence fields.

5(I)(a)
Broker as principal, algo provider as agent. FIELD · trace.relationship (broker_id, algo_provider_id, principal_agent_attestation, agency_contract_ref).
5(I)(b)
Exchange-issued unique identifier on every algo order. FIELD · trace.actions[*].order (exchange_algo_id, exchange_order_id, ts, broker_order_seq).
5(I)(d)
No open APIs · unique key, static IP, OAuth, 2FA, empanelled providers only. FIELD · trace.api (api_key_fingerprint, source_ip, oauth_token_id, mfa_factor_id, vendor_empanelment_ref).
5(II)(a)
Exchange permission obtained before the algo is offered. FIELD · trace.algo (exchange_permission_ref, permission_grant_date, permission_status_at_order_ts).
5(II)(b)
Modification approval from the exchange. FIELD · trace.algo.version (algo_version, modification_approval_ref, prior_version_ref, change_log_hash).
5(III)(c)
Broker due diligence on empanelled algo providers. FIELD · trace.algo_provider (empanelment_ref, due_diligence_completion_date, due_diligence_artefact_hash).
5(V)(a)(ii)
Black-box algo · Research Analyst registration plus per-algo research report. FIELD · trace.algo.category (white_box | black_box), trace.algo.research_analyst_ref, trace.algo.research_report_hash.
2025/132 § 4
Glide path milestones · application, registration, mock session evidence. FIELD · trace.broker (milestone1_ref, milestone2_ref, milestone3_evidence_hash, sanction_gate_status).
W
Sample SEBI Retail Algo evidence package · Warrant registerINDEPENDENTLY VERIFIABLE WITHOUT CONTACTING WARRANT
→ /v/sebi-retail-algo-sample
08 · GENEALOGY FROM 2012

The earlier institutional algo framework.

Paragraph 1 of the February 2025 circular cites the genealogy directly: SEBI, vide circular no. CIR/MRD/DP/09/2012 dated March 30, 2012, provided broad guidelines on Algorithmic Trading (Algo - orders generated using automated execution logic). Thereafter, SEBI has introduced measures to strengthen controls around Algorithmic Trading.

The 2012 circular targeted institutional algo trading via direct market access. It set order-rate controls, system audits, and stock-exchange surveillance obligations on members offering algo trading. The 2018 SEBI committee report on strengthening the algorithmic trading framework refined the institutional surveillance model. The 2021 SEBI consultation paper on algorithmic trading by retail investors raised the API question for the first time. The February 2025 circular is the operative answer.

The genealogy matters because the 2012 circular is not superseded. Paragraph 6 of the February 2025 circular reads: Exchanges and brokers shall continue to comply with existing provisions prescribed with regard to Algorithmic trading. The retail framework sits on top of the institutional framework. A broker offering both desks complies with both.

Paragraph 9 of the February 2025 circular roots the legal authority in the standard SEBI machinery: This circular is issued in exercise of powers conferred under Section 11(1) of Chapter IV of the Securities and Exchange Board of India Act, 1992, read with Section 30 of the Securities and Exchange Board of India (Stock Brokers) Regulations, 1992 to protect the interests of investors in securities, to promote the development of and to regulate the securities market. Penalty exposure for non-compliance runs through the SEBI Act, the Stock Brokers Regulations, and the exchange bye-laws. There is no single penalty ceiling number to quote.

09 · INDIAN MULTI-REGULATOR

Relationship to RBI FREE-AI and India DPDP.

Indian financial AI in May 2026 is supervised by three regulators. SEBI under the framework above. The Reserve Bank of India under the FREE-AI committee report and the supervisory letters that followed it. The Ministry of Electronics and Information Technology under the Digital Personal Data Protection Act, 2023, with rules notified in 2025.

The perimeters intersect. A retail algo trading platform that uses AI to generate trade signals is in scope for SEBI under the February 2025 circular and for RBI under FREE-AI if it is operated by an entity under RBI's supervisory perimeter (most algo providers are not, but several broker-affiliated platforms are). It is in scope for DPDP because the trade ledger holds personal data of the investor.

The intersection has practical consequences for the evidence package. Three identifiers cohabit on every order. The exchange-issued algo identifier under SEBI paragraph 5(I)(b). The model-version identifier expected under RBI FREE-AI for any AI-generated signal. The data-fiduciary linkage under DPDP for any personal-data processing. One record that carries all three, independently verifiable without contacting Warrant, is the only artefact that survives a tripartite inspection.

10 · FAQ

Questions a compliance officer asks first.

When does the SEBI Retail Algorithmic Trading Framework apply to all stock brokers?

Paragraph 8 of the September 2025 circular, verbatim: W.e.f. April 01, 2026, algo framework specified in circular dated February 04, 2025 along with implementation standards and detailed operational modalities (issued by exchanges) will be applicable for all stock brokers. Brokers ready earlier could go live from 1 October 2025 under paragraph 4 of the same circular.

Who is the principal under the framework, the broker or the algo provider?

The broker. Paragraph 5(I)(a) of the February 2025 circular reads: For the purpose of provision of algo trading through APIs, brokers shall be the principal while any algo provider or fintech/vendor (hereinafter referred to as Algo Provider) shall act as its agent, while using the API provided by the broker. Paragraph 5(II)(c) places sole responsibility for grievance handling and API monitoring on the broker.

Are SEBI-regulated entities the only source of algos under the framework?

No. Paragraph 5(III)(a) reads: While algo providers shall not be regulated by SEBI, for better oversight, any algo provider, providing the facility to place algo orders with Brokers through API, shall require to be empaneled with Exchanges in a manner as stipulated by Exchanges. Empanelment is exchange-led, not SEBI registration. Black-box algo providers separately register as Research Analysts under paragraph 5(V)(a)(ii).

What identifier must every algo order carry?

Paragraph 5(I)(b) reads: All algo orders originating/flowing through Application Programming Interface (API) extended by brokers to algo providers, shall be tagged with a unique identifier provided by Stock Exchange. Paragraph 5(II)(b) repeats the requirement and adds an audit trail purpose, plus an exchange-modification-approval requirement.

What does the framework require for black box algos?

Paragraph 5(V)(a)(ii) requires the algo provider for a black-box algo to register as a Research Analyst, maintain a detailed research report for each such algo, and confirm to the exchanges that the report has been maintained. A change in the logic governing the algo registers as a fresh algo with a fresh research report. White-box algos do not pull in the Research Analyst registration.

What are the September 2025 glide path milestones?

Three milestones inside paragraph 4 of the September 2025 circular. Milestone 1, 31 October 2025, retail algo product and at least one strategy applied for registration. Milestone 2, 30 November 2025, registration completed. Milestone 3, 3 January 2026, participation in at least one mock session with the new functionality complete in all aspects. Brokers failing to adhere shall be barred from onboarding new retail clients for API based algo trading w.e.f. 5 January 2026 under paragraph 5.

Can a tech-savvy retail investor write their own algo?

Yes, with limits. Paragraph 5(I)(c) reads: Algos developed by tech-savvy retail investors themselves, using programming knowledge, shall also be registered with the Exchange, through their broker, only if they cross the specified order per second threshold. Further, the same registered Algo shall be permitted to be used by such retail investors for their family (but not for other investors). Family for this purpose would mean self, spouse, dependent children and dependent parents. The threshold itself is set by the Broker's Industry Standards Forum, not directly by SEBI.

How do i produce a SEBI Retail Algo evidence package today?

Drop the algo execution trace at warrant.build/demo. Warrant produces a PDF mapped to the February 2025 circular per action, including the exchange-issued unique algo identifier, the empanelment status of the algo provider, the categorisation of the algo (white box or black box), and the broker due diligence record. The package is independently verifiable without contacting Warrant.

11 · READ THE SOURCE

Read the source directly.

Authored by Warrant Compliance, the regulatory-analysis function at Warrant. [email protected]. Editorial commentary on regulatory text. Not legal advice. The verbatim quotations of paragraphs 1, 3, 5(I), 5(II), 5(III), 5(IV), 5(V), 6, 7, and 9 of circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013 reflect the official English-language text published by SEBI on 4 February 2025. The verbatim quotations of paragraphs 1, 3, 4, 5, 6, and 8 of circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/132 reflect the official English-language text published by SEBI on 30 September 2025.