Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.landing.ai/llms.txt

Use this file to discover all available pages before exploring further.

An extraction model powers the field extraction capabilities of the API. It analyzes your Markdown content and extracts structured data according to your JSON schema. You can specify a model when calling the API directly or when using the client libraries. If you don’t specify a model, the API uses the latest extraction model (currently extract-20260314). 
curl -X POST 'https://api.va.landing.ai/v1/ade/extract' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'schema=...' \
  -F 'markdown=@markdown.md' \
  -F 'model=extract-20260314'

​
Model Versions

The following table lists the available model values for the API:
Model ValuesDescription
extract-20260314Use the extraction model snapshot released on March 14, 2026. For more information, go to extract-20260314. This is the default model.
extract-latestUse the latest extraction model snapshot.
These models have been deprecated and will result in errors: extract-20250930 and extract-20251024.

​
Why Model Versioning Matters

When integrating the API, you have two options for specifying the model:
  1. Use extract-latest to always get the newest version. This automatically gives you improvements and updates, but extraction results may change when new model versions are released.
  2. Use a specific version (like extract-20260314) to pin to an exact model version. This ensures consistent extraction results over time, but you won’t receive improvements.

​
extract-20260314

This model version introduces the following capabilities:
  • Unlimited schema size: No limits on the number of fields, nesting levels, or characters in a schema.
  • Semantic field matching: Use the x-alternativeNames keyword to define alternative labels for a field. The model maps fields by meaning, so fields with different names across documents resolve to the same schema field.
  • Cross-page table reconstruction: Tables that span page breaks are returned as a single array, with no post-processing needed.
  • Master schemas: Generate a single schema from multiple documents to handle field and layout variation across document types. Available in the Playground and via the API.
  • Schema drift detection: Update an existing schema when new or changed fields appear in your documents. Available in the Playground and via the API.
This version also introduces the metadata.warnings field in the API response. For more information, go to Warnings.
Extraction model extract-20260314 has different JSON schema requirements than the previous model. Learn about all schema requirements in Extraction Schema (JSON).

​
Set the Model in the API

When calling the endpoint, you can set the model using the model parameter. If you omit the model parameter, the API uses the latest model. This example shows how to specify a model: 
curl -X POST 'https://api.va.landing.ai/v1/ade/extract' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -F 'schema={"type": "object", "properties": {"field1": {"type": "string"}, "field2": {"type": "string"}}}' \
  -F 'markdown=@markdown.md' \
  -F 'model=extract-latest'

​
Set the Model with the Client Libraries

When using the Python or TypeScript library, you can set the model using the model parameter in the extract() method. If you omit the model parameter, the library will use the latest extraction model. 
import json
from pathlib import Path
from landingai_ade import LandingAIADE

# Define your extraction schema
schema_dict = {
    "type": "object",
    "properties": {
        "field1": {"type": "string"},
        "field2": {"type": "string"}
    }
}

client = LandingAIADE()
schema_json = json.dumps(schema_dict)

response = client.extract(
    schema=schema_json,
    markdown=Path("/path/to/output.md"),
    model="extract-latest"
)

​
The Playground Uses the Most Recent Model

The Playground always uses the most recent extraction model. If you pin a specific model version in your code, results may differ slightly from what you see in the Playground.

​
The Model Impacts the Schema Requirements

Different model versions have different JSON schema requirements. For details on supported keywords, field types, and structure, see Extraction Schema (JSON).