meerkat-agents 0.3.1 → 0.3.4
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.
- checksums.yaml +4 -4
- data/CHANGELOG.md +21 -0
- data/lib/meerkat/version.rb +1 -1
- metadata +38 -28
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 7f9cd7b7a43521def709a4b933cb35624880094c4bdeb2286da218d1e85ff7fc
|
|
4
|
+
data.tar.gz: 85046b0df47ccb0722ab4c2c349ecc9703d9795d06b05bf80b908f2392d0cb15
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cfaa1976b61ff53f87f5c5d0a5eb8c3294db21aa4cfecc7d3b7b91260db05c125189ffac2458eae9b3debb679cf76f903f26138201ac45e1eea0239b960b35e6
|
|
7
|
+
data.tar.gz: 81bfa814d2d295cba877cf2420f8c9e78d23807c3238f26c5a2f3d819eeb4010a80d4e141084b0363925b1597c38a96f66f1931337ce61a135df6eecafffd547
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,24 @@ 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.4] - 2026-07-17
|
|
9
|
+
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- RubyGems description uses RDoc section headings (`==`) so rubygems.org renders paragraphs, headings, and lists instead of one collapsed block
|
|
13
|
+
|
|
14
|
+
## [0.3.3] - 2026-07-17
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
|
|
18
|
+
- RubyGems description expanded for Change Intelligence across websites, APIs, databases, SaaS, and other connected systems
|
|
19
|
+
|
|
20
|
+
## [0.3.2] - 2026-07-17
|
|
21
|
+
|
|
22
|
+
### Changed
|
|
23
|
+
|
|
24
|
+
- RubyGems description copy refined for clarity (problem, cloud monitoring loop, Sidekiq/queue contrast, use cases)
|
|
25
|
+
|
|
8
26
|
## [0.3.1] - 2026-07-17
|
|
9
27
|
|
|
10
28
|
### Changed
|
|
@@ -51,6 +69,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
51
69
|
- Webhook HMAC-SHA256 verification helpers
|
|
52
70
|
- Optional Rails railtie and webhook verification concern
|
|
53
71
|
|
|
72
|
+
[0.3.4]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.4
|
|
73
|
+
[0.3.3]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.3
|
|
74
|
+
[0.3.2]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.2
|
|
54
75
|
[0.3.1]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.1
|
|
55
76
|
[0.3.0]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.0
|
|
56
77
|
[0.2.0]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.2.0
|
data/lib/meerkat/version.rb
CHANGED
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.
|
|
4
|
+
version: 0.3.4
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Tiny Bubble Company
|
|
@@ -31,36 +31,46 @@ dependencies:
|
|
|
31
31
|
- !ruby/object:Gem::Version
|
|
32
32
|
version: '3'
|
|
33
33
|
description: |
|
|
34
|
-
Meerkat Agents
|
|
34
|
+
== Meerkat Agents
|
|
35
35
|
|
|
36
|
-
|
|
37
|
-
-----------------
|
|
38
|
-
Rails apps often need to know when something on the web changes — competitor pricing,
|
|
39
|
-
plan pages, package tracking, stock, or content — without building scrapers, cron jobs,
|
|
40
|
-
HTML diffs, retries, and webhook plumbing. Meerkat runs that watch loop in the cloud and
|
|
41
|
-
POSTs structured change events to your Rails app.
|
|
36
|
+
The official Ruby client for Meerkat Cloud Change Intelligence.
|
|
42
37
|
|
|
43
|
-
|
|
44
|
-
----------------------------------------------------------------------------------------
|
|
45
|
-
Those gems are excellent for running YOUR Ruby jobs on YOUR workers (background jobs,
|
|
46
|
-
queues, cron). Meerkat is not a job queue. You describe what to watch in plain English;
|
|
47
|
-
Meerkat fetches sources, uses your LLM key (BYOK) to judge meaningful change, and delivers
|
|
48
|
-
signed JSON webhooks. No Sidekiq workers or scraping code required for the monitoring path.
|
|
38
|
+
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.
|
|
49
39
|
|
|
50
|
-
|
|
51
|
-
----------------
|
|
52
|
-
- Website / page change monitoring
|
|
53
|
-
- Competitor price and plan monitoring
|
|
54
|
-
- Package / shipment tracking alerts
|
|
55
|
-
- Stock and availability watches
|
|
56
|
-
- Recurring web scraping with structured findings
|
|
57
|
-
- Change detection webhooks for Rails and API backends
|
|
40
|
+
Building these monitoring loops yourself usually means maintaining polling jobs, cron schedules, background workers, state comparisons, retries, LLM orchestration, and webhook infrastructure.
|
|
58
41
|
|
|
59
|
-
|
|
60
|
-
website monitoring, price monitoring, package tracking, cron, scheduler, llm, agents,
|
|
61
|
-
change detection, faraday.
|
|
42
|
+
Meerkat runs the monitoring loop in the cloud and sends structured change events back to your Rails application.
|
|
62
43
|
|
|
63
|
-
|
|
44
|
+
== How it works
|
|
45
|
+
|
|
46
|
+
1. Create a monitoring task from Ruby.
|
|
47
|
+
2. Describe what to monitor in plain English.
|
|
48
|
+
3. Provide the relevant URLs, data, or connected system inputs.
|
|
49
|
+
4. Define how often the task should run.
|
|
50
|
+
5. Meerkat checks the source repeatedly, compares the latest result with previous state, and identifies meaningful changes using your own LLM key.
|
|
51
|
+
6. When something changes, Meerkat POSTs a signed JSON event to your webhook, with automatic delivery retries.
|
|
52
|
+
|
|
53
|
+
== How it differs from Sidekiq and job queues
|
|
54
|
+
|
|
55
|
+
Sidekiq, Active Job, Good Job, Solid Queue, Delayed Job, and Resque are excellent for running your Ruby jobs on your workers.
|
|
56
|
+
|
|
57
|
+
Meerkat is not a background-job queue. It is managed infrastructure for continuously monitoring connected systems and reporting meaningful changes.
|
|
58
|
+
|
|
59
|
+
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.
|
|
60
|
+
|
|
61
|
+
== Common use cases
|
|
62
|
+
|
|
63
|
+
* Website and page-change monitoring
|
|
64
|
+
* API response monitoring
|
|
65
|
+
* Database and application-data monitoring
|
|
66
|
+
* SaaS and third-party system monitoring
|
|
67
|
+
* Competitor pricing and plan tracking
|
|
68
|
+
* Package and shipment tracking
|
|
69
|
+
* Stock and inventory availability alerts
|
|
70
|
+
* Recurring data checks with structured findings
|
|
71
|
+
* Change-detection webhooks for Rails and API backends
|
|
72
|
+
|
|
73
|
+
Documentation: https://cloud.meerkatagents.com/docs/introduction
|
|
64
74
|
email:
|
|
65
75
|
- hello@meerkatagents.com
|
|
66
76
|
executables: []
|
|
@@ -113,6 +123,6 @@ requirements: []
|
|
|
113
123
|
rubygems_version: 3.4.1
|
|
114
124
|
signing_key:
|
|
115
125
|
specification_version: 4
|
|
116
|
-
summary: Change Intelligence
|
|
117
|
-
(not Sidekiq).
|
|
126
|
+
summary: Meerkat Cloud Change Intelligence — monitor websites, APIs, and systems;
|
|
127
|
+
get webhooks (not Sidekiq).
|
|
118
128
|
test_files: []
|