Backend service
Backend service
Use integrationContext: 'backend' when the SDK runs on a server (Node, worker, or bot).
Same as the browser for HTTPS reads and writes. Whether writes are allowed is still mode.
import { createNutrimaticSdk } from '@nutrimatic/sdk'
const sdk = createNutrimaticSdk({
ledgers: [{ id: 'evm:421018', kind: 'evm', chainId: 421018, alias: 'infinite-mainnet' }],
mode: 'read',
integrationContext: 'backend',
})
export async function getPoolTelemetry(venueId: string) {
return sdk.telemetry.getAmmView(venueId)
}Typical uses
- Bots and jobs — poll prices, monitor pools, alert on conditions.
- Analytics — aggregate telemetry across venues and ledgers.
- Custom APIs — wrap SDK reads in your own HTTP routes for your product.
First-day path
Same story as the browser for HTTPS calls: Quick start — First day. On a server you often pass owner explicitly for many addresses — Whose wallet (owner).
First jobs
| Job you are building | Start here |
|---|---|
| Poll prices / pools | Read operations |
| Activity / trade feeds | Activity feeds |
| Execute swaps or LP from a server signer | Write operations · Wallet adapter |
| Query many wallet addresses | Whose wallet (owner) |
Related
| Goal | Start here |
|---|---|
| Write path (quote, swap, LP, settlement) | Write operations |
| Balances, portfolio, stake, farm | Balances · Positions · Staking · Farming |
| Wallet adapter (server-side signer) | Wallet adapter |
| Config | Configuration |