Extract Metadata is the new name for Ironclad’s Run AI bulk action on repository records. It lets you choose exactly which metadata properties and clauses Ironclad should extract from existing contracts, instead of always pulling every supported field.
Use Case
For example, if you’ve just migrated 5,000 historic vendor MSAs into the Repository, you can run Extract Metadata on that saved view and tell it to pull only renewal terms, notice periods, and contract value.
Prerequisites
| Features |
Records |
| Permissions |
Available out-of-the-box (OOTB) to customers with an Extract Metadata (formerly Run AI) entitlement. |
How to Extract Metadata
- In your Dashboard, select the contracts you want to extract metadata from.
- In the bulk actions bar, click Extract metadata.
- Select the Choose specific data and click Continue.
Note: You can still choose to automatically capture all properties and clauses in the selected contracts by selecting the Scan all data option instead.
Select or search for the key terms you want to extract from your contracts.
At this stage, you can click the dropdown list in the top-right corner and select All to pull up properties that are preconfigured by Ironclad.
- Click Continue.
Review the metadata you want to extract, and click Confirm.
You'll receive a notification email with the CSV file to download when your metadata extraction is complete.
FAQs
Is Extract Metadata just a rename of Run AI?
Not exactly. The underlying capability is still the Run AI extraction pipeline, but the March 2026 release adds per-run field selection and updates the name to better reflect what the feature does.
Do users always have to select specific fields?
No. Selecting fields is optional. You can still extract all supported fields for a batch, just like before.
Can I use Extract Metadata during Smart Import?
Not in this release. Per-field selection is only available for existing repository contracts. Smart Import continues to perform its standard extraction for uploads.
Where do the selectable fields come from?
They are pulled from all properties and clauses that your instance currently supports for AI detection, including both out-of-the-box and custom AI properties/clauses.