Install Jentic One Beta

Connect the mempool.space REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the mempool.space REST 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%2Fmempool.space%2Fmempool" | 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%2Fmempool.space%2Fmempool" | 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 mempool.space REST API.

Look up the transaction history and UTXO set for a Bitcoin address via /api/address/{address}

Retrieve a block by hash including its full transaction list and miner data

Estimate next-block, half-hour, and hour fee rates from the live mempool

Track current mempool size, fee histogram, and unconfirmed transaction count

GET STARTED

Start building with mempool.space REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use mempool.space REST API for, with concrete tasks.

★ Wallet Fee Estimation

Self-custody wallets call /api/v1/fees/recommended to suggest a fee rate when the user composes a Bitcoin transaction. The endpoint returns next-block, half-hour, and hour estimates derived from real mempool state, which gives wallet UX a more accurate picture than static fee tables and helps users avoid over- or under-paying.

Call /api/v1/fees/recommended, return the next-block fee rate in sats/vB, and use it as the default in the wallet's send screen.

Bitcoin Address Monitoring

Treasury and accounting tools watch deposit addresses for incoming Bitcoin payments. /api/address/{address}/txs returns confirmed and unconfirmed transactions for an address, which lets a polling worker detect new payments, count confirmations, and reconcile against an order or invoice without running a node.

Poll /api/address/{address}/txs every 30 seconds, compare against the last seen txid, and emit a 'payment received' event when a new transaction reaches one confirmation.

Lightning Network Analytics

Lightning routing nodes and analytics dashboards consume mempool.space's Lightning endpoints to map node connectivity, channel capacity, and historical liquidity. The data underpins routing-fee strategy and capacity planning for node operators who need an external view of the public graph.

Pull the top 100 Lightning nodes by capacity, then fetch each node's channel list, and produce a CSV of node pubkey, alias, and aggregate capacity.

AI Agent On-Chain Research

An AI research agent can answer Bitcoin questions - 'what's the current next-block fee, what's the mempool backlog, is this transaction confirmed' - by chaining mempool.space calls. Through Jentic, the agent loads the address, transaction, and fee endpoints as discoverable tools and composes the answer without writing custom HTTP code.

Search Jentic for 'check bitcoin transaction status', execute /api/tx/{txid}, then if not confirmed call /api/v1/fees/recommended to suggest a fee bump.

Key Endpoints

42 endpoints — the mempool.

METHOD

PATH

DESCRIPTION

GET

/api/address/{address}

Get balance and transaction summary for an address

GET

/api/address/{address}/txs

List transactions for an address

GET

/api/address/{address}/utxo

List UTXOs for an address

GET

/api/v1/validate-address/{address}

Validate Bitcoin address format

GET

/api/block/{hash}

Get block by hash

GET

/api/v1/difficulty-adjustment

Get difficulty adjustment progress

GET

/api/v1/prices

Get current Bitcoin price

GET

/api/v1/historical-price

Get historical Bitcoin price

GET

/api/address/{address}

Get balance and transaction summary for an address

GET

/api/address/{address}/txs

List transactions for an address

GET

/api/address/{address}/utxo

List UTXOs for an address

GET

/api/v1/validate-address/{address}

Validate Bitcoin address format

GET

/api/block/{hash}

Get block by hash

GET

/api/v1/difficulty-adjustment

Get difficulty adjustment progress

GET

/api/v1/prices

Get current Bitcoin price

GET

/api/v1/historical-price

Get historical Bitcoin price

Why Jentic?

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

Setup

Wiring mempool.space by hand means hand-coding each address, block, fee, and price call against the mempool.space host and adding credentials only for a self-hosted instance behind auth. Through Jentic you install once, import the mempool.space REST API from the API Directory, store any self-hosted credential once, and your agent calls it.

Permission scoping

mempool.space puts the address, block hash, or txid in the URL path (/api/address/{address}, /api/block/{hash}), so a rule can pin your agent to reading data for a given address or block. You choose the operations it may call, and this API is read-only chain and mempool data, so nothing writes to the chain.

Credential isolation

Any credential for a self-hosted mempool.space instance is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check bitcoin transaction status' or 'estimate bitcoin fee', and Jentic returns the matching endpoint with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using mempool.space REST API through Jentic.

What authentication does the mempool.space REST API use?

The public hosted API requires no authentication - all 42 endpoints are open. Self-hosted mempool.space instances can sit behind a reverse proxy that adds auth; through Jentic any such credential is held in the encrypted vault and injected at request time.

Can I get a fee estimate for a Bitcoin transaction with mempool.space?

Yes. /api/v1/fees/recommended returns next-block, 30-minute, and hour fee rates in sats/vB derived from live mempool state, and /api/v1/fees/mempool-blocks exposes the projected fee bands of the next several blocks.

What are the rate limits for the mempool.space REST API?

The hosted API enforces fair-use rate limits per IP that are not numerically published in the spec. Heavy users should run a self-hosted mempool.space instance - the project is fully open source - or use a paid mirror to bypass shared limits.

How do I look up a Bitcoin address through Jentic?

Run `pip install jentic`, search for `look up bitcoin address`, load /api/address/{address}, and execute with the address. Jentic returns the address summary including balance and recent transaction count.

Does the mempool.space API cover the Lightning Network?

Yes. The API exposes Lightning Network node and channel data, including node capacity, alias, and channel topology, which lets analytics tools and routing nodes consume the public graph without running their own Lightning daemon.

Can I limit what my agent is allowed to do with the mempool.space REST API?

Yes. Because you run Jentic One yourself, your own rules decide which mempool.space operations and credentials the agent may use. This API puts the address, block hash, or txid in the URL path (/api/address/{address}, /api/block/{hash}), so you can pin the agent to reading data for a specific address or block and pick exactly which endpoints it may call. Since every operation is read-only chain and mempool data, nothing the agent does can write to the Bitcoin network.

mempool.space REST API

Name: mempool.space REST API
Brand: mempool.space REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyFinanceBankingnone42 EndpointsREST

For Agents

Query Bitcoin blockchain data - blocks, transactions, addresses, mempool, mining stats, Lightning Network, and fee estimates. Open public API, no authentication required.

Use for: Get the current Bitcoin transaction fee estimate for next-block confirmation, Look up the balance and transaction history for a Bitcoin address, Retrieve the most recent block and its transactions, Check whether a transaction is still in the mempool

Not supported: Does not broadcast transactions in a wallet, manage private keys, or trade - use for read-only Bitcoin chain, mempool, and Lightning data only.

The mempool.space REST API exposes Bitcoin blockchain data - blocks, transactions, addresses, mempool state, mining statistics, Lightning Network nodes and channels, and fee estimates - across 42 endpoints. The API is open and unauthenticated for public use, which makes it well suited to wallets, explorers, fee-estimation services, and on-chain analytics tooling that need direct access to Bitcoin network state without operating a full node.

Jentic One on Github View OpenAPI Document