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...
Top comments (0)