canonical: https://jentic.com/apis/roboflow.com/roboflow

# Roboflow REST API

Roboflow REST API for managing workspaces, projects, images, annotations, and model inference. Roboflow is a computer vision platform for building, deploying, and managing ML models. The API exposes 5 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically list workspaces and projects, create a project. Covers 5 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- List Workspaces and Projects
- Create a Project
- Get Project and List Versions
- Export Dataset
- Search Universe Datasets

## Use cases

### Cloud Infrastructure Operations

Use the Roboflow REST API to perform cloud infrastructure operations programmatically. The API provides 5 endpoints covering core functionality including list workspaces and projects, create a project, get project and list versions.

Example prompt: Call GET /{workspace} to list workspaces and projects

### Automated Workspaces Management

Automate workspaces operations by combining multiple Roboflow REST API endpoints. Agents can create a project and then get project and list versions in a single workflow.

Example prompt: Call POST /{workspace}/projects to create a project, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Roboflow REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'list workspaces and projects', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{workspace}` | List Workspaces and Projects |
| POST | `/{workspace}/projects` | Create a Project |
| GET | `/{workspace}/{project}` | Get Project and List Versions |
| GET | `/{workspace}/{project}/{version}/{format}` | Export Dataset |
| GET | `/universe/search` | Search Universe Datasets |

## Key resources

- **Workspaces** — Workspace management
- **Projects** — Project management
- **Data Export** — Dataset export operations
- **Universe** — Roboflow Universe public dataset search

## Why Jentic

- **Setup:** Wiring the Roboflow REST API by hand means sending your API key as a bearer token or api_key query parameter, choosing between the api.roboflow.com and serverless hosts, and threading workspace and project names through each path yourself. Through Jentic you install once, import the Roboflow REST API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Roboflow puts the workspace and project in the URL path (/{workspace}/{project}), so a rule can pin your agent to one workspace or project and its reads. You choose the operations it may call, so writes like creating a project are not included unless you add them.
- **Credential handling:** Your Roboflow API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list workspaces and projects' or 'search Roboflow Universe', and Jentic returns the matching Roboflow REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Roboflow REST API use?

The Roboflow REST API uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list workspaces and projects with the Roboflow REST API?

Yes. Use the GET /{workspace} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Roboflow REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list workspaces and projects through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list workspaces and projects'. Jentic returns the matching Roboflow REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Roboflow REST API have?

The Roboflow REST API exposes 5 endpoints covering workspaces, projects, data export operations.

### Can I limit what my agent is allowed to do with the Roboflow REST API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which Roboflow operations and credentials your agent may use. Since Roboflow puts the workspace and project in the URL path, such as GET /{workspace}/{project}, you can pin the agent to a single workspace or project and to read-only calls like listing workspaces, getting a project, or exporting a dataset. Write operations such as POST /{workspace}/projects to create a project stay out of reach unless you explicitly allow them.