Agent skill

alchemy-openapi-skill

Operate Alchemy Prices API reads through UXC with a curated OpenAPI schema, path-templated API-key auth, and read-first guardrails.

Stars 1,878
Forks 294

Install this agent skill to your Project

npx add-skill https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/alchemy-openapi-skill

SKILL.md

Alchemy Prices API Skill

Use this skill to run Alchemy Prices API operations through uxc + OpenAPI.

Reuse the uxc skill for shared execution, auth, and error-handling guidance.

Prerequisites

  • uxc is installed and available in PATH.
  • Network access to https://api.g.alchemy.com.
  • Access to the curated OpenAPI schema URL:
    • https://raw.githubusercontent.com/holon-run/uxc/main/skills/alchemy-openapi-skill/references/alchemy-prices.openapi.json
  • An Alchemy API key.

Scope

This v1 skill intentionally covers the narrow Prices API surface:

  • token price lookup by symbol
  • token price lookup by contract address
  • historical token prices

This skill does not cover:

  • node JSON-RPC
  • NFT or portfolio APIs
  • write operations
  • the broader Alchemy API surface
  • multi-symbol batch lookup in one uxc call

Authentication

Alchemy Prices API places the API key in the request path: /prices/v1/{apiKey}/....

Configure one API-key credential with a request path prefix template:

bash
uxc auth credential set alchemy-prices \
  --auth-type api_key \
  --secret-env ALCHEMY_API_KEY \
  --path-prefix-template "/prices/v1/{{secret}}"

uxc auth binding add \
  --id alchemy-prices \
  --host api.g.alchemy.com \
  --scheme https \
  --credential alchemy-prices \
  --priority 100

Validate the active mapping when auth looks wrong:

bash
uxc auth binding match https://api.g.alchemy.com

Core Workflow

  1. Use the fixed link command by default:

    • command -v alchemy-openapi-cli
    • If missing, create it: uxc link alchemy-openapi-cli https://api.g.alchemy.com --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/alchemy-openapi-skill/references/alchemy-prices.openapi.json
    • alchemy-openapi-cli -h
  2. Inspect operation schema first:

    • alchemy-openapi-cli get:/tokens/by-symbol -h
    • alchemy-openapi-cli post:/tokens/by-address -h
    • alchemy-openapi-cli post:/tokens/historical -h
  3. Start with narrow single-asset reads before batch historical requests:

    • alchemy-openapi-cli get:/tokens/by-symbol symbols=ETH currency=USD
    • alchemy-openapi-cli post:/tokens/by-address '{"addresses":[{"network":"eth-mainnet","address":"0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"}],"currency":"USD"}'
  4. Use positional JSON only for the POST endpoints:

  • alchemy-openapi-cli post:/tokens/historical '{"symbol":"ETH","startTime":"2025-01-01T00:00:00Z","endTime":"2025-01-07T00:00:00Z","interval":"1d","currency":"USD"}'

Operations

  • get:/tokens/by-symbol
  • post:/tokens/by-address
  • post:/tokens/historical

Guardrails

  • Keep automation on the JSON output envelope; do not use --text.
  • Parse stable fields first: ok, kind, protocol, data, error.
  • Treat this v1 skill as read-only and prices-only. Do not imply RPC, trade execution, or wallet mutation support.
  • API keys are sensitive because they appear in the request path. Use --secret-env or --secret-op, not shell history literals, when possible.
  • /tokens/by-symbol is query-based in the live API.
  • The live API supports repeated symbols= parameters, but this v1 skill intentionally narrows that endpoint to a single symbols=<TOKEN> query because current uxc query argument handling does not reliably execute array-shaped query parameters.
  • Historical requests can expand quickly. Keep time windows tight unless the user explicitly wants a larger backfill.
  • alchemy-openapi-cli <operation> ... is equivalent to uxc https://api.g.alchemy.com --schema-url <alchemy_openapi_schema> <operation> ....

References

Expand your agent's capabilities with these related and highly-rated skills.

LeoYeAI/openclaw-master-skills

audit-website

Audit websites for SEO, performance, security, technical, content, and 15 other issue cateories with 230+ rules using the squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use to discover and asses website or webapp issues and health.

1,878 294
Explore
LeoYeAI/openclaw-master-skills

firecrawl

Web search and scraping via Firecrawl API. Use when you need to search the web, scrape websites (including JS-heavy pages), crawl entire sites, or extract structured data from web pages. Requires FIRECRAWL_API_KEY environment variable.

1,878 294
Explore
LeoYeAI/openclaw-master-skills

computer-use

Full desktop computer use for headless Linux servers. Xvfb + XFCE virtual desktop with xdotool automation. 17 actions (click, type, scroll, screenshot, drag, etc). Unlike OpenClaw's browser tool, operates at the X11 level so websites cannot detect automation. Includes VNC for live viewing.

1,878 294
Explore
LeoYeAI/openclaw-master-skills

social-media-analyzer

Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use for analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards.

1,878 294
Explore
LeoYeAI/openclaw-master-skills

business-growth-skills

4 production-ready business and growth skills: customer success manager with health scoring and churn prediction, sales engineer with RFP analysis, revenue operations with pipeline and GTM metrics, and contract & proposal writer. Python tools included (all stdlib-only). Works with Claude Code, Codex CLI, and OpenClaw.

1,878 294
Explore
LeoYeAI/openclaw-master-skills

contract-and-proposal-writer

Contract & Proposal Writer

1,878 294
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results