MarketCrunch AI™BETA

MarketCrunch AI

API Overview

MarketCrunch API provides ticker-based endpoints for AI estimates and market analysis outputs.

Public Endpoint Base Pattern

  • Endpoints are GET-based and require a ticker query parameter.
  • Use uppercase ticker symbols where possible for consistency.
  • Responses are JSON payloads structured per endpoint contract.
  • Credit usage is 1 credit per unique ticker per day across all external endpoints; repeat requests for the same ticker on the same day are free.

API Key Generation

Authentication uses two keys: MC-API-KEY-ID and MC-API-SECRET-KEY. Use this gate to view the correct next step for your account.

Free Login

Authentication Headers

Authenticated API calls use key headers. Keep keys secret and send them on each request.

Required Headers

MC-API-KEY-ID: <your_api_key_id>
MC-API-SECRET-KEY: <your_api_secret_key>

Header Usage

  • Send both headers on every external endpoint request.
  • Missing or invalid headers return authentication errors.
  • Use your generated key pair exactly as provided.

Key Security Best Practices

  • Never expose API keys in frontend bundles, public repos, or client-side logs.
  • Store keys in secure backend environment variables or secret managers.
  • Rotate keys immediately if you suspect exposure.

Simple Request Checklist

  • Use endpoint URL + ticker query param.
  • Attach both auth headers.
  • Handle 200 success and partial response fields where applicable.

External Endpoints

Available public endpoints from the current API snapshot.

GET/ai-estimates?ticker=<TICKER>

Returns AI estimate payload for the requested ticker.

curl -X GET "https://mktcrunch-api-52245432644.us-central1.run.app/ai-estimates?ticker=<TICKER>" \
  -H "MC-API-KEY-ID: <your_api_key_id>" \
  -H "MC-API-SECRET-KEY: <your_api_secret_key>"
Sample response
GET/technical?ticker=<TICKER>

Returns technical summary and required technical scores.

curl -X GET "https://mktcrunch-api-52245432644.us-central1.run.app/technical?ticker=<TICKER>" \
  -H "MC-API-KEY-ID: <your_api_key_id>" \
  -H "MC-API-SECRET-KEY: <your_api_secret_key>"
Sample response
GET/factors?ticker=<TICKER>

Returns positive and negative factors from analysis output.

curl -X GET "https://mktcrunch-api-52245432644.us-central1.run.app/factors?ticker=<TICKER>" \
  -H "MC-API-KEY-ID: <your_api_key_id>" \
  -H "MC-API-SECRET-KEY: <your_api_secret_key>"
Sample response
GET/weekly?ticker=<TICKER>

Returns weekly min/max range payload for the ticker.

curl -X GET "https://mktcrunch-api-52245432644.us-central1.run.app/weekly?ticker=<TICKER>" \
  -H "MC-API-KEY-ID: <your_api_key_id>" \
  -H "MC-API-SECRET-KEY: <your_api_secret_key>"
Sample response
GET/analyze?ticker=<TICKER>

Returns analysis response for the requested ticker.

curl -X GET "https://mktcrunch-api-52245432644.us-central1.run.app/analyze?ticker=<TICKER>" \
  -H "MC-API-KEY-ID: <your_api_key_id>" \
  -H "MC-API-SECRET-KEY: <your_api_secret_key>"
Sample response

Query Parameters

  • ticker (required)

Response Shapes

High-level success contracts for external endpoints.

GET /ai-estimates

  • 200 response includes: target_price, prev_close, target_delta_pct, options_signal, confidence.
  • 200 response can include: partial_error when downstream data is partially available.

GET /analyze

  • 200 response includes: symbol, as_of, currency, ai_estimate, technical, weekly_range, factors.
  • 200 response can include: fault when one or more sections fail while others still return.

GET /technical

  • 200 response includes: ticker, summary, scores, timeframe.

GET /weekly

  • 200 response includes: week_ending, min, max, current, refreshed_at, history.

GET /factors

  • 200 response includes: model, positive factors (key/label), negative factors (key/label).

Shared Error Contracts

Common public-facing errors and mapping-specific errors.

  • 400 invalid_ticker: required ticker query is missing or blank.
  • 500 prediction_service_not_configured: required downstream configuration is missing.
  • 502 prediction_backend_unavailable: downstream backend failed or unavailable.
  • 502 technical_data_incomplete: technical mapping payload incomplete.
  • 502 weekly_data_incomplete: weekly mapping payload incomplete.
  • 502 factors_data_incomplete: factors mapping payload incomplete.