api-check  by october-coder

Front-end API testing tool for OpenAI proxies

created 11 months ago
826 stars

Top 43.9% on sourcepulse

GitHubView on GitHub
Project Summary

API Check is a pure front-end tool designed for testing the availability and performance of various OpenAI API proxies. It caters to developers and users who manage or utilize multiple AI model endpoints, offering detailed insights into response times, model consistency, and API quotas, all while prioritizing data security through client-side operations.

How It Works

The tool operates entirely in the browser, processing API requests and displaying results without sending sensitive data to a server. It supports OpenAI-compatible APIs, allowing users to test liveness, retrieve model lists, check quotas, and perform advanced verifications like temperature and function call consistency. This front-end-only approach enhances data security and simplifies deployment.

Quick Start & Requirements

  • Vercel Deployment: One-click deployment via GitHub. Requires filling backend password in environment variables.
  • Docker Deployment: docker run -d -p 13000:13000 -e PASSWORD=you_password -v you_path:/app/data --name api-check ghcr.io/rickcert/api-check:latest
  • Prerequisites: None explicitly stated beyond a web browser for the front-end. Backend deployment requires Docker or Vercel.
  • Links: Try it

Highlighted Details

  • Supports OpenAI proxy APIs (oneapi, newapi).
  • Features cloud and local storage for configurations.
  • Includes quick chat testing integrated with NextChat.
  • Offers experimental modules for batch testing refresh tokens and session keys.

Maintenance & Community

The project acknowledges contributors like Rick Megasoft and fangyuan99. Further community engagement details (Discord/Slack, roadmap) are not provided in the README.

Licensing & Compatibility

Licensed under the Apache License 2.0. This license is permissive and generally compatible with commercial and closed-source applications.

Limitations & Caveats

The README mentions optional backend deployment and custom domain binding, suggesting the core front-end functionality might rely on a separate backend service for certain features or persistence, though the exact dependencies are not fully detailed.

Health Check
Last commit

3 months ago

Responsiveness

1 day

Pull Requests (30d)
0
Issues (30d)
0
Star History
71 stars in the last 90 days

Explore Similar Projects

Feedback? Help us improve.