Uploadcare

Uploadcare is a file uploading and processing platform that provides REST APIs for file management, CDN delivery, image transformations, document conversion, video encoding, and malware scanning. Developers can integrate file upload widgets, manage files and metadata, apply on-the-fly image transformations via URL-based CDN API, handle multipart uploads for large files, configure webhooks, and leverage add-ons for extended processing capabilities.

Uploadcare publishes 9 APIs on the APIs.io network, including Add-Ons API, Conversion API, File API, and 6 more. Tagged areas include File Upload, File Management, CDN, Image Transformation, and Document Conversion.

The Uploadcare catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Uploadcare’s developer surface includes authentication, documentation, GitHub presence, engineering blog, pricing, and 17 more developer resources.

🌐 Visit website 📡 Source on GitHub

43.2/100 developing ▬ flat Agent 32/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessFreemiumSelf serve⚡ Free to try

2 APIs

File Upload File Management CDN Image Transformation Document Conversion Video EncodingMalware ScanningStorage Webhook

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 43.2/100 · developing

Contract Quality 14.9 / 23

Developer Ergonomics 4.3 / 18

Access Clarity 9.0 / 18

Operational Transparency 2.5 / 12

Contract Governance 2.7 / 11

Discoverability 6.2 / 9

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 32/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/uploadcare: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Uploadcare Add-Ons API

