agentadmit 1.1.0 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f9dee1c87344bc7be4a6ae662446c18c5ac25fe40dbe384091524026127c091a
-  data.tar.gz: 477af00d19a84da65d0405f804982272bceceec85661e7f9a4afba8332c408f3
+  metadata.gz: 8231757da1987653f73ed2c9b1cfa48c8745c2220856d99da8427fc017406616
+  data.tar.gz: a0128eb51759e86da018e9852db33cafaf853b86fb9f7cd3f15f6aabd06009e6
 SHA512:
-  metadata.gz: 97aef14949cfaea7090597db980330fc7cc7bfadf63909cdaced2d4e6c9889d0492f03108a0f6db4a31f42243e0dea8eb04c921a3058e6c4c37cab56ecade685
-  data.tar.gz: 30b10080024db2dc44b238bf2afa0941b15f697d465c58ed966208a1afbf9d9294fd212f5fe353c832f4ea0bc3491e16e0f63c37089fd3da961aa7d54cb5efaf
+  metadata.gz: 5eb0d7b249d27e9f5455eabc5b3214493dcd82b6be6563530ec05c66669aef52ae164aba352a21c744024be2b2b7a080fa5581bafff3ff9a1dc4aecab76f78a1
+  data.tar.gz: 8f955a6ac7d15948da7bf679e7fab80d5d0576110c672ba1e179f9e5458d6e1a6ef12dc60325d121dc41ccecdb69d0d709c3bbc8c125c3bff5bc6780c6601c84

data/README.md

@@ -122,15 +122,17 @@ Full integration guide: https://agentadmit.com/docs/app-owner-guide
 The AgentAdmit Ruby SDK runs server-side and does not interact with app stores or end-user devices directly.
 
 ### What the SDK does
-- Validates AgentAdmit tokens presented by AI agents
+- Validates AgentAdmit tokens by calling AgentAdmit's hosted introspection endpoint (`https://api.agentadmit.com/api/v1/verify`) on every agent request — this is mandatory introspection; there is no local or offline validation mode
 - Enforces scope-based access control on your API routes
-- Manages connection lifecycle (create, revoke, audit)
+- Manages connection lifecycle (create, revoke, audit) using your configured storage backend
 
 ### What the SDK does NOT do
-- Does not collect end-user data
-- Does not send telemetry or analytics
-- Does not phone home to AgentAdmit servers (all operations use your configured keys and storage)
-- Does not track users or devices
+- Does not transmit raw end-user PII (such as name, email, or device identifiers) — each introspection request sends the opaque access token and your API key
+- Does not perform passive background telemetry or analytics — network calls occur only during active token validation
+- Does not maintain its own persistent storage — local state (connections, audit log) lives in the storage backend you configure
+
+### What the AgentAdmit hosted service records
+On every token validation, AgentAdmit's `/api/v1/verify` endpoint receives the access token and API key, resolves the token to its `user_id`, `connection_id`, granted `scopes`, and `agent_label`, and records per-call metadata (including the endpoint and timestamp) for billing, audit logging, the security alerts engine, and usage metering. This is integral to how AgentAdmit works and applies to both test and live keys. See the "Mandatory introspection" notes above and the [compliance guide](https://agentadmit.com/docs/compliance) for the full data-handling description.
 
 ### Privacy impact
 Since this SDK runs on your server, it has no direct App Store or Play Store compliance surface. Your client-side integration (e.g., the AgentAdmit React SDK) handles privacy manifest and data safety requirements.

data/lib/agentadmit/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module AgentAdmit
-  VERSION = "1.1.0"
+  VERSION = "1.1.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: agentadmit
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.2
 platform: ruby
 authors:
 - Christopher Emerson
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-06-11 00:00:00.000000000 Z
+date: 2026-06-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json