
Agent Execution
Execute previously created agents on files to extract structured data with consistent, reproducible results. Monitor execution status and retrieve results asynchronously for long-running processing tasks.Key Features
- Consistent Results: Same agent produces identical output structure across executions
- Async Processing: Long-running extractions handled asynchronously with status tracking
- Batch Processing: Execute agents on multiple files efficiently
- Status Monitoring: Track execution progress from queued to completed
- Result Retrieval: Access structured results when processing finishes
Use Cases
Automated Document Processing
Process invoices, receipts, and forms at scale with consistent extraction
Data Entry Automation
Extract information from scanned documents to eliminate manual entry
Archive Digitization
Convert paper document archives to structured digital data
Multi-Source Integration
Extract data from various document types into a unified format
Industry Applications
- Healthcare: Patient Care Automation - Process patient forms and medical records
- Legal & Finance: Insurance Claims - Automate claims document processing
- Retail: Omnichannel Commerce - Process product catalogs and receipts
- Manufacturing: Smart Manufacturing - Process quality control documents
Configuration Options
name (string) - Optional
name (string) - Optional
Agent name and version in format “agent-name:version”. Required if not using inline config.
inputs (object) - Required
inputs (object) - Required
Input files and parameters for the agent. Must include “file” key with file URL.
config (object) - Optional
config (object) - Optional
Inline agent configuration for one-time execution without creating a persistent agent.
priority (string) - Default: normal
priority (string) - Default: normal
Execution priority: “low”, “normal”, or “high”. Higher priority executions are processed first.
Example: Execute Agent by Name
Execute a previously created agent by referencing its name and version:Response Format
Example: Execute with Inline Prompt
Execute an agent using an inline prompt without creating a persistent agent:Response Format
Checking Execution Status
Monitor execution status and retrieve results when processing completes:Response Format (Completed)
Complete Workflow Example
Full workflow from file upload to result retrieval:Example Output
Execution Statuses
| Status | Description |
|---|---|
pending | Execution queued, waiting to start processing |
processing | Agent is actively processing the file |
completed | Processing finished successfully, results available |
failed | Processing encountered an error |
cancelled | Execution was cancelled by user |
Retrieving Artifacts
Agent executions can generate artifacts such as processed images, videos, or documents. These artifacts are returned as object references (e.g.,ImageRef, VideoRef) in the response and can be retrieved using the execution ID.
Artifacts Guide
Learn more about working with artifacts, including supported types and retrieval patterns
Best Practices
- File Formats: Use high-quality PDFs or images (PNG, JPEG) for best results
- File Size: Keep files under 20MB for optimal processing speed
- Polling Interval: Poll status every 2-5 seconds to balance responsiveness and API load
- Error Handling: Always check execution status and handle failures gracefully
- Batch Processing: Use multiple concurrent executions for processing large batches
Monitor Executions
Track and monitor all your agent executions in the VLM Run dashboard