chain-insights 0.57.3 → 0.57.5

package/README.md

@@ -17,8 +17,8 @@ Chain Insights is open-source AML and forensics infrastructure for AI agents
 and analysts: a hosted Chain Insights Graph you reach over MCP, screened
 through one CLI. It screens blockchain addresses for risk, explores fund flows
 through read-only graph queries, and returns structured investigation facts.
-Every new account gets a free tier — a daily allowance
-of graph queries, no payment setup — so you can run a first screen in minutes.
+The hosted graph has a free tier — 5,000 units a day per address,
+no key and no payment setup — so you can run a first screen in minutes.
 
 ## Quickstart
 
@@ -119,7 +119,7 @@ Never touches:
 | `graph_query_batch`         | Run related read-only graph queries as one MCP call                                |
 | `meta_network_capabilities` | Check supported Chain Insights networks and graph tools                            |
 | `meta_schema`               | Read the live graph schema of a network: labels, link types, fields, indexes       |
-| `meta_usage_status`         | Check the caller's daily free-tier graph query allowance                           |
+| `meta_usage_status`         | Check the caller's daily free-demo graph query allowance                           |
 | `meta_help`                 | Show Chain Insights tool and workflow guidance                                     |
 | `wallet_balance`            | Show the local payment wallet amount                                               |
 | `wallet_topup`              | Show the local payment wallet address and its QR code for a USDC top-up on Base    |
@@ -203,6 +203,12 @@ Chain Insights Graph bills by **billable units**.
 - Bigger responses cost more. Narrow queries cost less.
 - The server reports `billable_units` on every graph response.
 
+| Door | Price | Limits |
+| --- | --- | --- |
+| Free tier | Free | 5,000 units a day per address, 30 requests a minute, resets at midnight UTC |
+| Pay as you go (USDC per call, and the ACP offering) | One cent per 100 units, rounded up to the next cent, one cent minimum per call. A batch is one call. | No daily limit, no rate limit for paying agents |
+| Subscription in $CIA (not yet live) | Paid in $CIA | 100,000 units a day, 60 requests a minute |
+
 **Check your own count.** `src/lib/recount-units.ts` mirrors the server's
 counting logic. Use it client-side to recount units in a response and
 confirm the billed amount matches what you received.
@@ -334,11 +340,12 @@ a prepared wallet. For paid access, run `cia wallet ready` — it checks
 funding and finishes one-time payment setup. Setup commands live in
 [MCP proxy](docs/mcp-proxy.md).
 
-The hosted graph includes a small public free tier for `graph_query`
-(default: 10 execution seconds per IP per UTC day). Use
-`meta_usage_status` to see the current caller allowance. Prepared wallet
-users receive the free tier first, then paid access continues
-automatically.
+The hosted graph includes a free tier for `graph_query` and
+`graph_query_batch`: 5,000 units a day per address (an IP address block),
+no key, 30 requests a minute, reset at midnight UTC. Schema reads
+(`meta_schema`) cost nothing on every door. Use `meta_usage_status` to see
+the current caller allowance. Prepared wallet users receive the free tier
+first, then paid access continues automatically.
 
 ## Test
 

package/docs/graph-query-compatibility.md

@@ -174,7 +174,7 @@ acting.
 The whole-graph high-fan-in sweep — every operator grouped by distinct owner
 count — is a valid shape but a heavy one: at millions of edges it can exceed
 the per-query limit (60 seconds by default), and a sweep that times out can
-still consume the metered seconds. A `network` filter does not narrow it. Bound
+still return a large metered result. A `network` filter does not narrow it. Bound
 it by a recent `last_seen_timestamp` window — recompute the cutoff rather than
 copying a literal, for example now minus 7 days in Unix milliseconds — and
 prefer the point-anchored probe on metered endpoints:

package/docs/graph-tools.md

@@ -340,18 +340,25 @@ and `:Sanctioned`. Each role also has a flag on the node.
   `kind` is a column and a filter. Add `t.kind = "internal"` to the pair and the
   day to read only the internal rows.
 - Use `meta_usage_status` through Chain Insights before public hosted reads
-  when you need the caller's remaining free-tier allowance.
-- Hosted endpoints can expose a public free tier for graph_query. The default
-  is 10 execution seconds per IP per UTC day.
+  when you need the caller's remaining free-demo allowance.
+- Hosted endpoints expose a free tier for graph_query and graph_query_batch:
+  5,000 units a day per address (an IP address block), 30 requests a minute,
+  reset at midnight UTC. A unit is one returned row, node, edge or list
+  element. Schema reads (`meta_schema`) cost nothing on every door.
+- Pay as you go on x402 (and the ACP offering) costs one cent per 100 units,
+  rounded up to the next cent, one cent minimum per call. A batch is one call.
+  There is no daily limit and no rate limit for paying agents.
+- A subscription in $CIA (not yet live) gives 100,000 units a day at 60
+  requests a minute.
 - Prepared wallet users receive the daily free tier 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.
 - Chain Insights Graph does not append `LIMIT`; Chain Insights recipes own their
   own limits and pagination.
