DEV Community: AION Analytics

One IMI analysis, two delivery formats: structured JSON or a text report

AION Analytics — Thu, 12 Nov 2026 12:50:22 +0000

An application needs fields it can parse. An analyst may need a report they can read. The current AION Indian Market Intelligence REST contract supports both through one optional request field: output_format. JSON is the default; "text" selects a plain-text report. The same analysis and quota apply. Current API documentation.

The input is an event supplied by the customer

IMI accepts one Indian financial or policy headline and optional article text in body. It returns modelled sector impact, numeric confidence and stakeholder views. The standalone API does not fetch a continuous news feed. Licensed institutional event ingestion is a separately proposed service. Product boundaries / Institutional scope.

Request a text report

This request template requires your own eligible AION API key. It is not a claim that a particular headline will produce a particular result.

curl -X POST 'https://api.aionanalytics.in/v1/analyze' \
  -H 'Content-Type: application/json' \
  -H "X-API-Key: $AION_API_KEY" \
  -d '{
    "headline": "RBI announces a change in the policy repo rate",
    "body": "Optional article context from your permitted source.",
    "output_format": "text"
  }'

A successful text response uses Content-Type: text/plain; charset=utf-8. Its report includes the submitted headline, numeric confidence, nonzero sector impacts and available stakeholder impacts. It does not invent a resolved event label or add a reasoning receipt. Text response contract.

Choose the format for the consumer

Requirement	Format
Persist a full sector vector in an application	`"json"`, or omit `output_format`
Present a readable executive or analyst report	`"text"`
Inspect sectors with no modelled impact	JSON; zero-valued sectors are omitted from the text summary
Handle an error	Parse the JSON error, even when text was requested

The current JSON contract describes all 32 output sectors, including zero-impact entries. Numeric confidence is part of the analysis, not a probability of profit. A processed response is not proof that the model understood the event correctly. Coverage and interpretation.

Keep the error path distinct

Unsupported output_format values return HTTP 422. Errors remain JSON. A client should inspect both status and content type before choosing a JSON parser or text display, and should preserve authorization and quota failures as failures. Formatting must not turn an unsuccessful request into a neutral-looking market summary. Published request and error contract.

Access and input retention

New self-service API enrollment is temporarily paused. Existing keys continue under their terms; approved developer integrations use separately confirmed access arrangements. Current prices, quotas and eligibility belong in the API catalogue, rather than an indefinitely copied article.

Under the published policy, unclassified or dynamically fallback-resolved headlines may be retained to improve and train the classifier, linked to the API key by a one-way hash. Other query text is not retained under that policy; billing uses query hashes. Submit only text you are permitted to process. Privacy Policy / IMI input-retention explanation.

AION Analytics Private Limited (India). Canonical integration documentation. Research information, not investment advice, broker execution or a guaranteed classification.

Choose a useful presentation without changing the meaning of the underlying analysis...

AION Intraday Infrastructure: choosing Full Engine or White-Box integration

AION Analytics — Thu, 12 Nov 2026 12:49:31 +0000

A quantitative team can own a strategy and still need the surrounding analytics: options Greeks, indicators, a separate assessment stage and a controlled delivery interface. AION Intraday Infrastructure is our flagship institutional technology project for evaluating those boundaries. Full Engine and White-Box leasing remain proposed contracts, pending legal review and tenant-isolation acceptance. They are not currently orderable services. Current product scope.

Two integration choices

The proposed Full Engine combines Rust computation, five proprietary strategy categories, Edge Heuristics, native Edge ML and approved analytical delivery. The public categories are S1 Intraday Momentum, S2 Mean Reversion, S3 Volatility Breakout, S4 Greeks Scalping and S5 Event-Driven. These names describe capability categories, not disclosed strategy implementations or a verified mapping to private strategy IDs. Public architecture.

The proposed White-Box arrangement is for a customer that keeps its own strategy. It would provide processed Greeks and indicators, with an optional Edge assessment of agreed candidate metadata. Keeping strategy source private does not mean no information is transmitted: the payload, logging and retention boundaries must be agreed. White-Box scope.

A conceptual integration comparison, not an executable endpoint example:

Customer need	Proposed arrangement	Customer responsibility
Evaluate the complete analytical workflow	Full Engine	Authorized input, agreed output use and downstream decisions
Retain an existing proprietary detector	White-Box	Own strategy, source permissions and optional candidate payload
Interpret a supplied financial headline	Separate standalone IMI API	Supply permitted event text and hold an eligible API key

View the public Full Engine diagram and White-Box diagram.

Exact interface names, with their status

Interface	Status
`WSS /v1/signals/execute`	Proposed Full Engine analytical delivery; no broker orders
`WSS /v1/stream/greeks`	Proposed processed Greeks and indicators
`REST /v1/edge/evaluate`	Proposed candidate assessment
`REST /v1/edge/historical`	Proposed licensed replay
`POST /v1/analyze`	Separately published standalone IMI API

Do not construct a public WebSocket hostname from these identifiers. Authentication, schemas, reconnect behavior and delivery guarantees require their own accepted contract. The word execute describes the analytical pipeline, not brokerage execution. Interface documentation.

Deployment is part of the test

AION Hosted, BYOC in an approved AWS, Azure or GCP environment, and On-Premise are intended arrangements. None is a blanket claim of certified isolation or performance. An internal gate measurement is not complete WebSocket latency. Proposed service levels require end-to-end qualification and a signed agreement. Deployment and acceptance.

Data rights remain a separate requirement

AION does not sell, sublicense, distribute, redistribute, publish, broadcast or otherwise provide raw exchange ticks, quote streams, order book records, private brokerage feeds or samples. The prohibition includes free demonstrations, trials, evaluation samples and onward redistribution. Customers must hold appropriate source and processing rights; transformation alone does not create redistribution permission. Data-rights policy.

Access is evaluated for qualified professional developers, verified SEBI-registered Research Analysts and Investment Advisers, and eligible institutional or brokerage technology teams. This is not a retail signal subscription. Documentation grants no data rights, broker credentials, trading permissions or advisory authorization, and promises no financial return, regulatory approval or contractual SLA. Qualification boundaries.

AION Analytics Private Limited (India). Discuss an evaluation / Canonical GitHub documentation.

Start with the input rights, required outputs and acceptance workload...