Api200

Created By
API-200a year ago
API 200 is an open source API gateway to simplify 3rd-party integrations. Import endpoints, set up caching, retries, and mocks. Access all services via one URL. Monitor logs, track errors, and get alerts on API incidents.
Overview

What is API 200?

API 200 is an open-source API gateway designed to simplify third-party integrations. It allows users to import endpoints, set up caching, retries, and mocks, providing access to all services via a single URL while monitoring logs and tracking errors.

How to use API 200?

To use API 200, you can either utilize the managed version available on their cloud platform or set up a self-hosted version using Docker. Users can start integrating API endpoints instantly without any setup or infrastructure management by visiting API200.co.

Key features of API 200?

  • Fast API setup with authentication management and response caching.
  • Automatic retries and mock responses.
  • Schema watching for API response changes.
  • Incident detection and comprehensive logging.
  • In-browser Swagger integration and endpoint monitoring.

Use cases of API 200?

  1. Managing multiple third-party API integrations efficiently.
  2. Setting up a mock server for testing API responses.
  3. Monitoring API performance and incidents in real-time.

FAQ from API 200?

  • Is API 200 free to use?

Yes! API 200 is open-source and free to use for everyone.

  • Can I self-host API 200?

Yes! API 200 can be self-hosted using Docker and Docker Compose.

  • What technologies does API 200 use?

API 200 is built using Koa, Redis, Next.js, and Supabase.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
API-200
Star
185
Language
TypeScript
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago