Marketplace

Use createMarketplaceClient with the selected network. Catalog reads are public. Trades and order changes need your backend’s builder key and the acting EOA’s signature; they do not need a Renaiss account or wallet access token.

Browse and price a card

Use listMarketplaceCards().firstPage() for the catalog, fetchCard({ tokenId }) for details and fetchCardOrders({ tokenId }) for its live ask and funded bids. Refresh orders before presenting a trade for confirmation. The SDK network constants specify the platform fee, currently 200 basis points (2%). Use the API’s prepared quote for the exact total and seller proceeds. Do not treat an estimated card value as an executable price.

Trade actions

SDK method	Inputs to review
`createAsk`	Card and either `totalPriceInUsdt` or `sellerReceivesInUsdt`, not both
`createBid`	Card and `amountInUsdt`
`buyCard`	Card and the displayed ask’s `expectedTotalPriceInUsdt`
`acceptBid`	Card, `bidId` and the displayed bid’s `expectedTotalPriceInUsdt`
`cancelOrder`	`orderId` belonging to the signing wallet

These methods prepare the action, validate it, request the signature and submit it. The SDK checks the selected chain, contracts, token, spender, fee, price and expiry before signing. Orders default to 30 days and may specify an expiry up to one year. The following function runs after your app has shown the price and checked wallet approvals:

import {
  getError, getValue, isFailed, type MarketplaceClient,
} from '@renaiss-protocol/client';

export async function buyReviewedCard(
  marketplace: MarketplaceClient,
  tokenId: string,
  reviewedTotalInUsdt: bigint,
) {
  const result = await marketplace.buyCard({
    tokenId,
    expectedTotalPriceInUsdt: reviewedTotalInUsdt,
  });
  if (isFailed(result)) throw new Error(getError(result).detail);
  return getValue(result);
}

A changed price must return the user to price review. Do not retry using a replacement price the user has not seen.

Contract approvals

Buyers and bidders need USDT allowance to Permit2. Check it against the token and spender in the selected network constants before starting the action, and wait for any approval transaction to confirm. The current seller flow authorizes transfer through the signed ask; it does not require a separate NFT approval transaction. Approvals are separate on-chain transactions handled by your wallet library. A sufficient existing allowance can be reused; the SDK does not automatically grant unlimited spending. A bid’s balance and allowance may later become insufficient, including when another order spends from the same wallet.

Cancel an order

cancelOrder signs a short-lived cancellation and removes the order from the API’s order book. It does not revoke the underlying Ask or Permit2 signature. Invalidating a bid’s Permit2 nonce is a separate on-chain wallet operation; the SDK does not perform it. See the contract addresses.

Recover an uncertain trade

After a timeout or lost response, check the returned transaction hash when available, on-chain ownership and the refreshed order book before resubmitting. An HTTP error alone does not prove that settlement failed. Prevent duplicate submissions while reconciliation is pending.

Getting started

Build a flow

Reference

Partner integrations

Browse and price a card

Trade actions

Contract approvals

Cancel an order

Recover an uncertain trade

​Browse and price a card

​Trade actions

​Contract approvals

​Cancel an order

​Recover an uncertain trade

Browse and price a card

Trade actions

Contract approvals

Cancel an order

Recover an uncertain trade