StorONE

StorONE builds S1, a software-defined enterprise storage platform that consolidates block, file and object storage onto a single hardware-agnostic engine, with auto-tiering across flash and disk, snapshots, replication, erasure coding and NAS/object services managed as one system. S1 is delivered as software that customers deploy on their own commodity servers or on validated partner hardware, so the management surface — the OmniUI web console, the StorONE CLI client and the S1 REST API — is served by the customer's own controller nodes rather than by a StorONE-hosted cloud. The REST API is documented in the public StorONE Documents Repository at docs.onestor.com and covers applications, volumes, snapshots, shares, object stores, hosts, mappings, NAS servers, nodes, resources, replication, floating IPs, templates, workflows, monitoring and notifications. StorONE also serves a Model Context Protocol endpoint from its marketing site.

StorONE publishes 1 API on the APIs.io network. Tagged areas include Storage, Enterprise Storage, Software-Defined Storage, Data Management, and Infrastructure.

The StorONE catalog on APIs.io includes 1 event-driven AsyncAPI specification.

StorONE’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, authentication, and 20 more developer resources.

🌐 Visit website 📡 Source on GitHub
34.4/100 thin ▬ flat Agent 44/100 agent ready Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2
1 APIs 1 MCP Servers
StorageEnterprise StorageSoftware-Defined StorageData ManagementInfrastructureBlock StorageFile StorageObject StorageBackupReplicationSnapshotsCompany

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2
Composite quality — 34.4/100 · thin
Contract Quality 10.7 / 25
Developer Ergonomics 11.9 / 20
Access Clarity 0.0 / 20
Operational Transparency 2.1 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 44/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 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 6 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/storone: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

StorONE S1 REST API

The S1 REST API manages a StorONE storage system: create and manage applications, volumes, snapshots, shares, file systems and object stores; register hosts and mappings; config...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

StorONE MCP server

StorONE serves a live Model Context Protocol endpoint from its WordPress marketing site at www.storone.com. It is a real, reachable remote MCP server — it answers MCP JSON-RPC o...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Storone Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Storone Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Storone Notifications Events

ASYNCAPI

Security Posture 2

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

Storone Authentication

0 schemes

SECURITY

Storone Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Storone Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted
GettingStarted
 SignUp
SignUp

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown
WellKnown
 MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 DataModel
DataModel
 Conformance
Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

CLI
CLI
 Packages
Packages

Access & Security 4

Authentication, authorization, and security posture

Authentication
Authentication
 OAuthScopes
OAuthScopes
 DomainSecurity
DomainSecurity
 Compliance
Compliance

Operate 3

Status, limits, changes, and where to get help

Support
Support
 ChangeLog
ChangeLog
 RateLimits
RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: storone
name: StorONE
description: StorONE builds S1, a software-defined enterprise storage platform that consolidates block, file and object storage
  onto a single hardware-agnostic engine, with auto-tiering across flash and disk, snapshots, replication, erasure coding
  and NAS/object services managed as one system. S1 is delivered as software that customers deploy on their own commodity
  servers or on validated partner hardware, so the management surface — the OmniUI web console, the StorONE CLI client and
  the S1 REST API — is served by the customer's own controller nodes rather than by a StorONE-hosted cloud. The REST API is
  documented in the public StorONE Documents Repository at docs.onestor.com and covers applications, volumes, snapshots, shares,
  object stores, hosts, mappings, NAS servers, nodes, resources, replication, floating IPs, templates, workflows, monitoring
  and notifications. StorONE also serves a Model Context Protocol endpoint from its marketing site.
url: https://raw.githubusercontent.com/api-evangelist/storone/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment
specificationVersion: '0.20'
created: '2026-08-29'
modified: '2026-08-29'
tags:
- Storage
- Enterprise Storage
- Software-Defined Storage
- Data Management
- Infrastructure
- Block Storage
- File Storage
- Object Storage
- Backup
- Replication
- Snapshots
- Company
tags_raw:
- Storage
- Enterprise Storage
- Software Defined Storage
- Data Management
- Infrastructure
- Block Storage
- File Storage
- Object Storage
- Backup
- Replication
- Snapshots
- Company
apis:
- aid: storone-s1-rest-api
  name: StorONE S1 REST API
  description: 'The S1 REST API manages a StorONE storage system: create and manage applications, volumes, snapshots, shares,
    file systems and object stores; register hosts and mappings; configure NAS servers, floating IPs and replication; manage
    nodes, drives and pools; read live and historical capacity, performance, utilization and health monitoring; and configure
    notification targets. Authentication is a session token obtained from POST /login and sent in the Authorization header.
    Because S1 is customer-deployed software, the base URL is the address of one of the customer''s own S1 controller nodes.'
  humanURL: https://docs.onestor.com/books/rest-api
  baseURL: https://{s1-controller-node}
  tags:
  - Storage
  - Block Storage
  - File Storage
  - Object Storage
  - Replication
  - Monitoring
  properties:
  - type: Documentation
    url: https://docs.onestor.com/books/rest-api
  - type: APIReference
    url: https://docs.onestor.com/books/rest-api/chapter/api-reference-guide
  - type: GettingStarted
    url: https://docs.onestor.com/books/rest-api/chapter/examples
  - type: Authentication
    url: authentication/storone-authentication.yml
  x-base-url-note: 'S1 is customer-deployed software: the API is served by the customer''s own S1 controller nodes over TCP,
    and StorONE operates no hosted API endpoint. The base URL is therefore templated by necessity, not by omission. StorONE''s
    own published examples use https://s1-node1.example.com/ and s1-n1.example.com as placeholders for the same reason. Probed
    2026-08-29: no StorONE-operated API host exists to name.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.storone.com/
- type: Documentation
  url: https://docs.onestor.com/
- type: APIReference
  url: https://docs.onestor.com/books/rest-api/chapter/api-reference-guide
- type: GettingStarted
  url: https://docs.onestor.com/books/getting-started
- type: Support
  url: https://storone.zendesk.com/hc/en-us
- type: Blog
  url: https://www.storone.com/blog/
- type: TermsOfService
  url: https://www.storone.com/eula/
- type: PrivacyPolicy
  url: https://www.storone.com/privacy-policy/
- type: SignUp
  url: https://www.storone.com/request-a-demo/
- type: WellKnown
  url: well-known/storone-well-known.yml
- type: MCPServer
  url: mcp/storone-mcp.yml
- type: LLMsTxt
  url: llms/storone-llms.txt
- type: Authentication
  url: authentication/storone-authentication.yml
- type: OAuthScopes
  url: scopes/storone-scopes.yml
- type: Conventions
  url: conventions/storone-conventions.yml
- type: ErrorCatalog
  url: errors/storone-problem-types.yml
- type: Lifecycle
  url: lifecycle/storone-lifecycle.yml
- type: ChangeLog
  url: changelog/storone-changelog.yml
- type: CLI
  url: cli/storone-cli.yml
- type: DataModel
  url: data-model/storone-data-model.yml
- type: Conformance
  url: conformance/storone-conformance.yml
- type: Plans
  url: plans/storone-plans-pricing.yml
- type: RateLimits
  url: rate-limits/storone-rate-limits.yml
- type: Packages
  url: packages/storone-packages.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/storone-domain-security.yml
- type: Compliance
  url: https://www.storone.com/quality-policy/
image: https://www.storone.com/wp-content/uploads/2023/11/logo.svg
x-enrichment:
  date: '2026-08-29'
  status: enriched
  artifacts_added: 24
  pass: local-v1

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/storone"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/storone/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/storone/evidence"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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