// Operate Blocknative gas intelligence APIs through UXC with a curated OpenAPI schema, API-key auth, and read-first guardrails.
| name | blocknative-openapi-skill |
| description | Operate Blocknative gas intelligence APIs through UXC with a curated OpenAPI schema, API-key auth, and read-first guardrails. |
Use this skill to run Blocknative gas intelligence operations through uxc + OpenAPI.
Reuse the uxc skill for shared execution, auth, and error-handling guidance.
uxc is installed and available in PATH.https://api.blocknative.com.https://raw.githubusercontent.com/holon-run/uxc/main/skills/blocknative-openapi-skill/references/blocknative-gas.openapi.jsonThis skill covers a read-first Blocknative gas intelligence surface:
This skill does not cover:
Blocknative uses Authorization header auth. Some discovery and gas reads can work without a key, but this skill standardizes on authenticated requests because basefee-estimates and distribution require a valid API key.
Configure one API-key credential and bind it to api.blocknative.com:
uxc auth credential set blocknative \
--auth-type api_key \
--api-key-header Authorization \
--secret-env BLOCKNATIVE_API_KEY
uxc auth binding add \
--id blocknative \
--host api.blocknative.com \
--scheme https \
--credential blocknative \
--priority 100
Validate the active mapping when auth looks wrong:
uxc auth binding match https://api.blocknative.com
Use the fixed link command by default:
command -v blocknative-openapi-cliuxc link blocknative-openapi-cli https://api.blocknative.com --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/blocknative-openapi-skill/references/blocknative-gas.openapi.jsonblocknative-openapi-cli -hInspect operation schema first:
blocknative-openapi-cli get:/chains -hblocknative-openapi-cli get:/gasprices/blockprices -hblocknative-openapi-cli get:/gasprices/basefee-estimates -hPrefer narrow validation before broader polling:
blocknative-openapi-cli get:/chainsblocknative-openapi-cli get:/gasprices/blockprices chainid=1blocknative-openapi-cli get:/gasprices/basefee-estimatesExecute with key/value parameters:
blocknative-openapi-cli get:/gasprices/blockprices chainid=1 confidenceLevels=70,90,99blocknative-openapi-cli get:/gasprices/blockprices system=story network=mainnetblocknative-openapi-cli get:/gasprices/distribution chainid=1get:/chainsget:/gasprices/blockpricesget:/gasprices/basefee-estimatesget:/gasprices/distribution--text.ok, kind, protocol, data, error.blockprices can be polled without auth on some plans, but basefee-estimates and distribution require a valid key. Standardize on auth so mixed workflows do not fail mid-run.distribution is Ethereum-mainnet focused in the current docs. Do not assume multi-chain coverage there just because blockprices supports many chains.confidenceLevels narrow and explicit when you do not need the full default ladder.blocknative-openapi-cli <operation> ... is equivalent to uxc https://api.blocknative.com --schema-url <blocknative_openapi_schema> <operation> ....references/usage-patterns.mdreferences/blocknative-gas.openapi.jsonOperate Feishu or Lark IM APIs through UXC with a curated OpenAPI schema, tenant-token bearer auth, and chat/message guardrails.
Operate GitHub REST API through UXC with the official OpenAPI schema, explicit gh-to-uxc auth import, and read-first guardrails for repo, issue, pull request, and event workflows.
Operate X API v2 through UXC with the official OpenAPI schema, OAuth2 PKCE user-context auth, app-only bearer guidance, and read-first guardrails for timeline/bookmark/post workflows.
Discover and call remote schema-exposed interfaces with UXC. Use when an agent or skill needs to list operations, inspect operation schemas, and execute OpenAPI, GraphQL, gRPC, MCP, or JSON-RPC calls via one CLI contract.
Use a local QMD knowledge base through UXC over MCP stdio, with daemon-backed session reuse and typed retrieval flows that avoid repeated model warmup and unnecessary query-expansion latency.
Operate Notion Public API through UXC with a curated OpenAPI schema for search, block traversal, page reads, content writes, and data source/database inspection. Use when tasks need recursive reads or structured writes that Notion MCP does not expose directly.