Skip to main content
GET
Reports, read live from the chain, which identity registers the market names and what each one gates. Both registers are optional. Without a borrower register, the collateral token’s own compliance alone governs borrowers. Without a provider register, each vault admits depositors through its own register alone. Change the registers with Set Identity Gates.

​
What Each Register Gates

On a current market, the two registers gate different parties at different doors. The borrower register (borrowerRegistry) is examined by the market itself on every openLoan and borrowMore. Repaying, closing a loan, releasing collateral and claiming a surplus are never gated. The provider register (providerRegistry) is not examined by the market. The market takes direct deposits only from the operator wallet and the vaults its admin registered, and asks no register about either. Every registered vault reads the market’s provider register, beside its own register, before it admits a depositor or a share transfer. With no provider register, each vault admits depositors through its own register alone. Redemptions are never gated. Every check is a live isVerified(address) call against the register, so a change on the register side takes effect on the next call. Registers answering a single bool, as ERC-3643 and ONCHAINID-based registers do, and registers answering (bool, uint8), as the Trusset register does, are read alike. A register that cannot answer refuses every party.

​
Gates Built on Verification Profiles

A register can be the eligibility register of one of your verification profiles. It then admits exactly the wallets admitted under that profile, and borrowerProfile or providerProfile names the profile. A register that belongs to no profile of your instance reads null there, which says nothing about whom it admits. A MARKET market lends to professional borrowers only, so its borrower register must qualify as a professional gate: every verification profile that admits wallets to it, on any instance of the market’s network and environment, is limited to professional clients and in the REGISTER mode, and there is at least one. borrowerGateCompliant says whether it qualifies, and borrowerGateProblem says what is missing. While it is false, the API opens no loan and adds no liquidity on the market: Open Loan, Borrow More, Add Liquidity and Register Vault refuse with PROFESSIONAL_BORROWER_GATE_REQUIRED, and so do vault allocations, draw caps and rebalances for the market. See Professional borrowers. borrowerProfile names only a profile of your own instance. A register can also be the eligibility register of a profile of another instance on the market’s network and environment, for example when a lender of record lends against the professional register a deploying instance keeps. borrowerProfileElsewhere is how the lender of record sees that: { professionalOnly: true } when every profile of another instance that admits wallets to the register is limited to professional clients, { professionalOnly: false } when at least one is not. The other instance’s profile is not named, and its key, name and requirements are not disclosed. A profile in the EXTERNAL mode admits nobody through Trusset and is not counted. providerProfileElsewhere does the same for the provider register. Both read null when a profile of your own instance owns the register, which borrowerProfile or providerProfile then names, when no profile of another instance admits wallets to it, and when the profiles could not be read. Profiles of other instances also count for borrowerGateCompliant.

​
Gates Built on Whitelists

A register can be a whitelist: a list created through Create Whitelist that admits exactly the wallets its owner and managers listed and examines no identity. borrowerAccessList or providerAccessList then describes it. A whitelist of your own instance carries id, name, purpose, ownerWallet and own: true. A whitelist another instance keeps carries its address with own: false, and id, name and purpose read null. A whitelist cannot be the borrower gate of a MARKET market and cannot gate a market on the earlier single-register implementation. See Whitelists as gates. accessListSteps offers the market’s lender of record the step that lets it maintain a whitelist gate itself: becoming a manager of the list. There is one entry per whitelist the gates name, while the lender of record is neither the list’s owner nor one of its managers, and none while the market has no lender of record. An offered step carries the setManager transaction for the list owner to sign. A step is withheld, with blocked: true and code: ACCESS_LIST_SHARED, when the list also serves the gate of a market of another lender of record, a vault or a vault group. As manager, the lender could admit and remove wallets there too, so sharedWith names those products and reason explains the alternative. Only products of the instance that keeps the list, of your instance and of the instances that record this market are counted.

​
Older Market Generations

generation: SINGLE_REGISTER marks an earlier implementation that examines borrowers and providers against one register and offers no way to change it. providerRegistry then repeats borrowerRegistry, and upgradeRequired is true. The market admin moves it onto the current implementation with Upgrade Market before the registers can be chosen. A two-register market from before the current generation reports vaultOnlyLiquidity: false and providerGateReadBy: MARKET. When its pool is open to third-party providers (operatorOnlyLiquidity: false), the market itself examines those providers against the provider register, which must then stay installed (providerGateRequired: true).

​
The Previous Trusset ID Register

The Trusset ID Register on Sepolia moved to 0xEf244c4Bd4d71Bd9A30EDF6Edef7CCC72642291a on 10 October 2026. A side still gated on the previous register, 0xE9114c40934f6fB6BB317935156b731f7A86D006, carries retired: true, currentRegistry and note in borrower or provider:
usable stays true, because the register still answers for the wallets verified on it before the move. Every customer verified since is refused at that door. The market admin moves the side with Set Identity Gates.

​
Path Parameters

​
string
required
The market’s record ID, as id on List Markets, not its contract address. See Market IDs.

​
Response Fields

​
object

​
Error Codes