Operate mempool.space public Bitcoin and Lightning explorer APIs through UXC with a curated OpenAPI schema, no-auth setup, and read-first guardrails.
Use this skill to run mempool.space public Bitcoin and Lightning explorer operations through uxc + OpenAPI.
Reuse the uxc skill for shared execution, auth, and error-handling guidance.
uxc is installed and available in PATH.https://mempool.space/api.https://raw.githubusercontent.com/holon-run/uxc/main/skills/mempool-space-openapi-skill/references/mempool-space-public.openapi.jsonThis skill covers a read-first mempool.space surface for:
This skill does not cover:
mempool.space public reads in this skill do not require authentication.
Use the fixed link command by default:
command -v mempool-space-openapi-cliuxc link mempool-space-openapi-cli https://mempool.space/api --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/mempool-space-openapi-skill/references/mempool-space-public.openapi.jsonmempool-space-openapi-cli -hInspect operation schema first:
mempool-space-openapi-cli get:/v1/fees/recommended -hmempool-space-openapi-cli get:/mempool -hmempool-space-openapi-cli get:/address/{address} -hmempool-space-openapi-cli get:/v1/lightning/search -hmempool-space-openapi-cli get:/v1/lightning/channels/{short_id} -hPrefer narrow reads before broader scans:
mempool-space-openapi-cli get:/v1/fees/recommendedmempool-space-openapi-cli get:/blocks/tip/heightmempool-space-openapi-cli get:/v1/lightning/statistics/latestExecute with key/value parameters:
mempool-space-openapi-cli get:/address/{address} address=bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlhmempool-space-openapi-cli get:/tx/{txid}/status txid=4d5d7f2d5dc69aa68a51887db07dd6d906f31f9141320f9f0b4bab76d735a47fmempool-space-openapi-cli get:/v1/lightning/search searchText=bfxmempool-space-openapi-cli get:/v1/lightning/channels public_key=033d8656219478701227199cbd6f670335c8d408a92ae88b962c49d4dc0e83e025 status=activemempool-space-openapi-cli get:/v1/lightning/channels/{short_id} short_id=835866331763769345get:/v1/fees/recommendedget:/mempoolget:/blocks/tip/heightget:/address/{address}get:/tx/{txid}/statusget:/v1/lightning/statistics/latestget:/v1/lightning/searchget:/v1/lightning/nodes/rankingsget:/v1/lightning/nodes/{public_key}get:/v1/lightning/channelsget:/v1/lightning/channels/{short_id}--text.ok, kind, protocol, data, error.tx/push, package submission, or internal routes.mempool.space is a public explorer service, so mempool state and Lightning rankings can move quickly. Re-query instead of assuming cached values remain current.get:/v1/lightning/channels/{short_id}, mempool.space currently accepts the channel id string even though the route label says short_id; prefer values returned by search or node channel listing.mempool-space-openapi-cli <operation> ... is equivalent to uxc https://mempool.space/api --schema-url <mempool_space_openapi_schema> <operation> ....references/usage-patterns.mdreferences/mempool-space-public.openapi.json