Upload Uploadcare Upload API Reference
Official vendor OpenAPI document · agent-readyStorageObject Storagenone9 EndpointsREST
For Agents
Programmatically upload individual file parts, direct uploads. Covers 9 operations.
Use for: I need to upload individual file parts, I want to direct uploads, Search for start multipart upload, Find all complete multipart upload
Not supported: Does not handle payments, communications, or crm - use for storage and databases only.
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.
Install Jentic One Beta
Connect the Upload API Reference to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Upload API Reference, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fupload.uploadcare.com%2Fupload-uploadcare" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fupload.uploadcare.com%2Fupload-uploadcare" | 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.
Capabilities
What an agent can do with Upload API Reference API.
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
Patterns agents use Upload API Reference API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'upload individual file parts', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
9 endpoints — summary upload api provides several ways of uploading files to uploadcare servers in a secure and reliable way.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Upload API Reference API through Jentic.
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.
GET STARTED