LlamaExtract

⚠️ EXPERIMENTAL This library is under active development with frequent breaking changes. APIs and functionality may change significantly between versions. If you're interested in being an early adopter, please contact us at [email protected] or join our Discord.

LlamaExtract provides a simple API for extracting structured data from unstructured documents like PDFs, text files and images (upcoming).

Quick Start

from llama_extract import LlamaExtract
from pydantic import BaseModel, Field

# Initialize client
extractor = LlamaExtract()


# Define schema using Pydantic
class Resume(BaseModel):
    name: str = Field(description="Full name of candidate")
    email: str = Field(description="Email address")
    skills: list[str] = Field(description="Technical skills and technologies")


# Create extraction agent
agent = extractor.create_agent(name="resume-parser", data_schema=Resume)

# Extract data from document
result = agent.extract("resume.pdf")
print(result.data)

Core Concepts

• Extraction Agents: Reusable extractors configured with a specific schema and extraction settings.
• Data Schema: Structure definition for the data you want to extract.
• Extraction Jobs: Asynchronous extraction tasks that can be monitored.

Defining Schemas

Schemas can be defined using either Pydantic models or JSON Schema:

Using Pydantic (Recommended)

from pydantic import BaseModel, Field
from typing import List, Optional


class Experience(BaseModel):
    company: str = Field(description="Company name")
    title: str = Field(description="Job title")
    start_date: Optional[str] = Field(description="Start date of employment")
    end_date: Optional[str] = Field(description="End date of employment")


class Resume(BaseModel):
    name: str = Field(description="Candidate name")
    experience: List[Experience] = Field(description="Work history")

Using JSON Schema

schema = {
    "type": "object",
    "properties": {
        "name": {"type": "string", "description": "Candidate name"},
        "experience": {
            "type": "array",
            "description": "Work history",
            "items": {
                "type": "object",
                "properties": {
                    "company": {
                        "type": "string",
                        "description": "Company name",
                    },
                    "title": {"type": "string", "description": "Job title"},
                    "start_date": {
                        "anyOf": [{"type": "string"}, {"type": "null"}],
                        "description": "Start date of employment",
                    },
                    "end_date": {
                        "anyOf": [{"type": "string"}, {"type": "null"}],
                        "description": "End date of employment",
                    },
                },
            },
        },
    },
}

agent = extractor.create_agent(name="resume-parser", data_schema=schema)

Important restrictions on JSON/Pydantic Schema

LlamaExtract only supports a subset of the JSON Schema specification. While limited, it should be sufficient for a wide variety of use-cases.

• All fields are required by default. Nullable fields must be explicitly marked as such, using "anyOf" with a "null" type. See "start_date" field above.
• Root node must be of type "object".
• Schema nesting must be limited to within 5 levels.
• The important fields are key names/titles, type and description. Fields for formatting, default values, etc. are not supported.
• There are other restrictions on number of keys, size of the schema, etc. that you may hit for complex extraction use cases. In such cases, it is worth thinking how to restructure your extraction workflow to fit within these constraints, e.g. by extracting subset of fields and later merging them together.

Other Extraction APIs

Batch Processing

Process multiple files asynchronously:

# Queue multiple files for extraction
jobs = await agent.queue_extraction(["resume1.pdf", "resume2.pdf"])

# Check job status
for job in jobs:
    status = agent.get_extraction_job(job.id).status
    print(f"Job {job.id}: {status}")

# Get results when complete
results = [agent.get_extraction_run_for_job(job.id) for job in jobs]

Updating Schemas

Schemas can be modified and updated after creation:

# Update schema
agent.data_schema = new_schema

# Save changes
agent.save()

Managing Agents

# List all agents
agents = extractor.list_agents()

# Get specific agent
agent = extractor.get_agent(name="resume-parser")

# Delete agent
extractor.delete_agent(agent.id)

Installation

pip install llama-extract==0.1.0

Tips & Best Practices

1. Schema Design:

   • Try to limit schema nesting to 3-4 levels.
   • Make fields optional when data might not always be present. Having required fields may force the model to hallucinate when these fields are not present in the documents.
   • When you want to extract a variable number of entities, use an array type. Note that you cannot use an array type for the root node.
   • Use descriptive field names and detailed descriptions. Use descriptions to pass formatting instructions or few-shot examples.
   • Start simple and iteratively build your schema to incorporate requirements.

2. Running Extractions:

   • Note that resetting agent.schema will not save the schema to the database, until you call agent.save, but it will be used for running extractions.
   • Check job status prior to accessing results. Any extraction error should be available as part of job.error or extraction_run.error fields for debugging.
   • Consider async operations (queue_extraction) for large-scale extraction once you have finalized your schema.

Additional Resources

• Example Notebook - Detailed walkthrough of resume parsing
• Discord Community - Get help and share feedback