-- Use single bounded `graph_query` calls for public no-wallet free-tier usage. Use
-  `graph_query_batch` for related reads that should share one paid call; public
-  free-tier access does not include batches.
+- Use bounded `graph_query` calls for public no-wallet free-demo usage.
+  `graph_query_batch` is also included in the free tier; use it for related
+  reads that should share one call.
 - `per_query_timeout_seconds` is optional and capped at `60` by default (`30` for
   `USE facts`). It can lower a limit. It cannot raise one.
 - Returned rows live in `structuredContent.facts`.
@@ -398,9 +405,9 @@ cia mcp call graph_query_batch \
   'queries=[{"id":"count","query":"USE topology MATCH (a:Address) RETURN count(a) AS count LIMIT 1"},{"id":"flows","query":"USE topology MATCH (src:Address)-[f:FLOWS_TO]->(dst:Address) RETURN src.address AS source, dst.address AS target, f.amount_usd_sum AS amount_usd_sum, f.tx_count AS tx_count LIMIT 3"},{"id":"linked","query":"USE topology MATCH (a:Address)-[l:LINKED]-(b:Address) RETURN a.address AS address, b.address AS linked_address, l.basis AS basis, l.confidence AS confidence 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-tier allowance remains.
+A batch is one call and counts the units of all its returned rows. The free
+demo includes batches. On public hosted endpoints, a batch that would pass
+the remaining free-demo allowance can ask for paid x402 access.
 
 Batch result facts include:
 
@@ -413,8 +420,7 @@ Batch result facts include:
     "live_tier_timeout_seconds": 60,
     "starrocks_tier_timeout_seconds": 30,
     "total_query_elapsed_ms": 1345,
-    "billable_seconds": 2,
-    "estimated_usdc": "0.02"
+    "billable_units": 12
   }
 }
 ```

package/docs/mcp-proxy.md

@@ -81,7 +81,7 @@ The proxy:
 | --------------------------- | ------------------------------------------------------------------------------------ |
 | `meta_network_capabilities` | Show the current Chain Insights network/tool support matrix                          |
 | `meta_schema`               | Show the live graph schema of a network: labels, link types, fields, indexes         |
-| `meta_usage_status`         | Check the caller's daily free-tier graph query allowance                             |
+| `meta_usage_status`         | Check the caller's daily free-demo graph query allowance                             |
 | `meta_help`                 | Show Chain Insights tool and workflow guidance                                       |
 | `wallet_balance`            | Show the local payment wallet address, payment network, token, and amount            |
 | `wallet_topup`              | Show the local payment wallet address and its QR code, with a Claude view            |
@@ -198,7 +198,7 @@ cia access-key set ci_test_REDACTED --endpoint https://mcp.chain-insights.ai/
 cia access-key status
 ```
 
-Daily free-tier graph usage:
+Daily free-demo graph usage:
 
 ```bash
 cia mcp call meta_usage_status
@@ -207,17 +207,21 @@ cia mcp call graph_query \
   "query=USE topology MATCH (n) RETURN count(n) AS count LIMIT 1"
 ```
 
-Hosted Chain Insights Graph can allow anonymous `graph_query` calls before wallet
-setup. The default public free tier is 10 execution seconds per IP per UTC day,
-reset on the UTC calendar day. `meta_usage_status` returns only the current caller's
-allowance status. Wallet users receive the same daily free tier first; after it
-is exhausted, x402 payment continues automatically when `wallet ready` reports
-ready.
-
-The daily free tier is intended for bounded single `graph_query` calls. It 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.
+Hosted Chain Insights Graph can allow anonymous `graph_query` and
+`graph_query_batch` calls before wallet setup. The free tier is 5,000 units a
+day per address (an IP address block), at 30 requests a minute, reset at
+midnight UTC. A unit is one returned row, node, edge or list element.
+Schema reads (`meta_schema`) cost nothing on every door.
+`meta_usage_status` returns only the current caller's allowance status.
+Wallet users receive the same free tier first; after it is exhausted, x402
+payment continues automatically when `wallet ready` reports ready.
+
+The free tier includes `graph_query_batch`. Pay as you go on x402 (and the ACP
+offering) costs one cent per 100 units, rounded up to the next cent, with one
+cent minimum per call; a batch is one call. It has no daily limit and no rate
+limit for paying agents. A subscription in $CIA (not yet live) gives 100,000
+units a day at 60 requests a minute. Use explicit LIMIT and pagination in your
+query when you want bounded result sets.
 
 ### CLI Output And Tool Versions
 
@@ -234,7 +238,7 @@ cia mcp call --json graph_query \
   "query=USE topology MATCH (a:Address) RETURN a.address AS address LIMIT 10"
 ```
 
-UAT on 2026-05-31 showed the 10-second free tier was enough for exact
+UAT on 2026-05-31 showed the earlier free tier was enough for exact
 address checks, sample address reads, sample flow reads, and the
 free-to-paid handoff, but bounded sample reads still returned topology data
 inside the same daily allowance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chain-insights",
-  "version": "0.57.3",
+  "version": "0.57.5",
   "description": "AML investigation CLI and MCP proxy for blockchain risk screening and Chain Insights Graph access",
   "homepage": "https://chain-insights.ai",
   "repository": {