Do I need SSL to test injection in Chainlit locally?

No. Set useSSL to false against a localhost server for development, and enable SSL with your production host for release.

Will local testing show real ads in Chainlit?

That depends on your local ad-server setup and available inventory. TODO_VERIFY: confirm the recommended local/sandbox ad configuration with Monetzly.

How-to guide

How to Test Ad Injection Locally in Chainlit

This guide shows how to test ad injection locally in a Chainlit app, the goal being to run injection against a local/non-SSL server during development. It builds on the Monetzly gRPC service (no Python SDK exists for this stack), so the approach is specific to how Chainlit produces and streams responses.

Overview

You can develop ad injection for a Chainlit app locally before going to production. Point the SDK at a local ad-server address and turn SSL off; everything else — the injection call, session context, fallback — behaves the same as production.

This lets you verify that your Chainlit stream flows through injection and reaches the client correctly without needing production credentials wired up.

Chainlit apps are usually built for chat UIs for LLM apps, agent demos, and RAG chat frontends, so test ad injection locally typically comes up while a user is mid-conversation, the moment where monetization has to be additive rather than disruptive.

How this works on Chainlit

Chainlit is Python. Drive the shipped tps_alter.proto gRPC service (or a Node sidecar) and stream injected tokens into a Chainlit Message via msg.stream_token(). Confirm the non-JS auth handshake before publishing.

Since Chainlit is a Python stack with no official SDK, this task runs through the shipped tps_alter.proto gRPC service (or a Node sidecar); the auth handshake for a direct client is still TODO_VERIFY.

Steps

Set the server address to your local host (e.g. localhost:8080) and disable SSL.
Run your Chainlit app and send a test prompt through the injection path.
Confirm tokens stream to the client, then switch to your production host and SSL for release.

Integration snippet

TODO_VERIFY: Chainlit uses the gRPC proto path, confirm the auth handshake with Monetzly before relying on this in production.

# No Python SDK. Generate stubs from tps_alter.proto and drive ProcessStream
# (see the FastAPI page for the full bidi loop), then in a Chainlit handler:
#
#   msg = cl.Message(content="")
#   async for token in inject(llm_tokens, prompt, session_id, api_key):
#       await msg.stream_token(token)
#   await msg.send()
#
# TODO_VERIFY: auth handshake (API key placement) for a direct gRPC client.