Basis Desk

API feedback

What the RWA API made possible, and six places it got in the way. These are the frictions the live desk works around.

What it made possible

quotes/latest returns each wrapper with issuer and a price in one object. That is the whole product: cluster by underlying, normalize units, score a liquid core, print Prefer / Skip / Wait. Map resolves a tradfi ticker to rwa_id. Info supplies CIK for EDGAR. Issuers name who minted the token. Crypto quotes and OHLCV fill live volume and the 30-day series the RWA family does not have.

Where it got in the way

  1. market-pairs/list on the hackathon Startup key returns venues with price and 24h volume, and omits ±2% depth. The desk lists those venues and will not turn a missing book into a Prefer or a size. A subscription rejection (error_code 1006) is labeled plan-gated.
  2. No underlying NAV or exchange print on the RWA family. The liquid reference is wrapper versus wrapper. Any Yahoo print is a labeled benchmark and is not mixed into the ticket.
  3. No RWA history endpoint. 30-day spread joins each wrapper crypto_id into /v2/cryptocurrency/ohlcv/historical.
  4. Gold units are inconsistent (troy ounce and gram). Gram tokens are scaled before any price sort.
  5. One underlying can be many rwa_ids. Clustering by ticker family is required.
  6. quotes/latest data is sometimes keyed rwa_assets and sometimes assets. Parsers accept both.