Is Storj agent-ready?

Storj scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does Storj publish an OpenAPI spec?

No published OpenAPI specification was found when Storj was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Storj's Headless Index score?

Storj scores 42/100 on the Headless Index thesis-fit rubric and sits in Band C in the Object & File Storage category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Object & File Storage

Storj

Headless Index

42/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Storj earns Band C in the Object & File Storage category of The Headless Index, with a thesis-fit score of 42/100. Its strongest dimension is API-first design intent (12/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when Storj was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Storj is partially headless and partly UI-led. The Headless Index thesis-fit score of 42/100 puts it mid-table on the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Storj lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Two surfaces, unevenly built. The S3-compatible gateway at gateway.storjshare.io means any aws-sdk client works, and the native path is a Go library over DRPC (storj.io/uplink, github.com/storj/drpc) with C and mobile bindings around it. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: The uplink CLI is genuinely capable: `uplink cp`, `uplink share` and access grant derivation all work without a browser, and the entire satellite is open source (github.com/storj/storj) if you want to run one. The gap sits at the top. Creating a project, minting S3 gateway credentials and managing billing still start in the satellite console, and no official Terraform provider closes that loop.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Nothing exists. No MCP server sits under the storj GitHub organisation, no entry appears in the public registry, and the docs (docs.storj.io) carry no agent or tool-use section. For a network whose whole pitch is programmatic access to distributed storage, leaving agents to wrap the uplink binary themselves is a missed opportunity rather than a neutral choice.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Storj emits nothing. There is no event catalogue, no webhook registration endpoint, no signing scheme and no bucket notification configuration in either the native uplink path or the S3 gateway (docs.storj.io lists none). An agent that needs to react to an upload has to poll a bucket listing, which is the crudest option available and scales badly against large prefixes. Net assessment: integrators can build agent flows against Storj, but the rough edge to plan around is MCP posture^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent12/20

scored

Two surfaces, unevenly built. The S3-compatible gateway at gateway.storjshare.io means any aws-sdk client works, and the native path is a Go library over DRPC (storj.io/uplink, github.com/storj/drpc) with C and mobile bindings around it. What is missing is a documented REST API for projects, access grants and buckets at the account level, which keeps provisioning tied to the console.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
·GraphQL endpointDiscovered at https://www.storj.io/graphql, introspection disabled or scoped
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation12/20

scored

The uplink CLI is genuinely capable: `uplink cp`, `uplink share` and access grant derivation all work without a browser, and the entire satellite is open source (github.com/storj/storj) if you want to run one. The gap sits at the top. Creating a project, minting S3 gateway credentials and managing billing still start in the satellite console, and no official Terraform provider closes that loop.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture4/20

scored

Nothing exists. No MCP server sits under the storj GitHub organisation, no entry appears in the public registry, and the docs (docs.storj.io) carry no agent or tool-use section. For a network whose whole pitch is programmatic access to distributed storage, leaving agents to wrap the uplink binary themselves is a missed opportunity rather than a neutral choice.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

github.sdks@2026-08-19

Schema observability10/20

scored

There is no OpenAPI document and no open introspection endpoint. What exists instead is protobuf: the wire protocol is defined in .proto files across the open repositories and served over DRPC (github.com/storj/drpc), which is machine-readable if an agent knows to look for protos rather than a spec URL. For the gateway path, the S3 models fill the gap.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://www.storj.io/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events4/20

scored

Storj emits nothing. There is no event catalogue, no webhook registration endpoint, no signing scheme and no bucket notification configuration in either the native uplink path or the S3 gateway (docs.storj.io lists none). An agent that needs to react to an upload has to poll a bucket listing, which is the crudest option available and scales badly against large prefixes.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:C band: scores 40-75 range

04 / Embed

Show Storj's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Object & File Storage

Backblaze B2C

Headless Index 41/100

UploadcareC

Headless Index 40/100

FilestackD

Headless Index 36/100

See full Object & File Storage ranking →

FAQ

Storj and agent readiness

Is Storj agent-ready?: Storj scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does Storj publish an OpenAPI spec?: No published OpenAPI specification was found when Storj was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Storj's Headless Index score?: Storj scores 42/100 on the Headless Index thesis-fit rubric and sits in Band C in the Object & File Storage category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.