Install Jentic One Beta

Connect the Blockchain Node Engine API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blockchain Node Engine API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fblockchainnodeengine" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fblockchainnodeengine" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Blockchain Node Engine API.

Provision dedicated Ethereum mainnet or testnet nodes in a Google Cloud region

List blockchainNodes under a project and location

Get node details including the JSON-RPC endpoint and current sync state

GET STARTED

Start building with Blockchain Node Engine API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Blockchain Node Engine API for, with concrete tasks.

★ Dedicated dApp Backend

Provision a dedicated Ethereum node so a dApp backend has a stable JSON-RPC endpoint without sharing rate limits with other tenants. blockchainNodes are managed at /v1/{parent}/blockchainNodes and the create call returns a long-running operation under /v1/{name}/operations. Once ready, the node exposes both a JSON-RPC and a WebSocket endpoint for the application.

Create a fullnode of type GETH on the MAINNET network in us-central1 under project myproj, then poll the operation until done.

Archive Node for Indexing

Run an archive node to support historical state queries that full nodes prune. blockchainNodes accept a nodeType of ARCHIVE and a network (MAINNET, GOERLI, SEPOLIA, or POLYGON_MAINNET). Archive nodes are larger and slower to provision but unlock building custom indexers and analytics over chain history.

Create an archive node of type GETH on POLYGON_MAINNET in us-east4 named indexer-1 under project myproj.

Operations Monitoring

List long-running operations on a node and inspect their state to track provisioning and updates. Operations are exposed at /v1/{name}/operations and individual operations at /v1/{name} where name is the operation resource. Cancel an in-progress provisioning if requirements change before it completes.

List all operations under projects/myproj/locations/us-central1 and return any in state RUNNING for blockchain nodes.

Agent-Driven Node Lifecycle

Let an AI agent take a request like 'spin up a Sepolia full node and tear it down after the test' and run the create+delete sequence through Jentic. The agent handles operation polling and reports the JSON-RPC endpoint when ready. OAuth credentials never leave your Jentic One instance.

From the request 'create a Sepolia testnet node, return its endpoint, and delete it after I confirm', execute create, poll until done, return the endpoint, then delete.

Key Endpoints

8 endpoints — blockchain node engine is google cloud's managed ethereum-compatible node service.

METHOD

PATH

DESCRIPTION

POST

/v1/{+parent}/blockchainNodes

Create a new blockchain node

GET

/v1/{+parent}/blockchainNodes

List blockchain nodes in a project and location

GET

/v1/{+name}

Get a node, operation, or location by resource name

PATCH

/v1/{+name}

Update a blockchain node

DELETE

/v1/{+name}

Delete a blockchain node

POST

/v1/{+name}:cancel

Cancel a long-running operation

GET

/v1/{+name}/operations

List long-running operations

POST

/v1/{+parent}/blockchainNodes

Create a new blockchain node

GET

/v1/{+parent}/blockchainNodes

List blockchain nodes in a project and location

GET

/v1/{+name}

Get a node, operation, or location by resource name

PATCH

/v1/{+name}

Update a blockchain node

DELETE

/v1/{+name}

Delete a blockchain node

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Blockchain Node Engine API by hand means setting up its Google OAuth 2.0 flow, refreshing scoped access tokens, and driving node provisioning through the long-running operations model yourself. Through Jentic you install once, import the Blockchain Node Engine API from the API Directory, store the OAuth credentials once, and your agent calls it.

Permission scoping

The API puts the project and node in the URL path (/v1/{+parent}/blockchainNodes and /v1/{+name}), so a rule can pin your agent to one project's blockchain nodes: it can create and inspect nodes there and nowhere else. You choose the operations it may call, so deleting a node is not included unless you add it.

Credential isolation

Your Google OAuth client credentials and refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived scoped access tokens and never sees the refresh token in its prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an Ethereum node on Google Cloud', and Jentic returns the create blockchainNode operation with its full ethereumDetails schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Blockchain Node Engine API through Jentic.

What authentication does the Blockchain Node Engine API use?

The API uses Google OAuth 2.0 with the cloud-platform scope. Through Jentic the OAuth refresh token is stored encrypted and the agent receives short-lived scoped access tokens for each call.

Can I provision an archive Ethereum node with this API?

Yes. POST /v1/{parent}/blockchainNodes with ethereumDetails.nodeType set to ARCHIVE and the desired network (MAINNET, GOERLI, SEPOLIA, or POLYGON_MAINNET) returns a long-running operation. Archive nodes take longer to sync because they retain full historical state.

What are the rate limits for the Blockchain Node Engine API?

Control-plane quotas are project-level: typically a small write QPS on the same node and bursty read QPS for list and get. Heavy provisioning churn is rate-limited per project. JSON-RPC traffic to the node itself is governed by the node's own throughput, not by this control-plane API.

How do I create a node through Jentic?

Search Jentic for 'create a Blockchain Node Engine node', load the schema for POST /v1/{parent}/blockchainNodes, and execute with blockchainType ETHEREUM and the desired ethereumDetails. Jentic forwards the OAuth token and returns the long-running operation name to poll.

Does this API submit transactions or read on-chain state?

No. This control-plane API only manages the node resource. Submit transactions and read state via the node's JSON-RPC endpoint (returned in the node's connectionInfo) using a standard Ethereum client library.

What networks are supported?

Ethereum mainnet, Goerli, Sepolia testnets, and Polygon mainnet are exposed via the ethereumDetails.network enum on the blockchainNode resource. Other chains are not currently supported by Blockchain Node Engine.

Can I limit what my agent is allowed to do with the Blockchain Node Engine API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and this API puts the project and node in the URL path (/v1/{parent}/blockchainNodes and /v1/{name}), so you can pin the agent to a single project's blockchain nodes and nowhere else. You choose exactly which operations it may call, so you can allow it to create, list, and get nodes while withholding the delete and cancel operations unless you add them. The Google OAuth credentials stay in your own instance, and the agent only ever receives short-lived scoped access tokens at execution time.

Google Blockchain Node Engine API

Name: Blockchain Node Engine API
Brand: Blockchain Node Engine API
Availability: InStock

Browse all Google APIs

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilityoauth28 EndpointsREST

For Agents

Provision and manage dedicated Ethereum nodes on Google Cloud's Blockchain Node Engine. Agents can create nodes, list operations, and inspect node endpoints.

Use for: I need to provision a dedicated Ethereum mainnet node, List all blockchain nodes in a project and location, Get the JSON-RPC endpoint for a specific node, Update a node to switch from full to archive type

Not supported: Does not submit transactions, broadcast blocks, or query on-chain state - use for managing dedicated blockchain node resources only.

Blockchain Node Engine is Google Cloud's managed Ethereum-compatible node service. The API provisions and manages dedicated archive and full nodes that you can query via JSON-RPC for on-chain data, transaction submission, and indexing without operating execution and consensus client pairs yourself. The API exposes blockchainNodes resources plus the surrounding long-running operations and locations metadata. It targets teams building wallets, indexers, analytics, and dApp backends that need a stable RPC endpoint with Google's reliability and IAM model.

Jentic One on Github View OpenAPI Document

Connect the Blockchain Node Engine API to your agent

Capabilities

Start building with Blockchain Node Engine API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Google Blockchain Node Engine API