Estimates

AI Estimates

POST/v2/estimates/ai-estimates

Bavest's own AI estimates for a security across task types (regression, classification, sequence, hazard). Filter with metrics and task_types. Omit both to return everything.

One prediction per metric, task type, target and frequency: the newest. A target whose period ended more than 120 days ago without an actual is left out, its figure is reported by then; earlier forecasts are on /v2/estimates/ai-estimates-history. Annual targets are calendar years (January to December) for every company, also where the fiscal year ends in another month: MSFT 2026 covers January to December 2026, not the fiscal year ending June 2026.

Included in: Startup, Pro, Growth.

Authentication

Send your API key in the x-api-key header on every request to https://api.bavest.co. The samples read it from the BAVEST_API_KEY environment variable. Get an API key · Authentication guide

Parameters

This route takes no path or query parameters.

Try it

JSON body

Draft from the schema. Review and fill in required fields before sending.

POST /v2/estimates/ai-estimates

API key

Sent only to api.bavest.co for this request; not stored.

Sign in to send Get an API keySends with the key above, or sign in to use your account's key. Each request counts as one API call.

curl -X POST 'https://api.bavest.co/v2/estimates/ai-estimates' \
  -H "x-api-key: $BAVEST_API_KEY" \
  -H 'content-type: application/json' \
  --data '{"symbol":"AAPL","metrics":["eps","revenue"],"task_types":["regression"]}'

Samples read your key from BAVEST_API_KEY and follow the form.

Example response 200

{
  "data": {
    "meta": {
      "as_of": "2026-05-20",
      "model_version": "ai-eps-v1.4"
    },
    "predictions": [
      {
        "symbol": "AAPL",
        "metric": "eps",
        "task_type": "regression",
        "target_date": "2026-09-30",
        "prediction_date": "2026-05-20",
        "model_version": "ai-eps-v1.4",
        "frequency": "quarterly",
        "prediction": {
          "point": 2.41,
          "lower": 2.18,
          "upper": 2.65,
          "components": {
            "trend": 2.3,
            "seasonal": 0.11
          }
        },
        "explainability": {
          "top_features": [
            {
              "name": "revenue_ttm",
              "shap": 0.42
            },
            {
              "name": "gross_margin",
              "shap": 0.19
            }
          ]
        }
      }
    ]
  },
  "meta": {
    "parameters": {
      "symbol": "AAPL",
      "metrics": [
        "eps"
      ],
      "task_types": [
        "regression"
      ]
    },
    "time": 12
  }
}

From the docs, not your data. Long lists are cut to 3 items.

Request body

symbolstringrequired
Ticker symbol, ISIN, or CUSIP. Resolved server-side.
Example AAPL
metricsarray of string
Restrict to these metrics. Omit for all. Also accepts a comma-separated string.
task_typesarray of string
Restrict to these task types. Omit for all.

Response 200

Successful response · application/json

dataPredictionsResponse
Model predictions for a security.
- metaForecastMeta
  Freshness summary for the returned forecast set.
- predictionsarray of PredictionRecord
metaResponseMeta
Response envelope metadata. Always present on a 200: time is set by core/response.py on every successful response. Errors carry the same block, built by the same code, so a client parses one meta shape whether the call succeeded or failed.
- timeinteger
  Server-side processing time in milliseconds
  Example 17
- parametersobject
  Echo of the request parameters the endpoint resolved

Errors

400Invalid request parameters. Returned when required query parameters are missing, have invalid types, or violate constraints (e.g., providing both symbol and isin when they are mutually exclusive).
401Missing or invalid API key.
404Resource not found.
429Rate limit exceeded. Retry after the `Retry-After` header interval.
500An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.
502Upstream data provider returned an error or is temporarily unavailable. Retry after a short delay.
504The request timed out waiting for a response from the upstream data provider. This may occur for complex queries or during peak load.
defaultAn unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.