SDKs

Is there a published CRX SDK?

No.

There is no published, installable CRX SDK package yet. No npm, PyPI, or crates.io release exists. Until one ships, call the relayer API directly over HTTP and read the chain over RPC.

What do I use instead?

Two things, both already in the repo.

Need	Use	Where
Call the relayer	Plain fetch against the API	CRX API → Get started (~4 min)
Know every endpoint's exact shape	The endpoint registry	frontend/lib/developers/endpoints.ts
Read positions, balances, marks	RPC reads against the core contract	Positions & Settlement API (~3 min)

What is the endpoint registry?

frontend/lib/developers/endpoints.ts — the one description of every relayer endpoint the browser calls. It drives the API explorer, the onboarding's first live call, and the copyable code snippets, so the maker bot, the explorer, and the docs cannot drift apart.

Each entry carries the method, path, whether it needs auth, whether it writes, its fields, and a sample response. It is the closest thing to a typed client today: read it as the contract.

How do I make a call without an SDK?

A fetch against the relayer base URL. The registry generates exactly this shape.

// Public read — no token.
const res = await fetch(`${RELAYER_URL}/makers`);
const makers = await res.json();

// Authenticated read — Bearer token from /auth/login.
const inbox = await fetch(`${RELAYER_URL}/rfq/inbox?maker=${address}`, {
  headers: { Authorization: `Bearer ${token}` },
});

RELAYER_URL is environment-specific (NEXT_PUBLIC_RELAYER_URL). See CRX API → Get started (~4 min) for the base URL and auth.

What about on-chain reads?

Use any standard EVM client — viem, ethers, web3.py, or cast. CRX is live on Sonic Testnet (chain id 14601). Point the client at the network RPC and read the core contract.

The deployed contract addresses: Live deployments (~1 min).

Next: Explorer & On-chain Reads (~3 min) — read venue metrics directly from chain.