Taurus
Taurus SA (Taurus HQ) is a Geneva-based digital asset infrastructure provider for banks and financial institutions. Its platform spans four institutional products exposed through APIs: Taurus-PROTECT (bank-grade custody of cryptocurrencies, digital assets, and private keys secured in FIPS 140-2 Level 3 HSMs), Taurus-CAPITAL (issuance and lifecycle management of tokenized securities and digital assets), Taurus-EXPLORER (blockchain node and indexing services across dozens of protocols), and Taurus-PRIME (institutional trading connectivity with deep liquidity via REST and FIX). The Taurus-PROTECT REST API (versioned /api/rest/v1/) uses bearer plus HMAC request signing, cursor-based pagination, and governance rules enforced by digital signatures, with first-party Java, Go, Python, and TypeScript SDKs, OIDC/SAML SSO, and SCIM provisioning.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Taurus the way a machine reads it — 8 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Taurus scores 36.6/100 (thin), with a separate agent-readiness read of 30/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Taurus
Each block below is one kind of artifact we hold for Taurus. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Taurus-PROTECT & Taurus-CAPITAL API
REST API for institutional custody (Taurus-PROTECT) and tokenization / digital asset issuance (Taurus-CAPITAL). Bearer + HMAC request signing, versioned under /api/rest/v1/, cur...
Taurus-EXPLORER API
Blockchain node and indexing services providing normalized access to on-chain data across dozens of supported protocols.
Taurus-PRIME API
Institutional trading infrastructure with deep liquidity and institutional-grade execution, accessible over both a REST API and the FIX protocol.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Taurus Protect Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Taurus — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/taurus · machine-readable index on apis.io