What makes aigate notable?

2.4K downloads. Trust evidence available

How should aigate be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

aigate

Self-hosted AI platform — one `docker-compose up`, one OpenAI-compatible endpoint at http://localhost:4000. Bundles inference (Groq/Cerebras/OpenRouter/HuggingFace/Mistral/Cohere/Ollama/vLLM/llama.cpp/claudebox/pibox-zai/Anthropic/OpenAI), MCP tool use, a stealth browser cluster, image generation (FLUX/DALL-E/SD), speech synthesis (Kokoro/Qwen3-TTS/Chatterbox/OpenAI TTS), transcription (Whisper/Parakeet), S3-compatible object storage, agentic code execution (Claude Code + pi-coding-agent + sandboxed piston), web search (SearXNG), an email gateway (mailbox), a Telegram client (Telethon), time-series forecasting + tabular ML (predictalot), audio/video production (audiolla/flickies), an async job queue (proxq), and a web UI (LibreChat) — all reachable through one bearer token and automatic per-model fallback routing. Use when the user wants a one-command self-hosted OpenAI-compatible stack that aggregates many providers/tools behind a single endpoint instead of wiring each service up individually.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.4k

Updated

Oct 9, 2026

Version

10.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.4K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.4K downloadsadoption · observed Oct 9, 2026
Latest release: 10.0.0release · observed Oct 8, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17fq93tmpky791n7516jcn08n83sfn2:aigate

Install using `clawhub skill install s17fq93tmpky791n7516jcn08n83sfn2:aigate` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/psyb0t/aigate before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-psyb0t-aigate/snapshot"

Documentation

CLAWHUB

