What happens to my LlamaIndex.TS response if Monetzly is down?

The SDK falls back to yielding your original token stream, so the user still receives a complete LlamaIndex.TS answer — just without ads for that request.

Do I need a manual fallback in LlamaIndex.TS?

The SDK handles fallback automatically, but wrapping the loop in your usual error handling is still good practice.

How-to guide

How to Handle Ad-Injection Errors in LlamaIndex.TS

This guide shows how to handle ad-injection errors in a LlamaIndex.TS app, the goal being to make sure the user still gets a reply if the ad service fails. It builds on the Monetzly server SDK, so the approach is specific to how LlamaIndex.TS produces and streams responses.

Overview

Monetization should never break your LlamaIndex.TS app. The Monetzly SDK is built for this: if the ad service connection fails or errors mid-stream, it falls back to yielding your original, un-injected token stream, so the user still gets a complete answer.

You should still wrap the injection loop in your normal error handling so a failure degrades to a plain LlamaIndex.TS response rather than a broken request.

LlamaIndex.TS apps are usually built for RAG over private docs, knowledge-base search, and structured data QA, so handle ad-injection errors typically comes up while a user is mid-conversation, the moment where monetization has to be additive rather than disruptive.

How this works on LlamaIndex.TS

Use the TypeScript edition (LlamaIndex.TS) so you stay in the Node runtime the SDK requires. A streaming chat/query engine yields response chunks; map each chunk's text to { content } and pass into sdk.inject(). Confirm the chunk field name against your LlamaIndex.TS version.

Because Monetzly's inject() accepts any async token stream, the LlamaIndex.TS side of this task is just mapping your output to it, no rewrite of your LlamaIndex.TS model call.

Steps

Wrap the injection loop in your standard LlamaIndex.TS error handling.
Rely on the SDK's automatic fallback to the original stream on ad-service failure.
Log injection failures so you can monitor fill and uptime separately from your model.

Integration snippet

import { MonetzlySDK } from "@monetzly/server-sdk";
// import a streaming chat engine from "llamaindex"

const sdk = new MonetzlySDK({
  apiKey: process.env.MONETZLY_API_KEY!,
  serverAddress: process.env.MONETZLY_SERVER_ADDRESS!,
});
await sdk.connect();

const stream = await chatEngine.chat({ message, stream: true });

async function* asChunks() {
  // TODO_VERIFY: confirm the text field (e.g. .response / .delta) for your version.
  for await (const chunk of stream) yield { content: chunk.response ?? chunk.delta ?? "" };
}

for await (const t of sdk.inject(asChunks(), { prompt: message })) send(t.content ?? "");
await sdk.disconnect();