check_api_health
ChatGPTRead-only. Check that the Skipo API is reachable and healthy. Returns status UP when serving normally, or MAINTENANCE when the API is in maintenance and every other route is returning 503 — in that case tell the user to retry later rather than reporting a failure. A 503 service_degraded from a pricing or trading tool while this returns UP means trading is paused and the API itself is up: wait the delay the error states (Retry-After) and retry, rather than reporting an outage. Requires no account data, so use it to diagnose connectivity before other tools.
get_account
ChatGPTRead-only. Get the authenticated Skipo account: fullName, verificationStatus and preferredCurrency. Use this to identify whose account this MCP connection is authorized for. Identity documents and contact details — the national ID (RUT), email and username — are deliberately not returned; the user can see them in the Skipo app.
get_assets
ChatGPTRead-only. List the ASSETS Skipo supports — fiat, stablecoins, crypto AND tokenised equities (public reference data, identical for every key) — or fetch one by asset_symbol. Each entry is identified by assetSymbol (the code to pass wherever a tool wants an asset, e.g. BTC) with assetName as its display name, and carries the CONSTRAINTS on using it: assetClass (FIAT/STABLECOIN/STOCK/CRYPTO), amountIncrement (smallest step Skipo operates on — finer amounts are truncated), displayIncrement (presentation only), minimumDeposit, minimumWithdrawal, minimumInternalWithdrawal, withdrawalFee, maxIndicativeQuoteAmount, rebaseMultiplier, and networks — the chains it can be withdrawn over. Use it to answer "what is the minimum to withdraw X" or "is X a tokenised stock". assetClass=STOCK is the ONLY way to know an asset rebases — never infer that from rebaseMultiplier being 1. ⚠️ An asset can have MORE THAN ONE network, and the fee differs per network. The top-level withdrawalFee is the CHEAPEST network fee, so quoting it for a specific chain can understate the cost badly — on USDT the Tron fee is several times the asset-level figure. When the question names a chain, or the answer will be acted on, read networks[].withdrawalFee for that chain instead. The MINIMUM is per-network too. The top-level minimumWithdrawal is only the PLATFORM floor; a chain can impose a higher one, and the amount actually enforced is the larger of the two. Read networks[].minimumWithdrawal — it is already resolved to the effective figure for that chain. Quoting the asset-level number can name a minimum the chain will reject. The minimum applies to the amount SENT, not the amount debited. On POST /v2/withdrawals the default feeMode is deduct, where amount is the total debited — so the smallest accepted amount on a chain is networks[].minimumWithdrawal + networks[].withdrawalFee. On some assets the fee is at or above the minimum (DOGE charges 5 and permits 5), so compute it rather than assuming. Each entry carries networkId (BSC, ETH, TRON — the stable key, and the field to match against contacts and movements), networkName, networkNativeAsset (the gas asset), evmChainId, assetType (the token standard, e.g. BEP20), withdrawalFee and minimumWithdrawal. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_balance_history
ChatGPTRead-only. Get historical balance snapshots for a single asset over a date range. Use this to chart or describe how a balance trended over time. Choose a granularity (day/week/month) to control the bucket size. Each point is {date, balance}; balance is an exact decimal STRING in plain notation (never exponential), truncated to the asset operating precision — parse it as a decimal, not a float. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_balances
ChatGPTRead-only. Get balances for every asset the account holds (returns the full list, not paginated). Each entry has assetSymbol, balance, balanceFrozen, balancePending, balancePrefCurrency and balanceUSD, plus balanceCapacityTotal/Available/Spent when the asset has credit capacity. Amounts are decimal strings — keep them as strings to preserve precision. balanceUSD is in US dollars whatever the preferred currency, and it values balance alone — balanceFrozen and balancePending are not in it — so summing balanceUSD across entries gives the total SPENDABLE value in USD, not the whole holding. A balanceUSD of "0" beside a non-zero balance means no USD price was available, not a worthless asset. There is no kind-of-asset field here, and joining this assetSymbol to get_assets assetSymbol silently MISSES EVERY TOKENISED EQUITY: this list defaults to the rebased ticker (NVDAX) while get_assets is keyed by the settled code (NVDASPV). Join base.asset (always the settled code, always present) to assets[].assetSymbol, or this assetSymbol to assets[].rebasedSymbol. A single-asset lookup, get_assets(asset_symbol=…), resolves either spelling. balance is the SPENDABLE figure and is already net of the other two — freezing moves value OUT of balance into balanceFrozen, and crediting a deposit moves it out of balancePending into balance. The three never overlap; the whole holding is balance + balanceFrozen. balanceCapacityAvailable is CREDIT capacity, not cash — never add it to a spendable figure. Maximum withdrawable over a chain = balance, sent as amount: POST /v2/withdrawals defaults to feeMode: deduct, where amount is the total DEBITED, so sweeping is one call. The destination then receives amount minus networks[].withdrawalFee for the contact chain's networkId. ⚠️ On a tokenised equity the assetSymbol above is the rebased ticker and that endpoint REJECTS it — withdraw with base.asset and a settled quantity. Each entry also has assetFormat (which representation the amounts are in) and multiplier (the rebase factor as it stands now, '1' when the asset does not rebase). For a tokenised equity the DEFAULT read gives you the underlying equity under the rebased ticker — so a holding may be reported as NVDAx, not NVDASPV. balancePrefCurrency and balanceUSD are denominated in a CURRENCY, not in the asset, so they are the same in either representation: do not scale them by multiplier.
get_contacts
ChatGPTRead-only. List the account's saved withdrawal destinations, or fetch one by contact_id. type is the discriminator and tells you which detail block is present: EXTERNAL_CRYPTO carries crypto (assetSymbol, address, tag, and the chain as networkId/networkName/networkNativeAsset/evmChainId), BANK_ACCOUNT carries bank (assetSymbol, bankName, bankAccountType, and bankAccountNumber MASKED to its last four digits), and INTERNAL carries neither because it has no external destination. The bank account holder is usually someone else, so their national ID (RUT) and email are deliberately not returned. Each contact has id and reference, and BOTH are accepted as the destination on POST /v2/withdrawals, as contactId or contactReference. The asset of a contact is fixed: a withdrawal whose asset does not match its contact is rejected. Contacts cannot be CREATED or deleted through v2 — adding a withdrawal destination is the blast radius if a key leaks, so it stays in the Skipo dashboard behind 2FA. Only the reference is editable (PATCH /v2/contacts/{id}), which relabels a destination rather than changing it. Match a destination to an asset on networkId (BSC, ETH, TRON) — it means the same thing on every tool. crypto.networkSymbol also exists and is LEGACY: it is the raw stored value, it disagrees with itself across the estate (the same chain reads BEP20 on some records and BSC on others), and it is NOT a stable key. Do not match on it. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_deposit_addresses
ChatGPTRead-only. The addresses to send funds TO in order to FUND this account, one per (asset, chain) pair. These are Skipo-owned addresses that credit the balance — the OPPOSITE direction from get_contacts, which lists the external destinations money can be withdrawn to. Do not confuse the two: sending to a contact address does not fund the account. Each entry has assetSymbol, networkId, networkName, address, tag, tagRequired, tagType and tagLabel. Join to an asset or a movement on networkId — the same key everywhere. ⚠️ FOUR ways a deposit is lost, all stated here rather than left to be inferred. FIRST: an address is only valid on the networkId it is listed under. Chains share address formats — every EVM chain does — so the same string can appear under several, and funds sent over a chain Skipo does not sweep do not arrive. SECOND: when tagRequired is true the tag is MANDATORY, because Skipo shares one address across accounts on those chains and the tag is the only thing identifying this one. tagType says which word the chain uses (MEMO or DESTINATION_TAG) as a machine key; tagLabel is the display text. Branch on tagRequired, never on tag !== null — most chains have no tag — and never on tagLabel, which can be null while a tag is still required. THIRD: an EVM address is shared by EVERY token on that chain, so sending a different asset to the address listed for this one parks the funds for manual review. Send only the exact assetSymbol on the row, and if an expected pair is absent do NOT use a neighbouring row address. FOURTH: a deposit below the asset minimumDeposit is NOT rejected, returned or queued — it is swept to a Skipo internal account, producing no deposit row, no webhook and no error. Read minimumDeposit from get_assets before advising any amount, and warn against dust as a connectivity test. All four failures are silent: there is no error response for any of them, and recovery is a manual support case. Addresses are stable — Skipo does not rotate or retire them — and reading this never mints a new one, so re-reading is free. Identify a row by the PAIR (assetSymbol, networkId), not by the address string, which is not unique across chains. A pair with no address yet is ABSENT rather than listed empty. Fiat has no chain and is never listed: asking for CLP returns an empty list, not an error. Amounts are not here: minimumDeposit is on get_assets. ⚠️ ONLY assets the account has ADDED are listed, and this is the most common reason a user says an address is "missing". Skipo pre-provisions an address for effectively the whole catalogue before anyone asks for it, so an address existing does not mean the asset is in use. An asset that has not been added returns an EMPTY list — including when it is named explicitly. Do NOT report that as "you have no address" or as an error: the address already exists and is unchanged. The fix is to add the asset in the Skipo app, or open the deposit screen and select it, after which it appears here on the next call. This is the same set get_balances returns. Returns a bare list, not paginated.
get_deposit_instructions
ChatGPTRead-only. Where to send a BANK TRANSFER to fund this account in CLP — the fiat counterpart of get_deposit_addresses, which covers crypto. ⚠️ THE TRANSFER MUST COME FROM A BANK ACCOUNT IN THE USER OWN NAME AND RUT. Skipo matches an incoming transfer to an account by the originator RUT the bank reports, and there is no reference code, no memo and no per-customer account number to fall back on. A transfer sent from anyone else's account — a company account for a personal balance, a partner, a friend, a payment processor — CANNOT be matched and is NOT credited; recovering it is a manual support case. Tell the user this BEFORE they transfer, every time. The RUT that has to match is the one on their own Skipo account; it is not returned by any tool. Each entry has assetSymbol, accountHolder, accountHolderNationalId, bankName, accountType, accountNumber, accountEmail and mustMatchSenderNationalId. accountHolderNationalId is SKIPO’s RUT — the destination — not the RUT the money has to come from. More than one account is returned and they are INTERCHANGEABLE: a deposit into any of them credits the same balance. Prefer the one at the user own bank — a same-bank transfer in Chile settles faster and costs less. CLP only; there is no USD bank account. Crypto funding is get_deposit_addresses. Amounts are not here: minimumDeposit is on get_assets. Returns a bare list, not paginated.
get_deposits
ChatGPTRead-only. List the account's deposits (incoming funds), or fetch one by transaction_id. Each deposit has id, subType, assetSymbol, amount, fee, total, status, createdAt, and a depositData block with source details. Statuses are PENDING, IN_PROGRESS, COMPLETED, FAILED — that is the complete set, and the last two are terminal. total is what was credited; fee is always "0" because Skipo charges no deposit fees, and exists only for shape parity with withdrawals. For an EXTERNAL_CRYPTO movement that block carries the chain it settled on as networkId/networkName/networkNativeAsset/evmChainId/assetType — the same fields get_assets and get_contacts use, so all three join on networkId. The legacy networkSymbol is no longer published here. It also has assetFormat (which representation the amounts are in), multiplier, and a base block holding the settled figures. Amounts are decimal strings. A fiat bank deposit additionally carries bankReference and valueDate, both null on a crypto deposit and on a fiat deposit an operator created by hand. WHO sent a bank transfer — the sender name, national ID (RUT) and account number — is deliberately not returned; the user can see it in the Skipo app. Never guess or state who sent a deposit. ⚠️ valueDate is when the money MOVED; createdAt is when Skipo credited it. Use valueDate to reconcile a month-end — on prod the two land in different months about once in 27 months, and the median gap is 91 seconds. The date FILTERS on this tool bound createdAt, not valueDate, so a month-end query still needs the value date read back and checked. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_fills
ChatGPTRead-only. List the account's FILLS (executions) across ALL convert orders, newest first. Use this when the question spans orders ("what did I trade last week", "every BTC fill"); use get_order_fills when you already have one order id. Filter by order_id, market, asset (matches either leg), side or date range. Each fill has id, orderId, sequence (1-based position within its order), side, market, baseAsset, quoteAsset, baseAmount, quoteAmount, rate, multiplier, onCredit, executedAt, and order (the owning order's cumulative status/filledBaseAmount/filledQuoteAmount, so you do not need a second call to see how much of the order is done). A fill id IS the id its ledger entries carry as source.id, so use it to reconcile against the ledger. Amounts are positive-magnitude decimal strings — keep them as strings to preserve precision. CURSOR-PAGINATED: follow pagination.nextCursor until it is null; a short page is not the end.
get_indicative_price
ChatGPTRead-only. Get an INDICATIVE (non-binding) price for a Skipo market — the rate, and the converted amount, for buying or selling. Use it to answer "what rate would I get on BTC-CLP" or "how much CLP is 0.1 BTC worth right now". This is NOT a quote and cannot be executed: nothing is reserved, there is no order id and no expiry. This connector is read-only and cannot place orders or move money at all. Do not tell the user their order has been placed or priced for execution. To actually trade, two REST calls, and they do NOT need the same credentials. Obtaining a confirmable quote is POST /v2/quotes — an ordinary Tier-1 bearer key plus the trading:write scope, NOT a signed request. Executing that quote is POST /v2/orders, which additionally requires a Tier-2 signed request. Saying a quote must be signed sends the caller off to build Ed25519 signing they do not need for that step. COST: this tool charges 10 rate-limit points per call, against 1-3 for every other tool — it reaches an external pricing provider. On this connection's budget of 600 points/minute that is about 60 calls a minute, shared with everything else. Do not loop it; price the sizes you actually need. Skipo prices a dealer spread, so the rate depends on size and does NOT scale linearly. Pass amount + amount_asset to price a specific size; omit both and the price is for the market MINIMUM — do not multiply that up to a larger amount. amount is capped by the asset's maxIndicativeQuoteAmount (from get_assets); above the cap the call is rejected and the error states the limit. If pricing fails for the requested size, report that rather than substituting a rate from another source. The response echoes assetFormat, so you never have to infer the units. For a tokenised equity the DEFAULT prices the underlying equity — real shares — and both the amount you send and the baseAmount and rate you get back are in that representation. quoteAmount is unaffected either way, and so is the market id: it names an instrument pair, not a quantity.
get_ledger
ChatGPTRead-only. The double-entry record of how a balance changed, for ONE asset (required) — the authoritative reconciliation surface. Every entry carries source:{type,id} naming the withdrawal, deposit or fill that caused it, and source.id is exactly the id that resource publishes, so you can go straight from a withdrawal to its ledger entries. Pass source_id to fetch only the entries of one resource, or order_id to fetch every entry an order produced across all of its fills (an order settles in TWO assets, so asset_symbol picks the leg). Each entry has id, source, type (BUY/SELL/DEPOSIT/WITHDRAWAL), subType, assetSymbol, detail, amount, fee, total, balance and createdAt. amount/fee/total are positive-magnitude decimal strings; balance is the SIGNED running balance after the entry, because it is a state and not a movement. Keep them as strings to preserve precision. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_markets
ChatGPTRead-only. List the tradable markets (asset pairs) Skipo supports, or fetch one by market. Each market carries baseAsset/quoteAsset, type (CRYPTO-CRYPTO/CRYPTO-FIAT/FIAT-FIAT), the minimum per denomination leg (minBaseAmount/minQuoteAmount — which applies depends on the asset you denominate the amount in), the amount step per leg (baseIncrement/quoteIncrement), and tradingDays as ISO weekday numbers (1=Monday; null means it trades every day). Use it to answer "what is the minimum order size on BTC-CLP" or "does this market trade at weekends". NOTE type does NOT identify a tokenised-equity market — those are CRYPTO-FIAT too; read assetClass on the asset instead. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_order_fills
ChatGPTRead-only. List the FILLS (executions) of ONE convert order — pass the order id. A normal convert has exactly one fill; an on-credit (capacity) order has several as the debt is paid down. Each fill has id, orderId, sequence (1-based position within its order), side, market, baseAsset, quoteAsset, baseAmount, quoteAmount, rate, multiplier, onCredit, executedAt, and order (the owning order's cumulative status/filledBaseAmount/filledQuoteAmount, so you do not need a second call to see how much of the order is done). A fill id IS the id its ledger entries carry as source.id, so use it to reconcile against the ledger. Amounts are positive-magnitude decimal strings — keep them as strings to preserve precision. CURSOR-PAGINATED: follow pagination.nextCursor until it is null; a short page is not the end.
get_orders
ChatGPTRead-only. List the account's convert orders. One order is created per confirmed quote and is filled by one or more fills. Each order has id, status (NEW/PARTIALLY_FILLED/FILLED/FAILED), side (BUY/SELL), market, baseAsset, quoteAsset, baseAmount, filledBaseAmount, quoteAmount, filledQuoteAmount, rate, multiplier, onCredit, createdAt. Amounts are positive-magnitude decimal strings — keep them as strings to preserve precision. Filter by market, side, status, base_asset/quote_asset, or date range. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
get_server_time
ChatGPTRead-only. Get Skipo's current server time. Use this to check clock skew before time-sensitive operations, or to anchor relative date filters ('last 24 hours') to the server's clock rather than the local one.
get_withdrawals
ChatGPTRead-only. List the account's withdrawals (outgoing funds), or fetch one by transaction_id. Each withdrawal has id, subType, assetSymbol, amount, fee, total, status, createdAt, and a withdrawalData block with destination details. For an EXTERNAL_CRYPTO movement that block carries the chain it settled on as networkId/networkName/networkNativeAsset/evmChainId/assetType — the same fields get_assets and get_contacts use, so all three join on networkId. The legacy networkSymbol is no longer published here. It also has assetFormat (which representation the amounts are in), multiplier, and a base block holding the settled figures. Statuses are PENDING, IN_PROGRESS, COMPLETED, FAILED — that is the complete set, and the last two are terminal. In-flight therefore means PENDING or IN_PROGRESS: query both, or omit status and filter client-side. amount is what the destination receives; fee is Skipo's flat fee, NOT the blockchain network fee, which Skipo absorbs; total = amount + fee and is what leaves the balance. Sum total for outflow, never amount. PAGE-PAGINATED: returns at most limit items — default 25, max 100. Read pagination.totalItems and pagination.totalPages and request the next page until you have them all. NEVER answer a total, a count, or an "is X supported" question from a single page. For the reference lists (get_assets, get_markets) pass limit: 100.
check_api_health
Claudeget_account
Claudeget_assets
Claudeget_balance_history
Claudeget_balances
Claudeget_contacts
Claudeget_conversion_orders
Claudeget_conversions
Claudeget_currencies
Claudeget_deposits
Claudeget_fills
Claudeget_indicative_price
Claudeget_ledger
Claudeget_ledger_movements
Claudeget_markets
Claudeget_order_fills
Claudeget_orders
Claudeget_server_time
Claudeget_withdrawals
Claude