Where do I put my Monetzly API key in a Flask app?

In an environment variable (e.g. MONETZLY_API_KEY) read at runtime — never hard-coded in source or shipped to the client.

Do I open a new connection per request in Flask?

Open a connection when a request begins and close it when the response stream finishes. The SDK manages reconnection internally.

How-to guide

How to Set Up the Monetzly SDK in Flask

This guide shows how to set up the Monetzly SDK in a Flask app, the goal being to get the SDK configured and connected before injecting any ads. It builds on the Monetzly gRPC service (no Python SDK exists for this stack), so the approach is specific to how Flask produces and streams responses.

Overview

Before you can monetize a Flask app, the Monetzly client needs configuring and connecting. This is a one-time setup: an API key, the ad-server address, and SSL settings, then a connection you open when a request starts and close when it ends.

Keep the API key in an environment variable, never in source. Use a non-SSL localhost address in development and your real ad-server host in production.

Flask apps are usually built for simple LLM web apps, chat endpoints, and prototype APIs, so set up the Monetzly SDK typically comes up while a user is mid-conversation, the moment where monetization has to be additive rather than disruptive.

How this works on Flask

Same as FastAPI: no Python SDK, so integrate via the shipped tps_alter.proto gRPC service (generate stubs, drive ProcessStream) or a Node sidecar. In Flask, stream the injected tokens back with a generator response. Confirm the non-JS auth handshake before publishing.

Since Flask 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

Install the SDK (or, for a Python Flask stack, generate gRPC stubs from the shipped tps_alter.proto).
Create a config with your API key, server address, and SSL flag.
Open a connection at the start of a request and close it when the response finishes.

Integration snippet

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

# Generate stubs once from tps_alter.proto (shipped in @monetzly/server-sdk):
#   python -m grpc_tools.protoc -I. --python_out=. --grpc_python_out=. tps_alter.proto
# Then drive TPSAlterService.ProcessStream: StartRequest -> TokenRequest* -> StopRequest,
# reading back injected TokenResponses. See the FastAPI page for the full bidi loop.
# In Flask, yield the injected tokens from a streaming Response.
# TODO_VERIFY: auth handshake (API key placement) for a direct gRPC client.