Read BlockVectra docs from Python — no API key

Read BlockVectra documentation from a Python agent with the official MCP Python SDK. No BlockVectra API key, wallet or model API is needed.

git clone https://github.com/blockvectra/agent-quickstart.git
cd agent-quickstart
uv run examples/mcp_docs.py

Requires Python 3.11+ and uv. The script pins mcp==2.3.0, connects to the documentation-only Streamable HTTP endpoint, lists search_docs and read_doc, and reads the English quickstart page. Its JSON output includes the complete Markdown text for an agent to use. Tool errors and empty text fail visibly; it does not run chain RPC or provision an account.

Read the example · MCP setup guide

Validated against the deployed docs endpoint with Python 3.14.8 and SDK 2.3.0. This is one compatibility check, not a performance benchmark or evidence of customer adoption. The script uses a 40-second cooperative Python timeout; package installation is outside it. The separate standard-library RPC example remains available without third-party packages.

Python first read for Robinhood Chain

Read Robinhood Chain’s public chain identity with Python 3.10 or newer:

git clone --branch python-keyless-chain-id-2026.11.06 --depth 1 https://github.com/blockvectra/agent-quickstart.git
cd agent-quickstart
python3 examples/public_chain.py

The example uses Python’s standard library and needs no wallet, account or API key. It reads the public chain catalog, checks the selected endpoint and confirms chain ID 4663 before printing:

{"chain": "robinhood_mainnet", "chainId": 4663}

To select another cataloged public chain, pass its decimal chain ID, for example python3 examples/public_chain.py 56 for BNB Smart Chain. The catalog must advertise a usable public endpoint for that chain.

The reader makes at most two serial HTTP attempts, including one JSON-RPC call, with no automatic retries. It checks chain identity; the existing Node.js example also reads block height. Indexed Data API and account operations use the separate authenticated flow.

Python source at this version · English quickstart · 中文快速开始

Source: b8744ea938c6b496390acf8934ba73844b995cc0, from PR #35. Validation includes nine Python offline tests and saved transport checks. A single live check at 09:56 UTC on November 6 returned chain ID 4663 on Python 3.14; that dated result is not an availability or performance guarantee. This release reuses those results and makes no new RPC request.

Keyless Robinhood read — native Node.js 22 support

Run the keyless Robinhood mainnet reader with Git and Node.js 22 (>=22.18) or Node.js >=24.12, without installing npm dependencies:

git clone --branch keyless-read-node22-2026.11.02 --depth 1 https://github.com/blockvectra/agent-quickstart.git
cd agent-quickstart
node src/public-read-cli.ts

The reader checks the public chain directory, confirms chain ID 4663 and reads the latest block number. It uses at most three HTTP requests, including two JSON-RPC calls, with no automatic retries. The directory must advertise the expected public endpoint and methods before RPC starts. No wallet, account or API key is needed for this reader.

For the npm route and full account onboarding, see the pinned README. npm start runs the separate SIWE/wallet/key flow; Data API and account operations require a key.

Source: a8f0d98119c5875aa953060c7901ed8e2070447c.

Existing CI passed on the same Git tree: three native-entry scenarios on Node.js 22.18.0, plus TypeScript checking and 145 offline tests on Node.js 24.21.0. The three native scenarios also appear in that 145-test suite. These mocked-transport checks verify client behavior; live Gateway availability remains a separate observation.

Keyless Robinhood mainnet read — fixed source snapshot

Run a first Robinhood Chain mainnet read without creating a wallet, account or API key.

With Git and Node.js 24.12 or newer:

git clone --branch keyless-read-2026.11.02 --depth 1 https://github.com/blockvectra/agent-quickstart.git
cd agent-quickstart
node src/public-read-cli.ts

No dependency installation or build is needed for this entry. Internet access is required. It reads the public chain directory, verifies chain ID 4663, then reads the latest block number: at most three serial HTTP requests, with no automatic retries. If the directory does not advertise the endpoint and required public methods, it stops before RPC.

For Node.js 18–23 or Node.js 24 before 24.12, use the existing dependency-based route after cloning:

npm ci --ignore-scripts
npm run read:public

npm start runs the separate wallet/account/API-key onboarding example. Use read:public or the direct command above for the keyless read. Indexed Data API and account tools still require an API key.

This is a fixed source snapshot of commit 338c522377ed940e130b360203110ed92cead3f6, not an npm publication. See the README at this version.

Validation reuses PR17: 145 offline tests, TypeScript check and the Node 24 CI run passed. Native execution was tested with Node 24.21 using mocked fetch, including before dependency installation. Node 24.12 and the older-version matrix were not individually run; this release does not assert current endpoint availability or a new live-chain test.

Keyless public reads by chain ID

Read a keyless public head on the chain you choose, without editing source or installing dependencies.

git clone --branch keyless-chain-id-2026.11.02 --depth 1 https://github.com/blockvectra/agent-quickstart.git
cd agent-quickstart
node src/public-read-cli.ts 56

Requires Node.js 22 (>=22.18) or Node.js >=24.12. Use 1 for Ethereum mainnet, or omit the argument for Robinhood mainnet (4663). The current public directory must advertise the selected chain and both required methods. The reader verifies eth_chainId before requesting the block number.

The read uses at most one directory request and two sequential JSON-RPC calls, with no automatic retries. No wallet, account, or API key is needed. Data API access and account operations still follow the existing authenticated flow.

Validation: 187 offline tests and typecheck passed with external network denied; seven native CLI cases are included in that total. No live RPC or customer adoption is claimed.