An `Add-On` is an application implemented by Uploadcare that accepts uploaded files as an input and can produce other files and/or [appdata](#operation/fileInfo) as an output.

Uploadcare Conversion API

The Conversion API from Uploadcare — 5 operation(s) for conversion.

Uploadcare File API

The File API from Uploadcare — 6 operation(s) for file.

Uploadcare File information API

There are a few ways to get information about uploaded file. One of them is on-the-fly with a request to CDN. Note: Other APIs also let you read file info: [after Upload](/docs/...

Uploadcare File metadata API

File metadata is additional, arbitrary data, associated with uploaded file. As an example, you could store unique file identifier from your system. Metadata is key-value data. Y...

Uploadcare File names API

Your original filenames can be accessed via [REST API](/docs/api/rest/). Make a request to receive a JSON response with file parameters including `original_filename`. You can se...

Uploadcare Group API

The Group API from Uploadcare — 2 operation(s) for group.

Uploadcare Project API

The Project API from Uploadcare — 1 operation(s) for project.

Uploadcare Webhook API

The Webhook API from Uploadcare — 3 operation(s) for webhook.

Scroll for all 9

Open Collections 12

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

URL API Reference Add-Ons API

OPEN COLLECTION

URL API Reference Add-Ons Conversion API

OPEN COLLECTION

URL API Reference Add-Ons File API

OPEN COLLECTION

URL API Reference Add-Ons File information API

OPEN COLLECTION

URL API Reference Add-Ons File metadata API

OPEN COLLECTION

URL API Reference Add-Ons File names API

OPEN COLLECTION

URL API Reference Add-Ons Group API

OPEN COLLECTION

URL API Reference Add-Ons Groups API

OPEN COLLECTION

URL API Reference Add-Ons Project API

OPEN COLLECTION

URL API Reference Add-Ons Upload API

OPEN COLLECTION

URL API Reference Add-Ons Webhook API

OPEN COLLECTION

Scroll for all 12

GraphQL 1

GraphQL schemas published by this provider.

Uploadcare GraphQL Schema

This is a conceptual GraphQL schema for the [Uploadcare](https://uploadcare.com/) platform, derived from the [Uploadcare REST API](https://uploadcare.com/api-refs/rest-api/), th...

GRAPHQL

Pricing Plans 1

Published pricing tiers and plan structures.

Uploadcare Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Uploadcare Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Uploadcare Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Uploadcare Context

37 classes · 22 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Uploadcare API Rules

5 rules · 4 warnings 1 info

SPECTRAL

JSON Schema 9

Standalone JSON Schema definitions for this provider's data models.

Uploadcare Applicationdata

4 properties

JSON SCHEMA

Uploadcare Contentinfo

3 properties

JSON SCHEMA

Uploadcare File

15 properties

JSON SCHEMA

Uploadcare Group

5 properties

JSON SCHEMA

Uploadcare Imageinfo

9 properties

JSON SCHEMA

Uploadcare Metadata

0 properties

JSON SCHEMA

Uploadcare Project

4 properties

JSON SCHEMA

Uploadcare Videoinfo

5 properties

JSON SCHEMA

Uploadcare Webhook

9 properties

JSON SCHEMA

Scroll for all 9

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Uploadcare Authentication

apiKey · 3 schemes

SECURITY

Uploadcare Domain Security

TLSv1.3 · DMARC

SECURITY

Uploadcare Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Uploadcare Agentic Access

44 operations · 24 acting

AGENTIC

Resources

Documentation 5

Reference material describing how the API behaves

Documentation

JSONSchema

JSONSchema

JSONSchema

JSONSchema

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Vocabulary

Vocabulary

JSONLD

JSONLD

Build 1

SDKs, sample code, and the tooling you integrate with

GitHub

GitHub

Access & Security 3

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 4

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

BlogRSS

BlogRSS

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

aid: uploadcare
name: Uploadcare
description: Uploadcare is a file uploading and processing platform that provides REST APIs for file management, CDN delivery,
  image transformations, document conversion, video encoding, and malware scanning. Developers can integrate file upload widgets,
  manage files and metadata, apply on-the-fly image transformations via URL-based CDN API, handle multipart uploads for large
  files, configure webhooks, and leverage add-ons for extended processing capabilities.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/uploadcare.png
url: https://raw.githubusercontent.com/api-evangelist/uploadcare/refs/heads/main/apis.yml
created: 2026-06-12
modified: 2026-06-12
specificationVersion: '0.23'
tags:
- File Upload
- File Management
- CDN
- Image Transformation
- Document Conversion
- Video Encoding
- Malware Scanning
- Storage
- Webhook
tags_raw:
- File Upload
- File Management
- CDN
- Image Transformation
- Document Conversion
- Video Encoding
- Malware Scanning
- Storage
- Webhooks
apis:
- aid: uploadcare:uploadcare-add-ons-api
  name: Uploadcare Add-Ons API
  description: 'An `Add-On` is an application implemented by Uploadcare that accepts uploaded files as an

    input and can produce other files and/or [appdata](#operation/fileInfo) as an output.'
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - Addons
  tags_raw:
  - Add-Ons
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-add-ons-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-conversion-api
  name: Uploadcare Conversion API
  description: The Conversion API from Uploadcare — 5 operation(s) for conversion.
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - Conversion
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-conversion-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-file-api
  name: Uploadcare File API
  description: The File API from Uploadcare — 6 operation(s) for file.
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - File
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-file-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-file-information-api
  name: Uploadcare File information API
  description: 'There are a few ways to get information about uploaded file.

    One of them is on-the-fly with a request to CDN.


    Note: Other APIs also let you read file info:

    [after Upload](/docs/api/upload/upload/file-upload-info)

    and [at REST](/docs/api/rest/file/info).'
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - File information
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-file-information-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-file-metadata-api
  name: Uploadcare File metadata API
  description: 'File metadata is additional, arbitrary data, associated with uploaded file. As an example, you could store
    unique file identifier from your system.


    Metadata is key-value data. You can specify up to 50 keys, with key names up to 64 characters long and values up to 512
    characters long.

    Read more in the [docs](https://uploadcare.com/docs/file-metadata/).


    **Notice:** Do not store any sensitive information (bank account numbers, card details, etc.) as metadata.


    **Notice:** File metadata is provided by the end-users uploading the files and can contain symbols unsafe in, for example,
    HTML context. Please escape the metadata before use according to the rules of the target runtime context (HTML browser,
    SQL query parameter, etc).'
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - File Metadata
  tags_raw:
  - File metadata
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-file-metadata-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-file-names-api
  name: Uploadcare File names API
  description: 'Your original filenames can be accessed via [REST API](/docs/api/rest/).

    Make a request to receive a JSON response with file parameters including

    `original_filename`.


    You can set an optional filename that users will see instead of the original name:


    ```https://ucarecdn.com/:uuid/:filename```


    `:filename` should comply with [file name conventions](https://tools.ietf.org/html/rfc3986#section-3.3)

    and it should be a valid part of a URL. For example, `filename.ext`.


    Here are some examples with full CDN URLs:


    ```

    Safe:


    // adding a simple filename

    https://ucarecdn.com/85b5644f-e692-4855-9db0-8c5a83096e25/image.jpg


    // using a char allowed in the pchar definition

    https://ucarecdn.com/85b5644f-e692-4855-9db0-8c5a83096e25/image@2x.jpg


    // allowed in pchar together with Image Transformations

    https://ucarecdn.com/85b5644f-e692-4855-9db0-8c5a83096e25/-/preview/-/resize/550x/image@1x.jpg


    // using a sub-delim allowed in pchar together with Image Transformations

    https://ucarecdn.com/85b5644f-e692-4855-9db0-8c5a83096e25/-/preview/-/grayscale/image_black&white@2x.jpg


    // using percent-encoded gen-delims that are not allowed in pchar

    https://ucarecdn.com/85b5644f-e692-4855-9db0-8c5a83096e25/-/preview/-/grayscale/image%5Bdesaturated%5D@2x.jpg


    Unsafe:


    // using gen-delims that are not allowed in pchar without encoding

    https://ucarecdn.com/85b5644f-e692-4855-9db0-8c5a83096e25/-/preview/-/grayscale/image[desaturated]@2x.jpg

    ```'
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - File names
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-file-names-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-group-api
  name: Uploadcare Group API
  description: The Group API from Uploadcare — 2 operation(s) for group.
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - Group
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-group-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-project-api
  name: Uploadcare Project API
  description: The Project API from Uploadcare — 1 operation(s) for project.
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - Project
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-project-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
- aid: uploadcare:uploadcare-webhook-api
  name: Uploadcare Webhook API
  description: The Webhook API from Uploadcare — 3 operation(s) for webhook.
  humanURL: https://uploadcare.com/api-refs/rest-api/v0.7.0/
  baseURL: https://api.uploadcare.com
  tags:
  - Webhook
  properties:
  - type: OpenAPI
    url: openapi/uploadcare-webhook-api-openapi.yml
  - type: Documentation
    url: https://uploadcare.com/docs/rest_api/
  - type: GraphQL
    url: graphql/uploadcare-graphql.md
  - type: Documentation
    url: https://uploadcare.com/docs/api_reference/cdn/
common:
- type: AgenticAccess
  url: agentic-access/uploadcare-agentic-access.yml
- type: VulnerabilityDisclosure
  url: security/uploadcare-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/uploadcare-domain-security.yml
- type: Authentication
  url: authentication/uploadcare-authentication.yml
- type: Website
  url: https://uploadcare.com/
- type: Documentation
  url: https://uploadcare.com/docs/
- type: GitHub
  url: https://github.com/uploadcare
- type: LinkedIn
  url: https://www.linkedin.com/company/uploadcare
- type: Blog
  url: https://uploadcare.com/blog/
- type: Pricing
  url: https://uploadcare.com/pricing/
- type: StatusPage
  url: https://status.uploadcare.com/
- type: X
  url: https://twitter.com/uploadcare
- type: Plans
  url: plans/uploadcare-plans-pricing.yml
- type: RateLimits
  url: rate-limits/uploadcare-rate-limits.yml
- type: FinOps
  url: finops/uploadcare-finops.yml
- type: Vocabulary
  url: vocabulary/uploadcare-vocabulary.yml
- type: JSONSchema
  url: json-schema/uploadcare-file.json
- type: JSONSchema
  url: json-schema/uploadcare-group.json
- type: JSONSchema
  url: json-schema/uploadcare-project.json
- type: JSONSchema
  url: json-schema/uploadcare-webhook.json
- type: JSONLD
  url: json-ld/uploadcare-context.jsonld
- type: BlogRSS
  url: https://uploadcare.com/blog/rss.xml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/uploadcare"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/uploadcare/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/uploadcare/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.