DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to point existing AI scripts at a private local API with Poly Strata

Redirect scripts written for the OpenAI or Anthropic API to a model on localhost.

Who it is forA developer or analyst with scripts that call a hosted AI API and who needs to stop sending sensitive text to a third party.

The problemScripts that summarize client notes or internal documents send that text to a hosted provider on every run.

The outcomeThe same scripts keep working, but requests go to a model served on localhost and the text stays on the PC.

What you need first

  • A Windows or Linux PC with an NVIDIA card, or an AMD card with 12 GB or more for Qwen3.8-Flash-Next
  • Enough disk space for the model file you pick, from about 11 GB to 114 GB depending on the model
  • Enough RAM for the model you pick, since large models such as GLM 5.3 Flash and DeepSeek V4 Flash keep most of their file in RAM
  • A coding agent that can point at a custom API base, if you want to use one with the local server

Steps

  1. Install Poly Strata with the one-click installer for your operating system.
  2. Choose one installed model, such as Qwen3.8-Flash-Next if you have a 12 GB card, and start the server.
  3. In your script, change only the base URL to the localhost address and keep the request format the same.
  4. Run the script on one test document and compare the output with what the hosted API returned before.

Prompt for your agent

Take the script at <target script> that calls an OpenAI or Anthropic style API and point its base URL at the PolyStrata server on localhost, using model <model name>. Expected output: the script's summary of <input file> produced without any remote request. Verify that the output is a usable summary and that the network traffic goes only to localhost.

Caveat. Output quality and speed depend on the model and card; the README reports speeds measured on specific PCs, not guarantees for yours.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page