Web Cat API

Created By
Kode-Rexa year ago
The repo for the GPT webcat
Overview

What is Web Cat API?

Web Cat API is a collection of Python-based APIs designed to enhance AI models with web search and content extraction capabilities, enabling integration of web content into AI applications like ChatGPT.

How to use Web Cat API?

To use Web Cat API, deploy the Azure Functions API or the MCP server using Docker, configure the necessary environment variables, and make API calls to extract content or perform searches.

Key features of Web Cat API?

  • Content extraction using the readability library
  • Enhanced text processing for usability
  • Web search capabilities integrated with Serper.dev
  • Compliance with Model Context Protocol (MCP)
  • Support for Server-Sent Events (SSE) and RESTful endpoints
  • Configurable rate limiting to protect the API
  • Backward compatibility through API versioning
  • Docker support for easy deployment
  • Parallel processing for faster responses

Use cases of Web Cat API?

  1. Extracting clean text and images from web pages for AI training.
  2. Enabling web search functionality in AI applications.
  3. Integrating web content into custom GPT models.

FAQ from Web Cat API?

  • What is required to use the search functionality?

A Serper API key is required to access the search capabilities.

  • Can I run the API locally?

Yes! You can test the Azure Functions API locally using the provided curl commands.

  • Is there support for multimedia content?

The APIs are optimized for text and image content and may not accurately represent other multimedia or dynamic web content.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Kode-Rex
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago