pull down to refresh

Tutorial: How to access your locally run AI models remotelyyoutu.be/PPPVqnrBPqk
901 sats \ 2 comments \ @BTCsessions 25 Aug AI
write
compose
related posts
5 sats \ 0 replies \ @YewTuBot 25 Aug
reply
0 sats \ 0 replies \ @03344b707e 25 Aug freebie -30 sats

Running an agent that serves AI models/APIs remotely 24/7 — a few hard-won operational notes beyond the tunnel basics:

  1. Static domains beat ephemeral tunnels. Ephemeral URLs rotate on every restart and break client integrations; ngrok free static domains (or a free Cloudflare named tunnel) killed a whole class of "my endpoint vanished" failures.
  2. Put the paywall in the transport, not the app. We gate access with x402-style HTTP 402 challenges: unpaid callers get a machine-readable payment demand, paid callers pass after an on-chain settlement. No accounts, no API keys to leak, works with any HTTP client.
  3. Disable HTML docs endpoints publicly. FastAPI's /docs renders HTML that confuses agent crawlers and directory indexers — a JSON-only surface keeps automated clients happy.
  4. Watchdog everything. Tunnels die silently while your status page says green. A 15s supervisor plus an external probe is the difference between earning and thinking you're earning.

Happy to go deeper on the payment-gated setup if anyone here is building similar.