Projects
Workspaces for files, verification runs, and context data.
Projects are workspaces within an organization for organizing related files and verification work. All file uploads, verification runs, and verification contexts belong to a project.
Project Types
| Type | Description | Best for |
|---|---|---|
standard | Default project type | Production workflows, ongoing verification |
research | Academic/research use | Batch processing, dataset creation, experimentation |
Research projects have higher processing limits and are intended for academic institutions and organizations running large-scale dataset verification. Contact support@crowdee.ai to have a project marked as research.
Creating a Project
curl -X POST https://api.crowdee.ai/v2/projects \
-H "X-API-Key: crw_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Disinformation Campaign Q4",
"type": "standard"
}'Example response:
{
"id": "proj_abc123",
"name": "Disinformation Campaign Q4",
"type": "standard",
"organizationId": "org_xyz789",
"createdAt": "2024-11-15T08:00:00Z"
}Managing Files
Upload files to a project with a multipart POST:
curl -X POST https://api.crowdee.ai/v2/projects/{projectId}/files \
-H "X-API-Key: crw_YOUR_API_KEY" \
-F "file=@document.pdf"After upload, Crowdee automatically enriches the file — extracting technical metadata, codec information, and other signals that verification pipelines operate on. Check enrichmentStatus before starting a pipeline run.
For a full guide to file management and enrichment, see Files & Enrichment.
Verification Contexts
Verification contexts are named sets of key-value pairs that provide contextual claims to pipelines — for example, the claimed source of an image or the date a video was supposedly recorded. Saving a context lets you reuse the same claims across multiple runs without retyping them.
Create a verification context:
curl -X POST https://api.crowdee.ai/v2/projects/{projectId}/verification-contexts \
-H "X-API-Key: crw_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Reuters Syria November 2024",
"data": {
"claimed_source": "Reuters",
"claimed_date": "2024-11-15",
"claimed_location": "Damascus, Syria"
}
}'Reference the context when starting a verification run using context_id:
curl -X POST https://api.crowdee.ai/v2/projects/{projectId}/verification-runs \
-H "X-API-Key: crw_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"pipeline_id": "verify-news-article",
"file_ids": ["{fileId}"],
"context_id": "{contextId}"
}'Contexts let you re-run the same pipeline against different claimed provenance without re-typing values each time. This is especially useful when batch-verifying a set of files that all share the same claimed origin.
For a full guide, see Verification Contexts.
Dossier View
The dossier endpoint returns all verification runs for a project, grouped by pipeline — useful for building audit reports or reviewing the full verification history of a project:
curl https://api.crowdee.ai/v2/projects/{projectId}/dossier \
-H "X-API-Key: crw_YOUR_API_KEY"How is this guide?
Organizations
Billing entities, modules, and member management.
Billing & Credits
How the credits system works and a guide to pricing tiers.