meerkat-agents 0.3.6 → 0.3.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +8 -0
  3. data/lib/meerkat/version.rb +1 -1
  4. metadata +49 -9
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 2402b329cac4ff6816f622c721f704f85ef8643cbdd6f96e977c17c9cf5371a0
4
- data.tar.gz: 8f8c1308e57434a1f098fe2691d7789e68173764cdb8a4fbf0b266855705d7fa
3
+ metadata.gz: 8931270a622f63c7e979beeca840cc4ace19f06cbb4c869f1ef573675e7e2d65
4
+ data.tar.gz: 884b364930c7a2991cf787d5a07e1e234cb12fea51e385f12acf5d80abbf3d05
5
5
  SHA512:
6
- metadata.gz: 41afc5d5dd213677aaefaca2ad8b0b12b3a98e433a4ce6f134a90e1bea713538a20a366b65ce01dac2198b45a13663da661549045f9ac55319e703941ac2a97e
7
- data.tar.gz: ff6050be0d456b1b58bbf13c591ff67d5d99b25cc2ffaae96222ca6bd436d7e0cdf02498933910a124bc9147c67e4bc4aaac0142ddbdfb5fc3efd3d9688cd717
6
+ metadata.gz: 7556beab603f0d810015ad5df9703136a9354163dbe6599a2152fdb310f5153f1f10f48890478d7c011c661443f7dedfe681798fa9ed29cfeae65779057c8f1e
7
+ data.tar.gz: f070fe107fc0f24a2146f2d08ee940167bd915be6658acb063029169485f490247abc6fde655344b24015821d9a4cce8649fe4986778057db989225e12f8bb1c
data/CHANGELOG.md CHANGED
@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [0.3.7] - 2026-07-17
9
+
10
+ ### Changed
11
+
12
+ - Expanded RubyGems description: Change Intelligence positioning, how it works,
13
+ difference from job queues, and common use cases (RDoc headings + lists)
14
+
8
15
  ## [0.3.6] - 2026-07-17
9
16
 
10
17
  ### Changed
@@ -84,6 +91,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
84
91
  - Webhook HMAC-SHA256 verification helpers
85
92
  - Optional Rails railtie and webhook verification concern
86
93
 
94
+ [0.3.7]: https://meerkatagents.com/changelog
87
95
  [0.3.6]: https://meerkatagents.com/changelog
88
96
  [0.3.5]: https://meerkatagents.com/changelog
89
97
  [0.3.4]: https://meerkatagents.com/changelog
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Meerkat
4
- VERSION = "0.3.6"
4
+ VERSION = "0.3.7"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: meerkat-agents
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.6
4
+ version: 0.3.7
5
5
  platform: ruby
6
6
  authors:
7
7
  - Tiny Bubble Company
@@ -33,16 +33,56 @@ dependencies:
33
33
  description: |
34
34
  == Meerkat Agents
35
35
 
36
- The official Ruby SDK for Meerkat Cloud.
36
+ The official Ruby client for Meerkat Cloud Change Intelligence.
37
37
 
38
- Define monitoring tasks in plain English, run them on demand or on a
39
- schedule, and receive structured results through your dashboard or webhook.
38
+ Rails applications often need to detect meaningful changes across the
39
+ systems they depend on—websites, APIs, databases, internal services, SaaS
40
+ tools, inventory systems, shipment providers, or other connected data
41
+ sources.
40
42
 
41
- Use it to monitor pricing pages, delivery statuses, competitor changes,
42
- internal systems, APIs, database-driven workflows, and other business events
43
- without building custom polling, diffing, retry, and scheduling infrastructure.
43
+ Building these monitoring loops yourself usually means maintaining polling
44
+ jobs, cron schedules, background workers, state comparisons, retries, LLM
45
+ orchestration, and webhook infrastructure.
44
46
 
45
- Documentation: https://meerkatagents.com/docs/ruby
47
+ Meerkat runs the monitoring loop in the cloud and sends structured change
48
+ events back to your Rails application.
49
+
50
+ == How it works
51
+
52
+ * Create a monitoring task from Ruby.
53
+ * Describe what to monitor in plain English.
54
+ * Provide the relevant URLs, data, or connected system inputs.
55
+ * Define how often the task should run.
56
+ * Meerkat checks the source repeatedly, compares the latest result with
57
+ previous state, and identifies meaningful changes using your own LLM key.
58
+ * When something changes, Meerkat POSTs a signed JSON event to your
59
+ webhook, with automatic delivery retries.
60
+
61
+ == How it differs from Sidekiq and job queues
62
+
63
+ Sidekiq, Active Job, Good Job, Solid Queue, Delayed Job, and Resque are
64
+ excellent for running your Ruby jobs on your workers.
65
+
66
+ Meerkat is not a background-job queue. It is managed infrastructure for
67
+ continuously monitoring connected systems and reporting meaningful changes.
68
+
69
+ Instead of building polling jobs, comparison logic, schedulers, scraping
70
+ code, LLM workflows, and webhook delivery pipelines, you describe what
71
+ should be monitored and let Meerkat operate the watch loop.
72
+
73
+ == Common use cases
74
+
75
+ * Website and page-change monitoring
76
+ * API response monitoring
77
+ * Database and application-data monitoring
78
+ * SaaS and third-party system monitoring
79
+ * Competitor pricing and plan tracking
80
+ * Package and shipment tracking
81
+ * Stock and inventory availability alerts
82
+ * Recurring data checks with structured findings
83
+ * Change-detection webhooks for Rails and API backends
84
+
85
+ Documentation: https://cloud.meerkatagents.com/docs/introduction
46
86
  email:
47
87
  - hello@meerkatagents.com
48
88
  executables: []
@@ -94,5 +134,5 @@ requirements: []
94
134
  rubygems_version: 3.4.1
95
135
  signing_key:
96
136
  specification_version: 4
97
- summary: Ruby SDK for Meerkat Cloud change monitoring
137
+ summary: Ruby SDK for Meerkat Cloud Change Intelligence
98
138
  test_files: []