canonical: https://jentic.com/apis/upload.uploadcare.com/upload-uploadcare

# Upload Uploadcare Upload API Reference

Summary Upload API provides several ways of uploading files to Uploadcare servers in a secure and reliable way. API endpoints Upload API's root is located at `https://upload.uploadcare.com/`. **Note**: All API endpoints end with a forward slash `/`. Please do not forget to include it. API clients Please checkout [API clients](https://uploadcare.com/docs/integrations/) page for a list of official a. The API exposes 9 endpoints.

## For AI agents

Programmatically upload individual file parts, direct uploads. Covers 9 operations.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Upload individual file parts
- Direct uploads
- Start multipart upload
- Complete multipart upload
- Check the status of a task to fetch/upload a file from a URL
- Get information about an uploaded file

## Use cases

### Storage and Databases Operations

Use the Upload API Reference to perform storage operations programmatically. The API provides 9 endpoints covering core functionality including upload individual file parts, direct uploads, start multipart upload.

Example prompt: Call PUT /<presigned-url-x> to upload individual file parts

### Automated Upload Management

Automate upload operations by combining multiple Upload API Reference endpoints. Agents can direct uploads and then start multipart upload in a single workflow.

Example prompt: Call POST /base to direct uploads, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Upload API Reference 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 none tokens manually.

Example prompt: Search Jentic for 'upload individual file parts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| PUT | `/<presigned-url-x>` | Upload individual file parts |
| POST | `/base` | Direct uploads |
| POST | `/multipart/start` | Start multipart upload |
| POST | `/multipart/complete` | Complete multipart upload |
| POST | `/from_url` | Upload files from URLs |
| GET | `/from_url/status` | Check the status of a task to fetch/upload a file from a URL |
| GET | `/info` | Get information about an uploaded file |
| POST | `/group` | Create a file group |

## Key resources

- **Upload** — Operations related to Upload
- **Groups** — Operations related to Groups
- **Integrations** — You don't have to code most of the low-level API interactions.
We have high-level [libraries](https:
- **Errors** — If the request fails, Upload API returns an error response.
Error responses are returned in the form
- **Other APIs** — You can find the complete reference documentation for the REST API [here](https://uploadcare.com/api

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 79 / 100
  - AI-Readiness & Agent Experience: 14 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/upload.uploadcare.com/upload-uploadcare/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Uploadcare Upload API by hand means orchestrating direct, multipart, and from-URL upload flows, tracking upload status, and grouping files yourself. Through Jentic you install once, import the Upload API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Upload API carries its targets in the request body rather than in the URL path, so limit the agent to the operations it needs, such as starting a multipart upload or checking from-URL status. You choose that operation set, so nothing beyond what you list runs.
- **Credential handling:** Your Uploadcare credential 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 'upload a file from a URL' or 'complete a multipart upload', and Jentic returns the matching Upload API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the Upload API Reference use?

The Upload API Reference uses no 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 upload individual file parts with the Upload API Reference?

Yes. Use the PUT /<presigned-url-x> endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Upload API Reference?

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 upload individual file parts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'upload individual file parts'. Jentic returns the matching Upload API Reference operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Upload API Reference have?

The Upload API Reference exposes 9 endpoints covering upload, groups, integrations operations.

### Can I limit what my agent is allowed to do with the Uploadcare Upload API?

Yes. Because you run Jentic One yourself, you decide which Upload API operations your agent may call, so you can grant only what a task needs, such as starting a multipart upload or checking from-URL status, while withholding direct uploads or file-group creation. This API carries its targets in the request body rather than the URL path, so scoping the allowed operation set is what bounds the agent, and nothing beyond the operations you list will run. Your Uploadcare credential is stored encrypted by your own instance and injected only at execution time.