Evez Api Gateway
PassAudited by ClawScan on May 12, 2026.
Overview
This appears to be a straightforward EVEZ API client that uses an API key and sends prompts or image URLs to EVEZ, with only minor credential-declaration and privacy notes.
This skill looks coherent for connecting to the EVEZ API. Before installing, verify that you trust the EVEZ endpoint, use a dedicated EVEZ API key, check the provider's privacy and billing terms, and avoid sending sensitive prompts or private image URLs unless that is acceptable for your use case.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing or using this skill may cause your agent or code to use an EVEZ account key, which can consume quota or incur charges depending on your plan.
The helper client uses an API key to authenticate to the EVEZ endpoint. This is expected for the skill's purpose, but it is a sensitive credential and the registry metadata does not declare a primary credential or required env var.
self.api_key = api_key or os.environ.get("EVEZ_API_KEY", "")
self.client = OpenAI(base_url=BASE_URL, api_key=self.api_key)Use a dedicated EVEZ API key, avoid reusing unrelated OpenAI keys, and confirm which environment variable your workflow should use.
Prompts, system messages, and vision image URLs sent through this client are shared with the EVEZ service.
The client sends chat messages to the external EVEZ API endpoint. This is purpose-aligned, but it means prompt content leaves the local environment.
BASE_URL = "https://evez-api2.fly.dev/v1"
response = self.client.chat.completions.create(
model=model_id, messages=messages, stream=stream
)Review EVEZ's privacy and retention policies before sending confidential data, secrets, private images, or regulated information.