How are self-custody wallets handled?

By public address, read from chain. The user pastes an address during the Link flow and balances are read through a configurable JSON-RPC endpoint. There is no private key anywhere in the system and no signing path, so the integration is read-only by construction rather than by policy. It also works in live mode with no provider agreement at all — you set one RPC URL and it runs.

Do exchange and brokerage holdings really come back in the same shape?

Yes. Each holding carries security metadata — id, ticker, name, type and close price — plus quantity, cost basis and value, whether the upstream was a brokerage, a custodial exchange or a wallet address. Normalizing that is the point of the layer: your allocation chart should not care which venue a position came from.

How do users connect an exchange?

It depends on the venue and both patterns are supported. Coinbase is an OAuth application you register yourself in about five minutes. Kraken needs nothing from you at all — users paste their own read-only API key during the Link flow, so the credential is theirs and scoped to reading. Whichever pattern applies, your integration code is identical.

Is net worth actually computed, or do I aggregate it myself?

Computed. /v1/assets/get returns total_assets, total_liabilities and net_worth across the accounts behind that token, so a portfolio view does not need its own accounting layer. If you want the components, the same response carries the accounts it summed.

Can I show price movement and performance?

Holdings carry a close price and cost basis, and the investment transactions endpoint returns buys, sells, dividends and fees over a date range — which is what performance calculations need. The platform is not a market data feed: intraday quotes, historical price series and corporate actions are outside its scope, and you would pair it with a market data provider for those.

What does the catalogue cover on the crypto side?

50 crypto exchanges and 30 wallets sit alongside 89 investment platforms in the catalogue. As always, a catalogue entry is a routable institution rather than a promise it is connectable today — that depends on which provider credentials are configured, and wallets are the exception because public-address tracking needs no provider.

Crypto and wealth

The crypto half stops being a separate product.

Brokerage positions, custodial exchange balances and self-custody wallets return the same holdings shape — security metadata, quantity, cost basis, value — and net worth is computed across all of it. One integration instead of a bank vendor, an exchange vendor and a chain indexer.

Create a sandbox key Read the docs

who this is for

Three vendors, one number.

Portfolio and wealth products that have to include the crypto half

Wealth products fragment along infrastructure lines. Banks come from an aggregator, brokerages sometimes from the same one and sometimes not, exchanges each have their own API, and self-custody wallets need a chain indexer. Four integrations, four data models, and a net worth figure assembled by hand in your own code.

The user does not experience it that way. They have money in several places and they want one number, one allocation chart, and a history that does not stop at the bank boundary.

Here every venue routes through one Link flow and returns one set of shapes. Adding a venue is a connection, not a project — and the wallet path needs nobody's permission because reading a public address is not a regulated activity.

what you'd call

The endpoints this actually uses.

Holdings and balances are the core; the search endpoint matters more here than elsewhere, because a crypto onboarding should not surface regional banks.

Endpoints used by crypto and wealth integrations
POST	/v1/investments/holdings/get	Positions with security metadata and cost basis
POST	/v1/investments/transactions/get	Buys, sells, dividends and fees over a range
POST	/v1/assets/get	Total assets, liabilities and net worth in one response
POST	/v1/accounts/get	Cash balances alongside positions
POST	/v1/accounts/balance/get	Refreshed balances for a live portfolio view
POST	/v1/institutions/search	Typed search: exchanges, wallets, brokerages
POST	/v1/link/token/create	One flow for banks, brokerages, exchanges and wallets
POST	/v1/items/refresh	Pull fresh valuations on demand

in code

What the integration looks like.

Aggregating across venues first, then the totals and history a portfolio view needs.

tsportfolio.ts

import { FeelConnect } from "@feelconnect/node"; const fc = new FeelConnect({  apiKey: process.env.FEELCONNECT_SECRET_KEY!,  baseUrl: "https://connect.feels.money/v1",}); // A brokerage, an exchange and a hardware wallet are three very// different upstreams and one response shape. Holdings carry security// metadata, quantity, cost basis and value regardless of source.export async function portfolio(accessTokens: string[]) {  const pages = await Promise.all(    accessTokens.map((access_token) => fc.investments.holdings({ access_token }))  );   const holdings = pages.flatMap((page) => page.holdings);   const byAssetClass = new Map<string, number>();  for (const holding of holdings) {    const key = holding.security.type; // equity | etf | crypto | cash | bond    byAssetClass.set(key, (byAssetClass.get(key) ?? 0) + holding.value);  }   return { holdings, byAssetClass };}

tsnet-worth.ts

// Net worth across everything the user connected, computed for you.const { total_assets, total_liabilities, net_worth } = await fc.assets.get({  access_token: accessToken,}); // Trades, dividends and fees when you need performance rather than a// point-in-time snapshot.const { investment_transactions } = await fc.investments.transactions({  access_token: accessToken,  start_date: "2026-01-01",  end_date: "2026-07-01",}); // Let the user find the right venue: search is typed, so a crypto// onboarding never makes someone scroll past a regional credit union.const { institutions } = await fc.institutions.search({  query: "",  types: ["crypto_exchange", "crypto_wallet", "investment"],}); console.log(net_worth, total_assets, total_liabilities);console.log(investment_transactions.length, institutions.length);

what you get

Mechanisms, in the order you would meet them.

One holdings shape across every venue
Security id, ticker, name, type, close price, quantity, cost basis and value — identical whether the source was a brokerage, an exchange or a wallet address.
Self-custody without custody
Wallets are tracked by public address through a configurable RPC endpoint. No private key exists anywhere in the system, and there is no signing path to abuse.
Both exchange auth patterns
OAuth where the venue supports it, and user-supplied read-only API keys where it does not — collected inside the same Link flow, with identical code on your side.
Net worth computed, not assembled
/v1/assets/get returns totals and net worth across connected accounts, so your portfolio view does not carry its own accounting layer.
Typed institution search
Filter by type and country so a crypto onboarding shows exchanges and wallets, and a retirement onboarding shows brokerages.
Holdings webhooks
holdings.updated tells you when a portfolio moved, signed and retried like every other event.

questions

Straight answers.

Other use cases

Show the whole picture, including the awkward half.

Connect a sandbox brokerage, an exchange and a wallet address and watch three very different upstreams return the same holdings array. No agreement required to try it.

Create a sandbox key Contact sales

The sandbox needs no approval and no card. You can have the shapes in front of you in a few minutes and decide from there.