Cubist Keys API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (Oidc).
An API key is passed in the header as Authorization (SignerAuth).
By default, every request must be authenticated.
Oidc — OIDC tokens allow users to authenticate using a third-party service. These are exchanged for signer session tokens.
SignerAuth — Signing API end-points use session tokens for auth. Specifically, with each request you need to use the \token\ from your signer session (which you create with…
Paths & Operations 14
Across 10 paths, the API surfaces 14 operations — 1 DELETE, 8 GET, 1 PATCH, 1 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.
Keys 14
PUT
/v0/org/{org_id}/derive_keydeprecated
Derive Key From Long-Lived Mnemonic
deriveKeyLegacy1 parambody→ 200default
PUT
/v0/org/{org_id}/derive_keys
Derive Key From New Or Existing Long-Lived Mnemonic
deriveKey1 parambody→ 200default
GET
/v0/org/{org_id}/export/{key_id}
Get an Org-Export Ciphertext
getOrgExport2 params→ 200default
GET
/v0/org/{org_id}/import_key
Create Key-Import Key
createKeyImportKey1 param→ 200default
PUT
/v0/org/{org_id}/import_key
Import Key
importKey1 parambody→ 200default
GET
/v0/org/{org_id}/keys
List Keys
listKeysInOrg6 params→ 200default
POST
/v0/org/{org_id}/keys
Create Key
createKey1 parambody→ 200default
GET
/v0/org/{org_id}/keys/{key_id}
Get Key
getKeyInOrg2 params→ 200default
DELETE
/v0/org/{org_id}/keys/{key_id}
Delete Key
deleteKey2 paramsbody→ 200202default
PATCH
/v0/org/{org_id}/keys/{key_id}
Update Key
updateKey2 paramsbody→ 200202default
GET
/v0/org/{org_id}/keys/{key_id}/attest
Attest to Key Properties
attestKey3 params→ 200default
GET
/v0/org/{org_id}/keys/{key_id}/roles
List Key Roles
listKeyRoles4 params→ 200default
GET
/v0/org/{org_id}/keys/{key_id}/tx
List Historical Transactions
listHistoricalKeyTx4 params→ 200default
GET
/v0/org/{org_id}/keys/{key_type}/{material_id}
Get Key by Material ID
getKeyByMaterialId3 params→ 200default
Schemas 65
The contract defines 65 schemas that model the data the API accepts and returns. The most detailed are HistoricalTx (11 properties), MfaRequestInfo (11 properties), MfaPolicy (8 properties), ClientSessionInfo (7 properties). Each schema is shown below with its type and property counts.
Empty
PreconditionErrorOwnCodes
string
EditPolicy
object
A policy which governs when and who is allowed to update the entity this policy is attached to (e.g., a role or a key). When attached to a role, by default, th…
3 properties
BadRequestErrorCode
string
MfaRequiredArgs
object
5 properties3 required
PreconditionErrorCode
AcceptedValueCode
string
PolicyErrorOwnCodes
string
UpdateKeyRequest
AcceptedValue
Different responses we return for success status codes.
Id
string
ForbiddenErrorCode
string
BinanceApiPropertiesPatch
object
5 properties
CreateKeyRequest
Seconds
integer
Duration measured in seconds A wrapper type for serialization that encodes a Duration as a u64 representing the number of seconds.
OperationKind
string
All different kinds of sensitive operations
UnauthorizedErrorCode
string
SignerErrorOwnCodes
string
DeriveKeysRequest
Request to derive keys for multiple types from a specified mnemonic.
SignDryRunArgs
object
2 properties1 required
ScopeSet
A set of scopes.
DeriveKeyRequest
Request to derive keys for one type from a specified mnemonic.
AcceptedResponse
ImportKeyRequestMaterial
object
3 properties3 required
EpochDateTime
integer
DateTime measured in seconds since unix epoch. A wrapper type for serialization that encodes a [SystemTime] as a [u64] representing the number of seconds since…
B32
string
Wrapper around a zeroizing 32-byte fixed-size array
CoinbaseDryRunArgs
object
2 properties2 required
ErrorResponse
object
The structure of ErrorResponse must match the response template that AWS uses
5 properties2 required
NotFoundErrorCode
string
ConflictErrorCode
string
CommonFields
Fields that are common to different types of resources such as keys, roles, etc. Includes versioning fields plus metadata, edit policy, etc.
KeyImportKey
object
A wrapped key-import key
4 properties4 required
SignerErrorCode
BybitDryRunArgs
object
3 properties3 required
PolicyErrorCode
MfaType
string
Different types that can be used to approve an MFA request
CreateAndUpdateKeyProperties
object
4 properties
Scope
All scopes for accessing CubeSigner APIs
KeyDerivationInfo
object
Derivation-related metadata for keys derived from a long-lived mnemonic
2 properties2 required
KeyTypeAndDerivationPath
object
3 properties2 required
SolanaTxCmp
object
1 property
TimeoutErrorCode
string
KeyInRoleInfo
object
4 properties2 required
HttpRequestCmp
How to compare HTTP requests when verifying MFA receipt (see [MfaRequest::verifyrequest])
HttpRequest
object
Information about the request. Captures all the relevant info (including the request body) about requests that require MFA. We use this to verify that when a r…
3 properties2 required
EvmTxCmp
object
3 properties
MfaPolicy
object
8 properties
NewSessionResponse
object
Information about a new session, returned from multiple endpoints (e.g., login, refresh, etc.).
5 properties4 required
KeyInfo
BinanceDryRunArgs
object
2 properties2 required
KeyType
string
KeyPropertiesPatch
Client-side wire payload for [KeyProperties]. Used in both directions: - On write: a patch, i.e., for each field, missing means "leave alone", null means "clea…
ClientSessionInfo
object
Session information sent to the client. This struct works in tandem with its server-side counterpart [SessionData].
7 properties7 required
BadGatewayErrorCode
string
ApprovalInfo
object
1 property1 required
CoinbaseApiPropertiesPatch
object
Wire-format patch payload for [KeyProperties::CoinbaseApi]. Every field follows the same per-field PATCH semantics: a missing field leaves the existing value a…
3 properties
Receipt
object
Receipt that an MFA request was approved.
3 properties3 required
EvmTxDepositErrorCode
string
ExplicitScope
string
Explicitly named scopes for accessing CubeSigner APIs
ImportKeyRequest
MfaRequestInfo
object
Returned as a response from multiple routes (e.g., 'get mfa', 'approve mfa', 'approve totp').
11 properties6 required
BybitApiPropertiesPatch
object
Wire-format patch payload for [KeyProperties::BybitApi]. Every field follows the same per-field PATCH semantics: a missing field leaves the existing value alon…
2 properties
Status
object
6 properties4 required
HistoricalTx
object
A recently signed transaction that we store in the DB.
11 properties7 required
InternalErrorCode
string
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Cubist Keys 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.