meerkat-agents 0.3.5 → 0.3.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 51c1742a69bf1d250bf974f258828a7c578530a29b2dc85a481201b7933ad27c
-  data.tar.gz: eb5f00f6185d64ce228031f4749dacd76aa8554913ed8e643a706724778a539a
+  metadata.gz: 8931270a622f63c7e979beeca840cc4ace19f06cbb4c869f1ef573675e7e2d65
+  data.tar.gz: 884b364930c7a2991cf787d5a07e1e234cb12fea51e385f12acf5d80abbf3d05
 SHA512:
-  metadata.gz: 956d4a8d7c51481b5acf4ae7410f32f403911f765e22465eff010d16b234a14cff8b1655b396ad1c5d3ada45bff6a748c346e197cf8d1397d25c0616d041644b
-  data.tar.gz: 02041b1e93bf95a5c5d5c9c6235184b8d2efcc6992e96c689337185494b8a5b10f3a6463d6e54b47ee16d7069375ddb64e11114d9db44390c2147792d92c8c8e
+  metadata.gz: 7556beab603f0d810015ad5df9703136a9354163dbe6599a2152fdb310f5153f1f10f48890478d7c011c661443f7dedfe681798fa9ed29cfeae65779057c8f1e
+  data.tar.gz: f070fe107fc0f24a2146f2d08ee940167bd915be6658acb063029169485f490247abc6fde655344b24015821d9a4cce8649fe4986778057db989225e12f8bb1c

data/CHANGELOG.md

@@ -5,6 +5,22 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.3.7] - 2026-07-17
+
+### Changed
+
+- Expanded RubyGems description: Change Intelligence positioning, how it works,
+  difference from job queues, and common use cases (RDoc headings + lists)
+
+## [0.3.6] - 2026-07-17
+
+### Changed
+
+- RubyGems listing: official Meerkat Cloud SDK positioning; no private GitHub links
+- Homepage → https://meerkatagents.com; docs → /docs/ruby; changelog → /changelog; bugs → /support
+- README quick start creates monitors without a webhook first
+- Signup resource accepts optional company/website
+
 ## [0.3.5] - 2026-07-17
 
 ### Changed
@@ -75,8 +91,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Webhook HMAC-SHA256 verification helpers
 - Optional Rails railtie and webhook verification concern
 
-[0.3.5]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.5
-[0.3.4]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.4
+[0.3.7]: https://meerkatagents.com/changelog
+[0.3.6]: https://meerkatagents.com/changelog
+[0.3.5]: https://meerkatagents.com/changelog
+[0.3.4]: https://meerkatagents.com/changelog
 [0.3.3]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.3
 [0.3.2]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.2
 [0.3.1]: https://github.com/Tiny-Bubble-Company/meerkat-ruby/releases/tag/v0.3.1

data/README.md

@@ -1,61 +1,69 @@
-# meerkat-agents
+# Meerkat Agents
 
-Change Intelligence for Ruby. Create monitors, inspect runs and artifacts, receive signed webhooks.
+The official Ruby SDK for Meerkat Cloud.
 
-```bash
-gem install meerkat-agents
-```
+Describe what you want to monitor, run it on demand or on a schedule, and
+receive structured change events in your dashboard or through a webhook.
+
+## Install
 
 ```ruby
-require "meerkat"
+gem "meerkat-agents"
 ```
 
-Default API base: `https://cloud.meerkatagents.com/api/v1`
+```bash
+bundle install
+```
 
----
+## Get an API key
 
