# Overview

The three ways a distributor connects to Yutai, and the kinds of distributor it serves, in one page. If this is your first integration, the [Get started](/docs/get-started) page walks the path to a first call: what to send, who approves it, and how the key reaches you once. Every state below is read when the site is built, from the zones the preview serves, the elements the SDK registers and the routes the site's API answers, so what you read is what Yutai serves today.

Every state on this page is read when the site is built, never retyped by hand: when Yutai ships what a row reading Planned names, the page reads it the same day.

## Ways to integrate

A distributor connects through one way or several: the hosted app, the embedded elements, or the distributor API. Each way carries its own state beside it.

## The hosted holder app Available

Yutai serves the holder app itself: the holder opens it, sees their own credential, tier and benefits, and your site hosts no line of it.

[Open Yutai app](/app)

## The SDK's elements Available

The SDK's elements render Yutai's own components inside your pages, styled with the tokens you set. The elements registered today are in the SDK; each names the docs page that explains it when one stands, and the docs still planned for the rest stand below.

`yutai-credential-card`: Available [Credential card](/docs/credential-card)

`yutai-tier-badge`: Available [Tier badge](/docs/tier-badge)

`yutai-benefits-list`: Available [Benefits list](/docs/benefits-list)

`yutai-benefits-module`: Available [Benefits module](/docs/benefits-module)

## The distributor API Callable today

Your server asks the distributor API for the facts behind your screens, with a key the platform issues. Each call reads the state its route answers, and every path links its own call page, where the call's parameters, its answer and its errors stand.

[GET /v1/eligibility](/docs/api/getWalletEligibility): Callable today

[GET /v1/availability](/docs/api/getBenefitAvailability): Callable today

[GET /v1/registry/companies](/docs/api/listRegistryCompanies): Callable today

[GET /v1/registry/instruments](/docs/api/readRegistryInstrumentFacts): Callable today

[GET /v1/claims/{id}](/docs/api/getClaim): Callable today

[POST /v1/claims/{id}/link](/docs/api/reissueClaimLink): Callable today

[GET /v1/status](/docs/api/getApiStatus): Callable today

[POST /v1/claims/challenge](/docs/api/requestClaimChallenge): Callable today

[POST /v1/claims](/docs/api/recordClaim): Callable today

[GET /v1/fulfilments](/docs/api/listPendingFulfilments): Callable today

[POST /v1/fulfilments/{id}/confirm](/docs/api/confirmFulfilment): Callable today

[POST /v1/connect/sessions](/docs/api/createConnectSession): Callable today

[GET /v1/connect/sessions/{id}](/docs/api/getConnectSession): Callable today

## The kinds of distributor

A distributor is one of three kinds. What Yutai reads, what the distributor sends, how long a holder has held and how a claim is proven differ by the kind. The three kinds, side by side:

| What differs | Self-custody wallet | Custodial exchange or broker | Other platform |

| --- | --- | --- | --- |

| What Yutai reads | The chains the distributor registered: Yutai reads the holder's wallets on them straight from the chain. | The registry instruments the distributor listed: the distributor signs what each account holds, and Yutai reads its signed word. | Nothing yet: no holdings channel stands for this kind, so Yutai reads no holdings from it. |

| What the distributor sends | Wallet addresses: one for each wallet the holder links. Nothing else about the holder. | A pseudonymous user reference for each account, and a short-lived signed statement of its holdings: never a name, an email address or a phone number. | Nothing yet: with no holdings channel, there is nothing for the platform to send about a holding. |

| How long a holder has held | The holding's own chain history, which Yutai reads; when no history stands, the first instant Yutai saw the holding at or above the floor. | The day the distributor's signed statement says the holding began. | Not yet: no holding is read for this kind, so no tenure is counted from it. |

| How a claim is proven | The holder signs a one-time message Yutai issues for the claim. | The distributor's own signature stands beside the claim. | Not yet: with no holdings channel, a claim has no holding behind it to prove. |