Install Jentic One Beta

Connect the Storj DCS S3-Compatible Gateway API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Storj DCS S3-Compatible Gateway API, 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.

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%2Fstorj.io%2Fstorj" | sh

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%2Fstorj.io%2Fstorj" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Storj DCS S3-Compatible Gateway API.

List all buckets

Create a bucket

Delete a bucket

Download an object

Upload an object

GET STARTED

Start building with Storj DCS S3-Compatible Gateway API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

11 endpoints — storj decentralized cloud storage provides an s3-compatible gateway for object storage.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Storj DCS S3-Compatible Gateway API through Jentic.

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.

Storj DCS S3-Compatible Gateway API

Name: Storj DCS S3-Compatible Gateway API
Brand: Storj DCS S3-Compatible Gateway API
Availability: InStock

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMCustomer Supportbearer11 EndpointsREST

For Agents

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

Use for: I need to all buckets, I want to objects in a bucket, Search for a bucket, Find all a bucket

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

42%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

46%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

72%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Storj DCS S3-Compatible Gateway API to your agent

Capabilities

Start building with Storj DCS S3-Compatible Gateway API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Storj DCS S3-Compatible Gateway API

Jentic AI Readiness Score

Storj DCS S3-Compatible Gateway API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness