Reader 1.7.6 — retain table references

Reader 1.7.6 retains safe reference destinations from HTML table cells and captions. Rectangular tables include clickable Markdown links even when structured metadata limits are reached. Table rows keep their plain-cell format. Irregular/spanning tables keep labelled TSV; their references are exposed separately through bounded link metadata. Links are never fetched automatically.

The owned technical-guide sample demonstrates a table reference. Prices and payment protections are unchanged. Significant inline-code whitespace remains preserved from 1.7.5. All six published 1.7.5 downloads stay immutable.

Download either reader-client.mjs plus reader-client.mjs.sha256, or reader-mcp.mjs plus reader-mcp.mjs.sha256. Keep filenames unchanged. Verify before running using the POSIX or PowerShell instructions in the reader guide. Requires Node 20.19+. No wallet or payment is needed to inspect downloads or request a quote. Buying requires an existing funded Base wallet and explicit spending authorization.

These files match the website's versioned downloads. SHA-256 checksums detect file mismatches; they are not independent security signatures. Cached demonstrations and readiness checks are not customer payments or proof of funded delivery.

Reader guide: https://agent-data-tools.revmesh2074.workers.dev/guides/web-reading
Source and setup: https://github.com/Nutshell2000/agent-data-tools/tree/main/clients

Reader 1.7.5 — literal code fidelity

Reader 1.7.5 corrects HTML inline-code whitespace: significant spaces and syntax-highlighting text survive extraction, and multiline literals use fenced Markdown. The owned technical-guide sample demonstrates the fix. All 32 tools and prices remain unchanged.

Download either reader-client.mjs plus reader-client.mjs.sha256, or reader-mcp.mjs plus reader-mcp.mjs.sha256. Keep filenames unchanged. Verify before running using the POSIX or PowerShell instructions in the reader guide. Requires Node 20.19+. No wallet or payment is needed to inspect downloads or request a quote. Buying requires an existing funded Base wallet and explicit spending authorization.

These files match the website's versioned downloads. SHA-256 checksums detect file mismatches; they are not independent security signatures. Earlier versioned downloads remain available unchanged. Readiness checks and cached examples are not customer payments or proof of funded delivery.

Reader guide: https://agent-data-tools.revmesh2074.workers.dev/guides/web-reading
Source and setup: https://github.com/Nutshell2000/agent-data-tools/tree/main/clients

Chain client 1.0.0 — capped Base checks

Chain client 1.0.0 buys structured results from four existing Base tools: transaction status ($0.003 maximum), wallet snapshot ($0.005), gas estimate ($0.002) and token allowance ($0.002). Quote commands never read keys or pay. Every buy requires an explicit per-invocation cap and an existing local X402_PRIVATE_KEY.

Download both chain-client.mjs and chain-client.mjs.sha256 into one folder, keeping filenames unchanged. Verify before running using the POSIX or PowerShell instructions in docs/chain-checks.md at this tag. Requires Node 20.19+; no npm installation or TypeScript is needed to use the executable. Source and reproducible build instructions are in clients/chain/README.md at this tag.

The client pins the HTTPS origin, full requested resource, fixed recipient, Base native USDC and exact scheme. It authorizes/submits at most once per invocation. Stop and reconcile after an uncertain signed outcome; there is no automatic retry or paid polling. It never sends the transaction being checked or changes a token approval. Caps are per invocation, not session/monthly allowances.

Transaction success is not proof of the intended token payment. Missing token rows are not proof of zero balance. Gas excludes Ethereum posting cost. Positive allowance need not cover the intended amount. Server receipts are not independent chain proof.

This separate client release does not change the Worker, API prices, handlers, existing reader downloads or Claude's checkout. Reader 1.7.6 remains the repository's latest release. Signing tests use offline fixtures; live quotes are unpaid operator checks. Funded delivery and customer demand remain unverified.

SHA-256 checksums detect mismatched files; they are not independent security signatures.

OFAC SDN list mirror

Unmodified copies of OFAC's SDN.CSV and ALT.CSV plus ofac-index.json (the same data pre-parsed), refreshed every 6 hours for /sanctions/check. Source: https://ofac.treasury.gov/

Reader clients 1.7.4

Download the CLI executable and its matching one-file checksum, or the local MCP adapter and its matching checksum. Requires Node 20.19+; no npm installation or new account.

• CLI: reader-client.mjs and reader-client.mjs.sha256
• Local MCP adapter: reader-mcp.mjs and reader-mcp.mjs.sha256
• SHA256SUMS covers both executables and command-builder.js. Checking the complete list requires all three files; verify only your chosen executable using its one-file checksum.

These six files match the website's published 1.7.4 bytes, checked against the tested release from source commit dbd3894. CLI setup and verification · Local MCP setup

Inspect an unpaid quote without a wallet or key:

node reader-client.mjs quote 'https://example.com' --format markdown

For an intended, authorized purchase with an existing funded Base wallet:

node reader-client.mjs buy 'https://example.com' --max-usdc 0.002 --format markdown

Supply X402_PRIVATE_KEY privately through the local process environment. Never put keys in command arguments, URLs or public reports. Each explicit buy can authorize once. The client pins this service, recipient, Base, native USDC and exact scheme. It refuses redirects and excessive prices. After an uncertain signed outcome, stop and reconcile the request ID and available receipt; there is no automatic fresh-payment retry.

