How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

2s Store API

The store API from 2s — 16 operation(s) for store.

2s Store API is one of 114 APIs that 2s publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Store. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 16 operations across 16 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://2s.io.

16 operations 16 paths 3 schemas 16 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://2s.io/mcp
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

2s Store API declares 1 security scheme for authenticating requests. An API key is passed in the header as PAYMENT-SIGNATURE (x402Payment).

  • x402Payment — x402 protocol v2: base64-encoded PaymentPayload. Call any paid endpoint without auth to receive a 402 with a multi-network PaymentRequirements envelope. Sign f…

Paths & Operations 16

Across 16 paths, the API surfaces 16 operations — 16 POST. Each is listed below with its method, path, parameters, and response codes.

Store 16
POST
/api/store/blob-delete
STORE: delete a file you uploaded, scoped to YOUR wallet
store_blob-delete 1 param body → 200400402405500502
POST
/api/store/blob-get
STORE: download a file you uploaded with store.blob-put, in
store_blob-get 1 param body → 200400402405500502
POST
/api/store/blob-list
STORE: list the files you've uploaded in a namespace
store_blob-list 1 param body → 200400402405500502
POST
/api/store/blob-put
STORE: upload a file (any bytes) in a single paid call
store_blob-put 1 param body → 200400402405500502
POST
/api/store/doc-delete
STORE: delete a stored document by id, scoped to YOUR wallet
store_doc-delete 1 param body → 200400402405500502
POST
/api/store/doc-get
STORE: fetch a stored document by id, scoped to YOUR wallet
store_doc-get 1 param body → 200400402405500502
POST
/api/store/doc-put
STORE: index a text document for full-text keyword search
store_doc-put 1 param body → 200400402405500502
POST
/api/store/doc-search
STORE: full-text keyword search over documents you stored
store_doc-search 1 param body → 200400402405500502
POST
/api/store/kv-delete
STORE: delete a key/value you stored, scoped to YOUR wallet
store_kv-delete 1 param body → 200400402405500502
POST
/api/store/kv-get
STORE: read back a JSON value you stored with store.kv-put
store_kv-get 1 param body → 200400402405500502
POST
/api/store/kv-put
STORE: persist a JSON value under a key, scoped to YOUR
store_kv-put 1 param body → 200400402405500502
POST
/api/store/kv-scan
STORE: list keys in a namespace, scoped to YOUR wallet
store_kv-scan 1 param body → 200400402405500502
POST
/api/store/usage
STORE: report how much storage YOUR wallet is using
store_usage 1 param body → 200400402405500502
POST
/api/store/vector-delete
STORE: delete a vector by id from a namespace, scoped to
store_vector-delete 1 param body → 200400402405500502
POST
/api/store/vector-query
STORE: nearest-neighbor search over vectors you upserted in
store_vector-query 1 param body → 200400402405500502
POST
/api/store/vector-upsert
STORE: upsert a vector for semantic retrieval, scoped to
store_vector-upsert 1 param body → 200400402405500502

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are X402PaymentRequiredV2 (5 properties), Source (3 properties). Each schema is shown below with its type and property counts.

X402PaymentRequiredV2
object
x402 v2 PaymentRequired envelope. Pick any entry from accepts[], sign for that rail, retry with the PAYMENT-SIGNATURE header.
5 properties 2 required
Source
object
Provenance of the data: upstream provider, source URL, and license.
3 properties
CallMeta
object
Per-call meta envelope — endpoint id, cost, caller kind, settlement details.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

2s-io-store-api-openapi.yml Raw ↑

Other APIs 2s publishes across the network.

2s MCP Server
2s A2A Agent
2s Agent API
2s Agriculture API
2s AI API
2s Airport API
2s Aviation API
2s Bank API
2s Barcode API
2s Batch API
2s Bio API
2s Bls API
Where this information came from

This is an independent, third-party profile of 2s Store API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.