Kraken

Editorial summary aggregated from CoinGecko and CoinMarketCap exchange profiles for Kraken, an exchange operating since 2011.

Key facts about Kraken compiled from verified market data and CoinGecko's exchange registry. These metrics help you evaluate liquidity, regulatory footprint and operational maturity before connecting a portfolio.

Puntuación de Confianza

10/10

Rank #7

24h Volume (normalized)

24.5K BTC

Active markets

100 pairs

Available in

1 jurisdictions

United States

Operating since

2011

15 years

Trading incentives

Not offered

CCXT integration

Supported

kraken

Data source

CoinGecko exchange registry

Kraken is wired into Mantapex through the CCXT integration layer, so importing balances and trade history into a read-only portfolio requires an API key and a secret that you generate inside your own Kraken account. Because Mantapex never custodies your funds, the keys you create should be scoped to read access only — withdrawal, transfer and trading permissions are unnecessary for portfolio tracking and should remain disabled. The trust score and rank shown in the Quick Facts above are sourced from CoinGecko's exchange framework, which blends reported liquidity, web traffic patterns, regulatory posture and API health into a single signal — useful when comparing Kraken to peer venues, but never a substitute for your own due diligence. The headquarters jurisdiction shown above determines the regulatory framework, KYC tier and product mix Kraken can offer a given user, and that scope can change as licensing evolves. Verify eligibility and the local terms of service on the official site before opening an account. The operating history reflected above means there is a comparatively deep public trail of incidents, audits, fee schedules and product launches you can review when sizing Kraken against newer venues.

Connection metadata is read directly from Mantapex's CCXT integration manifest — credential requirements reflect what Kraken itself exposes to read-only API consumers and may evolve as the venue updates its API.

Kraken operates as a custodial trading venue: when you fund an account, the deposited assets are held in wallets controlled by the exchange and credited to your balance as a book-entry until you withdraw them. That trade-off — convenience and order-book liquidity in exchange for counterparty risk — is the central design choice of every centralised exchange and is what makes platform-level security so important to evaluate. Kraken has been running its custody and matching infrastructure since 2011, which gives it 15 years of operational track record for users to review when judging incident history, fund-recovery policy and any insurance or reserve-fund coverage.

Almost every major centralised exchange — including Kraken — operates under some form of KYC ("Know Your Customer") and AML ("Anti-Money-Laundering") obligations imposed by the jurisdiction it serves. Kraken is reported with its operating entity in United States, so its baseline KYC programme follows that jurisdiction's rules — additional verification may still be requested for higher-tier withdrawal or fiat-on-ramp limits, and access to specific products can be restricted depending on where the user resides. Expect to provide a government-issued ID document and a recent proof-of-address at minimum; higher verification tiers may add liveness checks, source-of-funds questionnaires and accredited-investor confirmations.

For the specific case of connecting Kraken to Mantapex, the additional hardening layer is straightforward: generate a dedicated API key for read-only portfolio sync, label it clearly (for example "Mantapex read-only sync"), disable every permission except the minimum the exchange exposes for balance and trade-history queries, and store the secret in a password manager so you can rotate it on a schedule. If Kraken supports IP whitelisting and you connect from a stable address, restrict the key to that address. If you ever stop using Mantapex — or any other third-party dashboard — revoke the key on the exchange side rather than just deleting it from the dashboard, because the credential continues to authenticate against Kraken's API until Kraken itself invalidates it.

Security guidance on this page is generic exchange hardening that applies to every centralised crypto venue. For Kraken's exchange-specific policies — fund-segregation model, proof-of-reserves cadence, insurance coverage and incident-response history — the canonical references are Kraken's own Help Centre and any audit reports or attestations the venue publishes directly.

Connecting Kraken as a read-only portfolio source on Mantapex relies on the credentials defined by Kraken's own API. The matrix below mirrors exactly what the CCXT integration layer asks for — ticked rows mean the field is required to authenticate, untouched rows mean Kraken doesn't ask for that field at all.

In short, Kraken requires 2 credentials to authenticate API requests: Clave API and Secreto de API. All of these are generated from inside the exchange's own dashboard — Mantapex never asks you to share your account password or to set up an API key with withdrawal permissions enabled.

When you create the key on Kraken for use with Mantapex, restrict its permissions to read-only access (sometimes labelled "view", "read", "query" or "info"). Mantapex only needs to fetch balances, trade history and open positions. Withdrawal, trade-execution and transfer scopes should remain disabled. If Kraken offers a granular permission model, the safest combination is: enable "Read" or "View", disable "Trade" or "Spot trade", disable "Withdraw" or "Universal Transfer", and leave any margin / futures permission switched off unless you specifically want those positions visible inside your portfolio dashboard.

Some exchanges — Binance, OKX, Bybit, Bitget, KuCoin and several Asia-Pacific venues — offer an optional IP whitelist when you create the API key. Leaving the whitelist empty lets the key authenticate from any address, which is the simplest setup for use with a cloud-hosted dashboard such as Mantapex. If Kraken forces you to enter at least one IP and you don't have a static address, you can usually use a placeholder value the exchange recognises (for example "0.0.0.0/0" or the wildcard option) — consult Kraken's API documentation before relying on that workaround. Either way, the credentials remain in a read-only scope and cannot be used to move funds off the venue.

Credential schema sourced directly from the CCXT integration manifest used by Mantapex. Kraken may rotate or extend its API in the future — if the exchange asks for a credential not listed here when you create the key, you can safely ignore it for the purpose of a read-only Mantapex import.

The links below point to first-party Kraken properties. We track them so you can verify announcements, support channels and operator-published policies directly at the source rather than from third-party copies. External destinations open in a new tab and are marked nofollow per our resource-link policy.

• Sitio web oficial de Kraken

  kraken.com

Principales exchanges por puntuación de confianza

Binance

Cayman IslandsConfianza 10.0/10234.6K BTC

Bybit

British Virgin IslandsConfianza 10.0/1049.6K BTC

Gate.io

PanamaConfianza 10.0/1047.4K BTC

Coinbase

United StatesConfianza 10.0/1043.7K BTC

Coinbase

United StatesConfianza 10.0/1043.7K BTC

Bitget

SeychellesConfianza 10.0/1035.4K BTC

MEXC

SeychellesConfianza 9.0/1070.2K BTC

KuCoin

SeychellesConfianza 9.0/1064.8K BTC

Otros exchanges en United States

Coinbase

United StatesConfianza 10.0/1043.7K BTC

Coinbase

United StatesConfianza 10.0/1043.7K BTC

Gemini

United StatesConfianza 9.0/102.0K BTC

Binance US

United StatesConfianza 8.0/10287 BTC

Peer sets sourced from CoinGecko's trust-score ranking and CCXT's exchange manifest. Inclusion here is not an endorsement — it simply means Mantapex tracks the venue with current trust / volume data.