Net API

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitynone4 EndpointsREST

For Agents

Inspect and control EOSIO peer-to-peer network connections on a local nodeos node. Query peer status, connect to or disconnect from specific peers, and read network sync state.

Quickstart

Get started with Net 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:
"list eosio peer connections"

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

Capabilities

What an agent can do with Net API API.

List every active peer connection on the local nodeos node with sync and handshake details

Open a new peer-to-peer connection to a specific host and port

Disconnect from a named peer to drop unwanted or stale connections

Read current network status including handshake metadata and sync state

Inspect chain_id, node_id, and last_handshake fingerprints reported by each peer

GET STARTED

Start building with Net API API

Explore with Jentic

View OpenAPI Document

Use for: List all current peer connections on this nodeos instance, Connect to a new EOS peer at host eos1.example.com port 9876, Disconnect from peer eos2.example.com that is no longer responding, Get the current network status of my local EOSIO node

Not supported: Does not handle smart-contract execution, transaction submission, or block production — use for nodeos peer-to-peer connection management only.

Jentic publishes the only available OpenAPI document for Net API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Net API, keeping it validated and agent-ready. The Net API is the peer-networking control plane exposed by an EOSIO node, providing four endpoints for inspecting peer connections, opening or closing connections to specific peers, and reading current network status. It targets node operators who need to script connection management against a local nodeos instance running at the configurable host and port. All operations are POST requests against the local node and require no authentication because the endpoint is bound to a private interface.

Use Cases

Patterns agents use Net API API for, with concrete tasks.

★ Operating an EOSIO Block Producer Node

Block producers and node operators need to keep a healthy mesh of peer connections to stay in sync with the chain. The Net API exposes the four operations (connections, connect, disconnect, status) needed to script peer rotation, drop misbehaving peers, and confirm sync state without dropping into the nodeos CLI. Operators run it against a local-only port for safety.

Call POST /net/connections, parse the array, and disconnect any peer where connecting=true and last_handshake.time is older than 10 minutes.

Local Network Diagnostics for Chain Sync Issues

When an EOSIO node falls behind the head block, operators need to confirm whether peers are actually syncing or stalled. The /net/status and /net/connections endpoints together provide the chain_id, node_id, and per-peer syncing flags needed to diagnose connectivity faults in seconds.

Call POST /net/status, then POST /net/connections, and report the count of peers with syncing=true alongside the head-block-num field.

AI Agent Node Operations Assistant via Jentic

An AI ops agent can be wired through Jentic to act as an EOSIO node-watch tool: search 'list eos peer connections', load the operation schema, and execute against the operator's nodeos endpoint. Because the nodeos host and port are spec variables, the agent supplies them at execution time without code changes.

Use Jentic to find the connections operation, load its schema, and execute against host=localhost, port=8080 to return the live peer list.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for net api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/net/connections

List all current peer connections

POST

/net/connect

Connect to a new peer

POST

/net/disconnect

Disconnect from a peer

POST

/net/status

Read network status and handshake metadata

POST

/net/connections

List all current peer connections

POST

/net/connect

Connect to a new peer

POST

/net/disconnect

Disconnect from a peer

POST

/net/status

Read network status and handshake metadata

Why though Jentic?

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

Credential isolation

The Net API has no API key, but the nodeos host and port are stored as scoped configuration in Jentic so each operator's node target stays isolated and is never exposed in agent prompts.

Intent-based discovery

Agents search by intent (for example 'list eos peer connections' or 'check nodeos network status') and Jentic returns the matching Net operation with its schema, removing the need to read the EOSIO source for endpoint shapes.

Time to first call

Direct nodeos Net plugin integration: half a day to write a typed client and handle the handshake schema. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

U.S. EPA ECHO Clean Air Act

Public-data REST API — different domain but illustrative of authenticated public services agents may chain with internal node data

Pick this only if cross-referencing facility data with on-chain attestations stored on EOS; otherwise irrelevant.

Complementary

EODHD Financial Data API

Market data API — useful when correlating chain activity with traditional asset prices

Choose when an agent monitors EOS network health alongside EOS token price or related equities.

Complementary

Escrow.com API

Off-chain escrow service — pairs with on-chain transaction monitoring for hybrid settlement flows

Use when a workflow combines EOSIO chain state checks with off-chain fiat escrow.

FAQs

Specific to using Net API API through Jentic.

Why is there no official OpenAPI spec for Net API?

EOSIO does not publish an OpenAPI specification for the nodeos Net plugin. Jentic generates and maintains this spec so that AI agents and developers can call the Net API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Net API use?

The Net API has no authentication scheme defined in the spec because it is intended to bind to a private host and port on the operator's machine. Through Jentic the host and port are stored as scoped configuration so multiple operators can target their own nodes safely.

Can I list active peer connections with the Net API?

Yes. POST /net/connections returns an array of peer objects with peer host, connecting flag, syncing flag, and the last_handshake structure containing chain_id and node_id.

What are the rate limits for the Net API?

The nodeos process does not enforce HTTP rate limits on the Net plugin; throughput is bounded by the local node's CPU and the configured http-max-response-time-ms. Treat it as a local administrative endpoint and avoid tight polling loops.

How do I add a new peer through Jentic?

Search 'connect to eos peer'. Jentic returns the POST /net/connect operation, you load its schema, and execute with the peer host:port string. The scoped nodeos endpoint variable is injected at run time.

Can the Net API report which chain my node is on?

Yes. POST /net/status returns the handshake fields including chain_id, which uniquely identifies the chain the node is connected to.