chain-insights 0.3.5 → 0.3.6

package/README.md

@@ -120,8 +120,11 @@ GraphRAG MCP endpoint.
 Hosted GraphRAG MCP lets new users try `graph_query` with a small public free
 quota before setting up paid access. The default public free graph_query quota
 is 10 execution seconds per IP per UTC day. Use `usage_status` to see the
-current caller quota. When the free quota is exhausted, prepare a wallet or use
-an invited tester access key and retry.
+current caller quota. Prepared wallet users receive the daily public grant
+first, then paid access continues automatically after the grant is exhausted.
+If you do not have a prepared wallet yet, use bounded single `graph_query`
+calls for the demo, then prepare a wallet or use an invited tester access key
+when the quota is exhausted.
 
 Open a case and run a small investigation:
 
@@ -182,6 +185,10 @@ cia mcp call graph_query_batch \
   'queries=[{"id":"count","query":"USE live_topology MATCH (n) RETURN count(n) AS count LIMIT 1"},{"id":"archive_flows","query":"USE archive_topology MATCH (src:Address)-[f:FLOWS_TO]->(dst:Address) RETURN f.period_granularity AS granularity, src.address AS source, dst.address AS target LIMIT 3"},{"id":"facts_sample","query":"USE facts MATCH (a:Address)-[:HAS_FEATURE]->(f:AddressFeature) RETURN a.address AS address, f.sent_count AS sent_count LIMIT 3"}]'
 ```
 
+For no-wallet public demos, prefer the single-query example first. Batch calls
+reserve worst-case execution time and can ask for paid access even when a small
+free balance remains.
+
 Run suspect topology without requiring an incident timestamp:
 
 ```bash

package/docs/graph-tools.md

@@ -34,11 +34,15 @@ GraphRAG MCP endpoint.
   remaining free quota.
 - Hosted endpoints can expose a public free graph_query quota. The default is
   10 execution seconds per IP per UTC day.
+- Prepared wallet users receive the daily public grant first; after it is used,
+  x402 payment continues automatically from the configured wallet.
 - Use explicit LIMIT and pagination in your query when you want bounded result
   sets.
 - The GraphRAG MCP server does not append `LIMIT`; Chain Insights recipes own
   their own limits and pagination.
-- Use `graph_query_batch` for related reads that should share one paid call.
+- Use single bounded `graph_query` calls for public no-wallet demos. Use
+  `graph_query_batch` for related reads that should share one paid call; public
+  free access does not include batches.
 - `per_query_timeout_seconds` is optional and capped at `10` by default.
 - Returned rows live in `structuredContent.facts`.
 
@@ -74,6 +78,10 @@ chain-insights mcp call graph_query_batch \
   'queries=[{"id":"count","query":"USE live_topology MATCH (n) RETURN count(n) AS count LIMIT 1"},{"id":"archive_flows","query":"USE archive_topology MATCH (src:Address)-[f:FLOWS_TO]->(dst:Address) RETURN f.period_granularity AS granularity, src.address AS source, dst.address AS target LIMIT 3"}]'
 ```
 
+Batch calls reserve worst-case execution time from their timeout settings. On
+public hosted endpoints, they can ask for paid x402 access even when a small
+free balance remains.
+
 Batch result facts include:
 
 ```json

package/docs/mcp-proxy.md

@@ -152,10 +152,21 @@ chain-insights mcp call graph_query \
 Hosted GraphRAG MCP can allow anonymous `graph_query` calls before wallet
 setup. The default public free graph_query quota is 10 execution seconds per IP
 per UTC day, reset on the UTC calendar day. `usage_status` returns only the
-current caller's quota status. Public free access does not include
-`graph_query_batch`; use a tester access key or paid x402 mode for regular
-usage and batches. Use explicit LIMIT and pagination in your query when you
-want bounded result sets.
+current caller's quota status. Wallet users receive the same daily public grant
+first; after it is exhausted, x402 payment continues automatically when
+`wallet ready` reports ready.
+
+Public free access is intended for look-and-feel demos with bounded single
+`graph_query` calls. Public free access does not include `graph_query_batch`;
+use a tester access key or paid x402 mode for regular usage and batches. Use
+explicit LIMIT and pagination in your query when you want bounded result sets.
+
+Staging UAT on 2026-05-31 showed the 10-second grant was enough for exact
+Bittensor address checks, sample address reads, sample flow reads, and the
+free-to-paid handoff. The tested address
+`5EkTMF1noWnWupGxQqtPczW2FFB7ktdVwjaZ22Cam54U93Xx` returned no indexed live or
+archive rows on staging, but bounded sample reads still returned Bittensor
+topology data inside the same daily grant.
 
 For custom graph reads, install the shipped `chain-insights-cypher` skill. Its
 Memgraph examples reference distinguishes staging-tested GraphRAG MCP query

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chain-insights",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "description": "AML investigation CLI and MCP proxy for blockchain risk, fund-flow tracing, case reports, and GraphRAG MCP access",
   "homepage": "https://chain-insights.ai",
   "repository": {