154,244 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: aigate
description: Self-hosted AI platform — one `docker-compose up`, one OpenAI-compatible endpoint at http://localhost:4000. Bundles inference (Groq/Cerebras/OpenRouter/HuggingFace/Mistral/Cohere/Ollama/vLLM/llama.cpp/claudebox/pibox-zai/Anthropic/OpenAI), MCP tool use, a stealth browser cluster, image generation (FLUX/DALL-E/SD), speech synthesis (Kokoro/Qwen3-TTS/Chatterbox/OpenAI TTS), transcription (Whisper/Parakeet), S3-compatible object storage, agentic code execution (Claude Code + pi-coding-agent + sandboxed piston), web search (SearXNG), an email gateway (mailbox), a Telegram client (Telethon), time-series forecasting + tabular ML (predictalot), audio/video production (audiolla/flickies), an async job queue (proxq), and a web UI (LibreChat) — all reachable through one bearer token and automatic per-model fallback routing. Use when the user wants a one-command self-hosted OpenAI-compatible stack that aggregates many providers/tools behind a single endpoint instead of wiring each service up individually.
homepage: https://github.com/psyb0t/aigate
user-invocable: true
permissions:
  network:
    - outbound HTTP to the aigate endpoint (default http://localhost:4000, or wherever it's deployed)
    - aigate itself reaches out to model providers, MCP tool backends, and the open internet on the user's behalf (web search, browser automation, email, Telegram)
  shell:
    - docker / docker compose (bring the stack up/down, read logs)
    - curl (call the OpenAI-compatible endpoint and direct service routes)
metadata:
  openclaw:
    emoji: "🚪"
    primaryEnv: AIGATE_TOKEN
    requires:
      bins:
        - docker
        - curl
---

# aigate — self-hosted AI platform behind one endpoint

A self-hosted AI platform. One `docker-compose up` stands up inference, tool use, browser automation, image generation, speech synthesis, transcription, object storage, agentic code execution, web search, an email gateway, a Telegram client, time-series forecasting, an async job queue, and a web UI — all behind a single OpenAI-compatible endpoint at `http://localhost:4000`. Point any existing OpenAI-client library or `curl` at it and it works. Everything else is opt-in via `.env` flags; the always-on core is nginx, LiteLLM, PostgreSQL, Redis, and the `proxq` async job queue (at `/q/`, no flag needed).

## Security & safety

**This is a very high-capability, very high-blast-radius stack. Treat the endpoint and its token like root on the host.** A single `AIGATE_TOKEN` bearer can, depending on what's enabled:

- Hold API keys/credentials for many cloud model providers (Groq, Cerebras, OpenRouter, HuggingFace, Mistral, Cohere, Anthropic, OpenAI) plus subscription agent backends (Claude Code OAuth/API key, z.ai GLM Coding Plan).
- Execute arbitrary code — three full agentic coding agents (claudebox, pibox-zai, pibox) with shell + file access, plus sandboxed multi-language execution (piston).
- Drive a real browser (stealth Camoufox cluster) that can log

_meta.json

{
  "ownerId": "kn79dhvmpjng4rp2jjk8k0v5xx80ccbk",
  "slug": "aigate",
  "version": "10.0.0",
  "publishedAt": 1791475477433
}

references/setup.md

# aigate setup

Accurate to the aigate `README.md` / `docker-compose.yml` / `.env.example` at time of writing. Re-check those files if this drifts. `.env` and `docker-compose.override.yml` are the operator's local files and are gitignored.

## Bring-up

```bash
git clone https://github.com/psyb0t/aigate
cd aigate
make bootstrap   # creates .env from .env.example (any target does this)
# edit .env — see "Required env" below, then flip service flags to 1
# .env is gitignored. docker-compose.yml is tracked, so put compose changes in
# docker-compose.override.yml, which is gitignored and merges last
make limits      # checks enabled services fit this machine, writes CPU caps to .env.limits
make run-bg      # start detached
# or: make run   # start in foreground with logs
```

`make restart-audiolla` recreates only enabled Audiolla CPU/CUDA variants from their locally available pinned images. It does not rebuild or pull images and leaves other services running.

`make run` / `make run-bg` regenerate `litellm/config.yaml` from fragments (only enabled providers + filtered fallback chains) and pre-flight-validate any file-path env vars (e.g. `MAILBOX_CONFIG`, `CLOUDFLARED_CONFIG`) actually exist before starting containers.

Other Makefile targets: `make down`, `make restart`, `make logs`, `make build-config` (regenerate litellm config only), `make test` (stack must already be running).

## Ports

Single exposed port: **`4000`** (nginx), hardcoded — not env-configurable. Everything else (Postgres, Redis, LiteLLM, and most optional services) binds to no host port at all; they're reached only through nginx's path-based routing on `:4000`. Do not add host port mappings for internal services unless you specifically need direct access.

- Gateway (OpenAI-compatible): `http://localhost:4000`
- LiteLLM admin UI: `http://localhost:4000/ui/`
- LibreChat (if `LIBRECHAT=1`): `http://localhost:4000/librechat/`
- SearXNG (if `SEARXNG=1`): `http://localhost:4000/searxng/`
- Async queue (proxq): `http://localhost:4000/q/`
- Direct-routed services (not via LiteLLM): `/predictalot/`, `/predictalot-cuda/`, `/decidealot/`, `/decidealot-cuda/`, `/audiolla/`, `/audiolla-cuda/`, `/flickies/`, `/flickies-cuda/`, `/mailbox/`, `/telethon/`, `/piston/`, `/storage/` (hybrids3), `/claudebox/`, `/pibox-zai/`, `/pibox/`, `/stealthy-auto-browse/`

## Required env / keys

Core, always needed regardless of which optional services you enable:

| Variable | Purpose |
| --- | --- |
| `AIGATE_TOKEN` | Master bearer token. Every per-service token below defaults to this value when left unset — one token authenticates against LiteLLM, claudebox, pibox-zai, predictalot, decidealot, mcp_tools, stealthy-auto-browse, hybrids3, telethon, audiolla, flickies, talkies, talkies-cuda. Override a specific `*_AUTH_TOKEN` / `*_API_TOKEN` var to scope that service separately. |
| `LITELLM_MASTER_KEY` | Optional override; defaults to `AIGATE_TOKEN` when unset. |
| `POSTGRES_DB` / `POSTGRES_USER` / `POSTGRES_P

skill-card.md

## Description:

Guides developers in deploying and using a self-hosted, OpenAI-compatible gateway for model routing and optional AI tools.

This skill is ready for commercial/non-commercial use.

## Publisher:

[psyb0t](https://clawhub.ai/user/psyb0t)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and engineers use this skill to set up a Docker-based AI gateway and connect clients to model providers and optional tools through one endpoint.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: One bearer token may grant access to code execution, browser automation, messaging, and storage across enabled services.

Mitigation: Enable only necessary services, split per-service tokens, and grant agent access only for explicitly authorized tasks.

Risk: Direct internet exposure of the gateway could expose high-privilege capabilities.

Mitigation: Install only on a trusted host and avoid exposing port 4000 directly to the internet; use a protected access path.

Risk: Gateway, mailbox, and Telegram configuration may contain sensitive credentials.

Mitigation: Keep AIGATE_TOKEN and mailbox/Telethon configuration private and out of committed files.

## Reference(s):

- [aigate ClawHub release](https://clawhub.ai/psyb0t/skills/aigate)
- [aigate setup guide](references/setup.md)

## Skill Output:

**Output Type(s):** [Guidance, Shell commands, Configuration instructions]

**Output Format:** [Markdown with shell and configuration examples]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Deployment and API usage depend on enabled services and operator-provided credentials.]

## Skill Version(s):

10.0.0 (source: ClawHub release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 9h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.