canonical: https://jentic.com/apis/storj.io/storj

# Storj DCS S3-Compatible Gateway API

Storj Decentralized Cloud Storage provides an S3-compatible gateway for object storage. This spec covers the primary S3-compatible operations supported by the Storj gateway, plus Storj-specific extensions such as object TTL and attribution. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically list all buckets, list objects in a bucket. Covers 11 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- List all buckets
- Create a bucket
- Delete a bucket
- Download an object
- Upload an object

## Use cases

### CRM Operations

Use the Storj DCS S3-Compatible Gateway API to perform crm operations programmatically. The API provides 11 endpoints covering core functionality including list all buckets, list objects in a bucket, create a bucket.

Example prompt: Call GET / to list all buckets

### Automated Resource Management

Automate resource operations by combining multiple Storj DCS S3-Compatible Gateway API endpoints. Agents can list objects in a bucket and then create a bucket in a single workflow.

Example prompt: Call GET /{bucketName} to list objects in a bucket, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Storj DCS S3-Compatible Gateway 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | List all buckets |
| GET | `/{bucketName}` | List objects in a bucket |
| PUT | `/{bucketName}` | Create a bucket |
| DELETE | `/{bucketName}` | Delete a bucket |
| GET | `/{bucketName}/{objectKey}` | Download an object |
| PUT | `/{bucketName}/{objectKey}` | Upload an object |
| DELETE | `/{bucketName}/{objectKey}` | Delete an object |
| POST | `/{bucketName}/{objectKey}?uploads` | Initiate a multipart upload |

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 64 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/storj.io/storj/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 Storj DCS S3-Compatible Gateway API by hand means handling its S3-style bearer auth against gateway.storjshare.io and managing multipart uploads and bucket operations yourself. Through Jentic you install once, import the Storj DCS S3-Compatible Gateway API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** This gateway puts the bucket and object in the URL path (/{bucketName}/{objectKey}), so a rule can pin your agent to reading and writing objects in one bucket. You choose the operations it may call, so deleting a bucket or deleting objects is not included unless you add it.
- **Credential handling:** Your Storj gateway 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 an object to a bucket' or 'list all buckets', and Jentic returns the matching Storj DCS S3-Compatible Gateway API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Storj DCS S3-Compatible Gateway API use?

The Storj DCS S3-Compatible Gateway API uses a Bearer token in the Authorization header. 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 all buckets with the Storj DCS S3-Compatible Gateway API?

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

### What are the rate limits for the Storj DCS S3-Compatible Gateway 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 all buckets through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all buckets'. Jentic returns the matching Storj DCS S3-Compatible Gateway API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Storj DCS S3-Compatible Gateway API have?

The Storj DCS S3-Compatible Gateway API exposes 11 endpoints for crm operations.

### Can I limit what my agent is allowed to do with the Storj DCS S3-Compatible Gateway API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use with this API. Since the gateway puts the bucket and object in the URL path (/{bucketName}/{objectKey}), you can pin the agent to reading and writing objects in a single bucket and grant only the operations it needs, such as List all buckets, List objects in a bucket, Download an object, and Upload an object. Destructive calls like Delete a bucket or Delete an object stay off limits unless you explicitly add them.