Every business runs on documents. Invoices land in AP, contracts go to legal, claims hit operations, resumes route to recruiting. Agno turns each of those into a typed Python object you can persist, route, or hand to the next system. Define the schema, pass the PDF, get a validated object back.Documentation Index
Fetch the complete documentation index at: https://docs.agno.com/llms.txt
Use this file to discover all available pages before exploring further.
result is a validated Invoice. The next line in your code is an INSERT, an ERP call, or a queue message. The model has done its job.
Workloads
| Workload | Page |
|---|---|
| Invoices, receipts, statements | Invoices and receipts |
| Contracts, MSAs, policies | Contracts |
| Resumes, applications, KYC intake | Forms and intake |
Production concerns
| You need to | Page |
|---|---|
| Process a folder or a queue of documents | Batch and durability |
| Schedule a nightly run that retries on failure | Batch and durability |
| Route low-confidence fields to a human | Human routing and eval |
| Track accuracy against a labeled golden set | Human routing and eval |
Explore
Invoices and receipts
Header fields, line items, and the path from PDF to a database row.
Contracts
Parties, dates, and a clause-level breakdown for review queues.
Forms and intake
Resumes, applications, KYC. Lists inside lists, same
File() plumbing.Batch and durability
Workflows over a folder, background runs, scheduled jobs with retries.
Human routing and eval
Confidence-gated approval and accuracy tracking against a golden set.