The local MCP adapter starts with quotes only. Buying needs deliberate opt-in, a process budget and a per-call cap. Its uncertainty lock prevents further buys after an unknown signed outcome. This release does not install or enable the adapter in a host.

Compared with repository download 1.7.0, the current clients include recognized error codes with static guidance, bounded error-body reads and local URL-error guidance. The live reader also preserves superscript/subscript distinctions and omits clearly identified same-document permalink controls. Service 1.7.4 isolates cold payment-gateway initialization; that server repair is already deployed separately from these client files.

The clients support reader, bounded sitemap and Bitcoin-fee data purchases at $0.002 each. Static HTML, Markdown and plain text only; no JavaScript rendering, authenticated pages or paywall access. Section selection requires an exact visible HTML source ID. Inspect output scope, truncation and warnings. Source metadata is unverified; image pixels are not interpreted.

All earlier published downloads remain unchanged. Checksums are served by the same operator and are not independent signatures. Unsigned quotes, downloaded-client tests and local payment fixtures do not establish funded production delivery or customer demand. No self-purchases were made for this release.

Reader clients 1.7.0

Download one executable and its matching checksum into the same folder. These are the exact 1.7.0 files served by our website, checked against the build from source commit c203ff8 and the published SHA-256 checksums. Requires Node 20.19+; no npm installation or new account.

• CLI: reader-client.mjs and reader-client.mjs.sha256
• Local MCP adapter: reader-mcp.mjs and reader-mcp.mjs.sha256
• SHA256SUMS covers both executables and command-builder.js. Verify only your downloaded executable using its matching one-file checksum; checking the complete list requires all listed files.

Setup and shell-specific verification · Local MCP setup

An unpaid quote needs no key and never signs:

node reader-client.mjs quote 'https://example.com' --format markdown

An intended purchase requires an existing funded Base wallet, explicit authorization and a cap:

node reader-client.mjs buy 'https://example.com' --max-usdc 0.002 --format markdown

Supply X402_PRIVATE_KEY privately through the local process environment. Never put it in command arguments, URLs or public reports. Each buy can authorize one payment. After an uncertain signed outcome, stop and reconcile the request ID and available receipt; do not automatically retry. The local MCP adapter starts in quotes-only mode; buying requires deliberate opt-in and a process budget. This release does not install or enable it in a host.

The clients also support capped sitemap and Bitcoin fee-data calls. Static HTML, Markdown and plain text only; no JavaScript rendering, login or paywall access. HTML sections use exact source IDs. The reader preserves code, tables and labelled image alt text; image pixels are not interpreted. Markdown source keeps its syntax with empty structured metadata.

The current service adds bounded, unverified author/date declarations with provenance and publishes exact successful-result schemas for its remote MCP reader, sitemap and Bitcoin-fee tools. Both transports validate those results before settlement. Remote quotes/failures use isError=true and JSON in content[0].text, without structuredContent. These are server capabilities; this download does not independently verify source claims, on-chain receipts or customer demand. The CLI and adapter retain their existing payment controls.

Version 1.5.1 downloads remain unchanged. These operator download/quote checks are unpaid verification, not purchases or proof of funded delivery. Checksums come from the same operator and are not independent signatures. Prices remain unchanged.

Reader clients 1.5.1

Download one executable and its matching checksum into the same folder. These are the exact 1.5.1 files served by our website, verified against source commit 651be3d and the published checksums. Requires Node 20.19+; no npm install or new account.

• CLI: reader-client.mjs and reader-client.mjs.sha256
• Local MCP adapter: reader-mcp.mjs and reader-mcp.mjs.sha256
• SHA256SUMS covers both executables and command-builder.js. Verify only your downloaded executable using its matching one-file checksum; checking the complete list requires all listed files.

Setup and shell-specific checksum commands: https://agent-data-tools.revmesh2074.workers.dev/guides/web-reading.md
Local MCP setup: https://agent-data-tools.revmesh2074.workers.dev/guides/local-mcp

An unpaid quote needs no key and never signs:

node reader-client.mjs quote https://example.com --format markdown

A purchase requires an existing funded Base wallet, explicit authorization and a cap:

node reader-client.mjs buy https://example.com --max-usdc 0.002 --format markdown

Supply X402_PRIVATE_KEY privately through the local process environment. Never put it in command arguments, URLs or public reports. Each buy can authorize one payment; stop and reconcile the request ID and receipt after an uncertain signed outcome. Do not automatically retry. The MCP adapter starts in quotes-only mode; buying requires explicit opt-in and a process budget.

The same clients support capped sitemap and Bitcoin fee-data calls. Static HTML, Markdown or plain-text reader input only; no JavaScript rendering, login or paywall access. Markdown source retains syntax with empty structured metadata. Version 1.5.1 corrects source-relative HTML links using linkBaseUrl. No source code or linked page is executed or fetched automatically.

These download checks are unpaid operator verification, not customer purchases or evidence of funded delivery. Checksums are published by the same operator and are not independent security signatures. API prices remain unchanged.