Instructions tell anyformat how to extract a field. They are written in plain English and can include:Documentation Index
Fetch the complete documentation index at: https://docs.anyformat.ai/llms.txt
Use this file to discover all available pages before exploring further.
- What to look for
- Where it usually appears
- How to interpret ambiguous cases
“Extract the total amount charged, including taxes. Ignore subtotals.”
Why instructions matter
Good instructions
- Reduce ambiguity
- Improve accuracy
- Lower review time
Bad instructions
- Are vague
- Repeat the field name
- Try to encode logic unnecessarily
Instruction best practices
Explain edge cases when needed
If a value can appear in multiple forms, clarify which one to prefer.
Examples
Good instruction
Good instruction
Field:
total_amountInstruction: “Extract the final total amount including taxes. If multiple totals appear, use the one labeled ‘Grand Total’ or ‘Amount Due’.”Bad instruction
Bad instruction
Field:
total_amountInstruction: “The total amount.” (Too vague — doesn’t clarify which total or whether to include taxes.)What’s next?
AI Suggestions
Let AI help you write fields and instructions
Workflows
Put your schema to work with repeatable workflows
