Blockchain Node Engine API

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

✓ Official Vendor SpecDeveloper 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.

Quickstart

Get started with Blockchain Node Engine API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"provision an Ethereum node on Google Cloud"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Blockchain Node Engine API 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

Update node configuration such as type and Polygon-specific settings

GET STARTED

Start building with Blockchain Node Engine API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Blockchain Node Engine API 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 the Jentic vault.

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 though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive short-lived scoped access tokens at execution time, so node provisioning credentials never sit in agent context.

Intent-based discovery

Agents search Jentic with intents like 'create an Ethereum node on Google Cloud' and Jentic returns the create blockchainNode operation with its full ethereumDetails schema.

Time to first call

Direct integration: half a day to a day for OAuth, the long-running operation pattern, and the node config. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Kubernetes Engine API

Hosts the dApp backend that consumes the node's JSON-RPC endpoint.

Use GKE to run application workloads; use Blockchain Node Engine to provide their RPC dependency.

Alternative

Alchemy API

Multi-tenant Ethereum and L2 node-as-a-service with enhanced APIs.

Choose Alchemy for shared, feature-rich endpoints; choose Blockchain Node Engine for dedicated nodes inside a Google Cloud project.

Alternative

QuickNode API

Multi-chain managed RPC provider supporting many networks.

Choose QuickNode for broad chain coverage; choose Blockchain Node Engine for tight Google Cloud and IAM integration.

FAQs

Specific to using Blockchain Node Engine API 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.