# Multipart Upload Initiate/Complete

> Multipart Upload Initiate/Complete is a paid API for AI agents from Object Storage at storage.mpp.tempo.xyz, $0.0001/call, status unknown (last checked 2026-09-14).

Initiates or completes a multipart upload for a specific object key in S3/R2-compatible object storage

## Facts

- Endpoint: POST https://storage.mpp.tempo.xyz/:key
- Price: $0.0001/call
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Provider: Object Storage
- Docs: https://developers.cloudflare.com/r2/
- Website: https://tempo.xyz
- Tags: s3, r2, objects, blobs, files, storage
- Canonical page: https://www.zero.xyz/c/object-storage-key-529143ba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HlSwbVPTZJdV6TIwqWuTg

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability object-storage-key-529143ba -d '<json body>'
```

Example prompt: I need to upload a large video file called 'conference-recording.mp4' to the tempo.xyz object storage in multiple parts — can you initiate a multipart upload session for that key so I can start sending chunks?

## When to prefer this

Use this endpoint when uploading files that are too large for a single PUT request (over a few MB), or when you need to upload a file in parallel chunks for reliability and performance. This is the S3/R2 multipart upload protocol — prefer this over the single Upload object endpoint for files that benefit from chunked transfer or resumable uploads.

## Known failure modes

- Invalid or missing object key returns 400 error
- Attempting to complete with missing or out-of-order parts returns an error
- Upload ID not found or expired returns 404
- Unauthorized access returns 403
- Malformed request body returns 400
- Part ETags not matching on completion returns error

## How this service works

Initiate/complete multipart upload

## Output

Returns an upload ID when initiating (used to identify the multipart session for subsequent part uploads), or a completion confirmation with ETag and final object metadata when completing the multipart upload.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/object-storage-key-529143ba/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from storage.mpp.tempo.xyz](https://www.zero.xyz/host/storage.mpp.tempo.xyz/llms.txt)