This feature is currently in beta. The API may change.
POST /api/v1/agent. You need a processor ID such as cp_XXXXX that your team can access. The processor’s published contract determines the task and output format.
Before you begin, make sure you have:
- A Datalab account with an API key
- Python 3.11+ installed
- The Datalab SDK:
pip install datalab-python-sdk - Your
DATALAB_API_KEYenvironment variable set
Built-in Processors
The publishedjats processor produces JATS XML for scholarly articles. The
published wcag processor produces a tagged Accessible PDF. Both return
verification results that need review before using the artifact. See
JATS XML and Accessible PDF
for complete examples and output fields.
Run a Processor
AgentResult. Available output fields depend on the published processor. REST clients should check status and success, then download result_url if the completed response provides one.
Pin a Version
Useprocessor="cp_abc123@2.0" to pin a published version. Omitting the version runs the newest published version. Pin production integrations when you need repeatable processor behavior.
Run Options
AgentOptions accepts the following options. Omitted optional values use API defaults.
The published processor sets its output format. Conversion options such as
output_format are not run options on this endpoint.
CLI
Next Steps
Python SDK
Configure clients, handle errors, and control polling.
API Overview
Understand submission, polling, and completion responses.
Migration Guide
Replace deprecated custom processor calls.
Webhooks
Receive a notification when a run finishes.