Meerkat Agents The official Ruby client for Meerkat Cloud Change Intelligence. Rails applications often need to detect meaningful changes across the systems they depend on—websites, APIs, databases, internal services, SaaS tools, inventory systems, shipment providers, or other connected data sources. Building these monitoring loops yourself usually means maintaining polling jobs, cron schedules, background workers, state comparisons, retries, LLM orchestration, and webhook infrastructure. Meerkat runs the monitoring loop in the cloud and sends structured change events back to your Rails application. How it works 1. Create a monitoring task from Ruby. 2. Describe what to monitor in plain English. 3. Provide the relevant URLs, data, or connected system inputs. 4. Define how often the task should run. 5. Meerkat checks the source repeatedly, compares the latest result with previous state, and identifies meaningful changes using your own LLM key. 6. When something changes, Meerkat POSTs a signed JSON event to your webhook, with automatic delivery retries. How it differs from Sidekiq, Active Job, Good Job, Solid Queue, Delayed Job, and Resque These libraries are excellent for running your Ruby jobs on your workers. Meerkat is not a background-job queue. It is managed infrastructure for continuously monitoring connected systems and reporting meaningful changes. Instead of building polling jobs, comparison logic, schedulers, scraping code, LLM workflows, and webhook delivery pipelines, you describe what should be monitored and let Meerkat operate the watch loop. Common use cases - Website and page-change monitoring - API response monitoring - Database and application-data monitoring - SaaS and third-party system monitoring - Competitor pricing and plan tracking - Package and shipment tracking - Stock and inventory availability alerts - Recurring data checks with structured findings - Change-detection webhooks for Rails and API backends Documentation: https://cloud.meerkatagents.com/docs/introduction