-## Quick start
+1. Sign up at [cloud.meerkatagents.com/signup](https://cloud.meerkatagents.com/signup) (email + password).
+2. Copy your API key (shown once).
 
-### 1. Sign up
+```bash
+export MEERKAT_API_KEY=mk_...
+```
 
-[cloud.meerkatagents.com/signup](https://cloud.meerkatagents.com/signup) — copy `MEERKAT_API_KEY`, add your LLM key under **LLM key**.
+## Create your first monitor
 
-### 2. Create a monitor
+Webhook is optional — results appear in the Cloud dashboard and API.
 
 ```ruby
-client = Meerkat::Client.new(api_key: ENV["MEERKAT_API_KEY"])
+require "meerkat"
 
-client.monitors.create(
-  description: "Notify me when pricing or plan limits change",
-  input_params: { url: "https://competitor.com/pricing" },
-  frequency: "every 6 hours",
-  output_webhook: "https://myapp.com/webhooks/meerkat"
+client = Meerkat::Client.new(api_key: ENV.fetch("MEERKAT_API_KEY"))
+
+monitor = client.monitors.create(
+  description: "Tell me when this pricing page changes",
+  input_params: { url: "https://example.com/pricing" },
+  frequency: "every 6 hours"
 )
 ```
 
-All monitors are recurring. There is no `task_type`.
-
-### 3. List / update / delete
+## Run it
 
 ```ruby
-client.monitors.list
-client.monitors.retrieve(id)
-client.monitors.update(id, frequency: "every 12 hours")
-client.monitors.pause(id)
-client.monitors.resume(id)
-client.monitors.delete(id)
+run = client.monitors.run(monitor["data"]["id"])
+puts run
 ```
 
-### 4. Runs & artifacts
+Inspect findings in the [Cloud dashboard](https://cloud.meerkatagents.com/dashboard) under **Runs**, or:
 
 ```ruby
-client.monitors.runs(id)
-client.monitors.retrieve_run(id, run_id)
-client.monitors.artifacts(id, run_id)  # structured findings from the run
-client.monitors.run(id)                # trigger an on-demand run
+client.monitors.artifacts(monitor_id, run_id)
+client.monitors.retrieve_run(monitor_id, run_id)
 ```
 
-### 5. Webhooks in Rails
+## Add a webhook (optional)
+
+For production delivery to your Rails app:
+
+```ruby
+client.monitors.update(
+  monitor_id,
+  output_webhook: "https://myapp.com/webhooks/meerkat"
+)
+```
 
 ```ruby
 class Webhooks::MeerkatController < ApplicationController
@@ -68,28 +76,19 @@ class Webhooks::MeerkatController < ApplicationController
 end
 ```
 
-Set `MEERKAT_WEBHOOK_SECRET`.
-
----
+Set `MEERKAT_WEBHOOK_SECRET` for signature verification.
 
 ## Configuration
 
 | Variable | Description |
 |----------|-------------|
 | `MEERKAT_API_KEY` | From Cloud signup |
-| `MEERKAT_WEBHOOK_SECRET` | HMAC verification |
+| `MEERKAT_WEBHOOK_SECRET` | HMAC verification (when using webhooks) |
 | `MEERKAT_BASE_URL` | Optional; defaults to Cloud |
 
----
-
-## Pricing
-
-Free: 1 monitor · 1 run. Then [$20 — 5 monitors, 50 runs](https://cloud.meerkatagents.com/subscribe).
-
-Limit hit → `Meerkat::SubscriptionRequiredError`.
-
----
-
 ## Docs
 
-https://cloud.meerkatagents.com/docs/introduction
+- Product: https://meerkatagents.com
+- Ruby docs: https://meerkatagents.com/docs/ruby
+- Changelog: https://meerkatagents.com/changelog
+- Support: https://meerkatagents.com/support

data/lib/meerkat/resources/signup.rb

@@ -3,13 +3,15 @@
 module Meerkat
   module Resources
     class Signup < Base
-      def create(email:, company:, website:, name: nil)
+      def create(email:, name: nil, company: nil, website: nil, password: nil, password_confirmation: nil)
         client.post("/signup", body: {
           customer: {
             email: email,
             name: name,
             company: company,
-            website: website
+            website: website,
+            password: password,
+            password_confirmation: password_confirmation
           }.compact
         })
       end

data/lib/meerkat/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Meerkat
-  VERSION = "0.3.5"
+  VERSION = "0.3.7"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: meerkat-agents
 version: !ruby/object:Gem::Version
-  version: 0.3.5
+  version: 0.3.7
 platform: ruby
 authors:
 - Tiny Bubble Company
@@ -35,28 +35,40 @@ description: |
 
   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.
+  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.
+  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.
+  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.
+  * Create a monitoring task from Ruby.
+  * Describe what to monitor in plain English.
+  * Provide the relevant URLs, data, or connected system inputs.
+  * Define how often the task should run.
+  * Meerkat checks the source repeatedly, compares the latest result with
+    previous state, and identifies meaningful changes using your own LLM key.
+  * When something changes, Meerkat POSTs a signed JSON event to your
+    webhook, with automatic delivery retries.
 
   == How it differs from Sidekiq and job queues
 
-  Sidekiq, Active Job, Good Job, Solid Queue, Delayed Job, and Resque are excellent for running your Ruby jobs on your workers.
+  Sidekiq, Active Job, Good Job, Solid Queue, Delayed Job, and Resque 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.
+  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.
+  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
 
@@ -95,15 +107,14 @@ files:
 - lib/meerkat/resources/tasks.rb
 - lib/meerkat/version.rb
 - lib/meerkat/webhooks.rb
-homepage: https://meerkatagents.com/
+homepage: https://meerkatagents.com
 licenses:
 - MIT
 metadata:
-  homepage_uri: https://meerkatagents.com/
-  documentation_uri: https://cloud.meerkatagents.com/docs/introduction
-  source_code_uri: https://github.com/Tiny-Bubble-Company/meerkat-ruby
-  changelog_uri: https://github.com/Tiny-Bubble-Company/meerkat-ruby/blob/main/CHANGELOG.md
-  bug_tracker_uri: https://github.com/Tiny-Bubble-Company/meerkat-ruby/issues
+  homepage_uri: https://meerkatagents.com
+  documentation_uri: https://meerkatagents.com/docs/ruby
+  changelog_uri: https://meerkatagents.com/changelog
+  bug_tracker_uri: https://meerkatagents.com/support
   rubygems_mfa_required: 'true'
 post_install_message:
 rdoc_options: []
@@ -123,6 +134,5 @@ requirements: []
 rubygems_version: 3.4.1
 signing_key:
 specification_version: 4
-summary: Meerkat Cloud Change Intelligence — monitor websites, APIs, and systems;
-  get webhooks (not Sidekiq).
+summary: Ruby SDK for Meerkat Cloud Change Intelligence
 test_files: []