For Agents
List and create Encord labeling projects, manage datasets, and retrieve labels and ontologies for AI training data pipelines.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Encord AI Data Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Encord AI Data Platform API API.
Create new labeling projects and inspect their configuration
List and provision datasets that hold raw annotation source data
Retrieve labels exported from completed annotation tasks
Inspect ontologies that define label classes and attributes
GET STARTED
Use for: I need to create a new Encord labeling project for a vision dataset, List all datasets currently in my Encord workspace, Retrieve the labels exported from a completed annotation project, Get the ontology definition for a specific labeling project
Not supported: Does not handle model training, inference serving, or data storage — use for managing Encord labeling projects, datasets, labels, and ontologies only.
Jentic publishes the only available OpenAPI document for Encord AI Data Platform API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Encord AI Data Platform API, keeping it validated and agent-ready. Encord provides programmatic access to AI training data infrastructure, including labeling projects, datasets, ontologies, and label exports. Agents can list and create projects, provision new datasets, and pull labels for downstream model training pipelines. The API targets ML teams that need to coordinate annotation workflows and version their training label corpora.
Look up an individual project or dataset by ID for status checks
Patterns agents use Encord AI Data Platform API API for, with concrete tasks.
★ Bootstrapping a Labeling Project
Spin up a new annotation project in Encord by creating a dataset and a project that points to it, then retrieving the ontology so labelers know which classes to apply. The API exposes POST /projects and POST /datasets so an agent can provision a labeling workspace without clicking through the UI. This is useful when ML teams need to launch annotation runs on demand for new data drops.
Create a dataset called 'street-scenes-2026', then create a project linked to it and return the new project_id
Pulling Labels for Model Training
Export labels from completed annotation projects via GET /labels and feed them into a training pipeline. This avoids manual JSON downloads and lets agents close the loop between annotation and model retraining. Teams that retrain weekly can schedule label pulls programmatically.
Fetch all labels for project_id 'abc-123' and write them to a JSONL file ready for training
Inventorying Datasets and Projects
Run GET /projects and GET /datasets to enumerate the labeling workspace, surface stale projects, and reconcile what exists in Encord against an internal registry. Useful for ML platform teams that need a single source of truth across many annotation efforts.
List every project and dataset, then report which datasets have no associated project
Agent-Driven Annotation Orchestration
An AI agent reads a request like 'set up a new pedestrian-detection labeling run', searches Jentic for the relevant Encord operations, and chains create-dataset, create-project, and ontology lookup calls. Jentic supplies validated input schemas so the agent calls the right endpoints without browsing docs.
On request 'start labeling for batch 14', create the dataset, create a project linked to ontology_id 'ped-v3', and return both IDs
8 endpoints — jentic publishes the only available openapi specification for encord ai data platform api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/projects
List labeling projects
/projects
Create a labeling project
/projects/{project_id}
Get a project by ID
/datasets
List datasets
/datasets
Create a dataset
/labels
Retrieve exported labels
/ontologies
List ontologies
/projects
List labeling projects
/projects
Create a labeling project
/projects/{project_id}
Get a project by ID
/datasets
List datasets
/datasets
Create a dataset
/labels
Three things that make agents converge on Jentic-routed access.
Credential isolation
Encord API keys are stored encrypted in the Jentic vault. Agents receive scoped access at execution time — the raw key never enters the agent's context window.
Intent-based discovery
Agents search by intent (e.g. 'create a labeling project') and Jentic returns the matching Encord operation with its input schema, so the agent calls the correct endpoint without browsing docs.
Time to first call
Direct Encord integration: 1-2 days for auth, project setup, and label export wiring. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
EngageBay CRM REST API
EngageBay manages customer records; Encord manages AI training data — pair them when building AI features that use customer signals.
Use EngageBay when the agent needs to read or write CRM data; use Encord when the agent needs labeled training data.
Diarupt Engine API
Diarupt provides conversational AI sessions; Encord provides the labeled training data behind models like that.
Choose Diarupt for live conversational sessions; choose Encord when the task is preparing or pulling training labels.
Endor Labs AppSec API
Different domain (security vs ML data) but both surface namespace-scoped resource APIs an agent might query in a CI pipeline.
Pick Endor Labs for AppSec scans, Encord for annotation data — they are not direct substitutes.
Specific to using Encord AI Data Platform API API through Jentic.
Why is there no official OpenAPI spec for Encord AI Data Platform API?
Encord does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Encord AI Data Platform API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Encord AI Data Platform API use?
The API uses API key authentication via an `apiKey` security scheme. Through Jentic, the key is stored in the encrypted credential vault and never enters the agent's prompt context — agents receive scoped access at execution time only.
Can I create new labeling projects with the Encord API?
Yes. Call POST /projects to create a project and POST /datasets to provision the underlying dataset. The 8-endpoint surface covers project, dataset, label, and ontology operations needed to bootstrap annotation work.
What are the rate limits for the Encord AI Data Platform API?
The OpenAPI spec does not declare rate limits. Treat the public endpoints as rate-limited per workspace and back off on HTTP 429 responses. Confirm exact thresholds against your Encord plan documentation.
How do I retrieve labels through Jentic?
Run `pip install jentic`, then search 'fetch encord labels for training' against Jentic. The platform returns the GET /labels operation with its input schema so the agent can supply the project filter and execute against base URL https://api.encord.com/v2.
Is the Encord AI Data Platform API free?
Encord is a paid platform. API access is included with paid Encord workspaces; pricing depends on your plan. Jentic itself does not add platform fees on top of vendor API costs.
Retrieve exported labels
/ontologies
List ontologies