LlamaParse adapter: `url` field in json_schema.json doesn't match `base_url` config key, breaking EU region support

[amohammadict]

Bug Description

The LlamaParse x2text adapter has a mismatch between the UI schema field name
and the config key used in the adapter code, causing the base URL to always
fall back to the hardcoded US endpoint regardless of what the user enters.

Files affected

• unstract/sdk1/src/unstract/sdk1/adapters/x2text/llama_parse/src/static/json_schema.json
  — defines the UI field as "url"
• unstract/sdk1/src/unstract/sdk1/adapters/x2text/llama_parse/src/constants.py
  — defines BASE_URL = "base_url"
• unstract/sdk1/src/unstract/sdk1/adapters/x2text/llama_parse/src/llama_parse.py
  — reads self.config.get(LlamaParseConfig.BASE_URL) which maps to "base_url"

Impact

Users with EU region LlamaCloud accounts cannot use LlamaParse — their API key
is sent to https://api.cloud.llamaindex.ai (US) instead of
https://api.cloud.eu.llamaindex.ai (EU), resulting in a 401 Unauthorized error.

Fix

In json_schema.json, rename the field from "url" to "url" → "base_url":

Version

latest