# Any AI Proxy API

Any AI Proxy API is a self-hosted gateway that exposes browser-only AI services as an OpenAI-compatible API endpoint. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5810/any-ai-proxy-api

## Description

Any AI Proxy API is a self-hosted gateway that exposes browser-only AI services as an OpenAI-compatible API endpoint. It drives the provider's web interface automatically so existing OpenAI clients, scripts, and agents can call other models without an official developer key. It suits homelab users who want to route multiple AI providers through one consistent API format.

## Platform availability

Available on 0 of 10 platforms.

## Health score

43/100 (Fair), based on 4 of 5 factors.
- Maintained: 72 (last commit 32 days ago)
- Popular: 29 (27 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Security check: 20 (1 serious finding, 4 minor, CI)

## Security check

1 serious finding: Uses proxy-addr 2.0.7, which has a known critical vulnerability.
Automated checks on commit fec7690, 16 Nov 2026. Not an audit.

## Links

- GitHub: https://github.com/AI-QL/api-proxy
- Docker Hub: https://hub.docker.com/r/eceasy/any-ai-proxy-api
- Official website: https://api.aiql.com/

## Common questions

### How do I start the default Docker instance and change its port or target?

Run the Docker image with port 9017 mapped to the container. You can override the server port and target endpoint with the PORT and TARGET environment variables; the defaults are 9017 and the OpenAI API target.

### Can I send a custom Host header to a backend whose domain differs from the URL?

Yes. Set the HOST environment variable to define a different Host header. If it is not set, the host is inherited from the target URL.

### Can the proxy expose a backend that does not include CORS headers?

Yes. It is intended to bypass CORS restrictions so private APIs without CORS headers can be accessed through the proxy.

### Does it support bypassing TLS certificate validation for internal self-signed certificates?

Yes. It lists TLS certificate validation bypass as a use case for enterprise internal self-signed certificates. The SECURE variable defaults to true to enable TLS validation security features.

### I was using the older Docker image; is it still available after the current release?

The previous Docker image for version 2.0.0 and below is still available at the old image name. The current repository uses the api-proxy image for new deployments.

---
Source: Our Local Host (https://ourlocalhost.com/app/5810/any-ai-proxy-api), the self-hosted and open-source app directory.
