360 Secure SkillHub
360 安全技能中心

Alchemy

该 Skill 通过 OOMOL 的 oo CLI 调用 alchemy 连接器，由服务端注入凭证，查询以太坊主网数据，提供资产转账、NFT 元数据与持仓、ERC-20 代币余额与元数据共五个只读动作；执行前先用 schema 获取输入契约，再以 JSON 载荷运行动作，返回结构化响应与执行 ID。

oomol
oomol
热度 52.26
最近更新 2026-09-15 13:07:59
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / API 集成

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-alchemy
Metadata
name
oo-alchemy
description
Alchemy (alchemy.com). Use this skill for ANY Alchemy request — searching and reading data. Whenever a task involves Alchemy, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Alchemy","author":"OOMOL","version":"1.0.3","services":["alchemy"],"icon":"https://static.oomol.com/logo/third-party/alchemy.svg"}

Alchemy

Operate Alchemy through your OOMOL-connected account. This skill calls the alchemy connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Alchemy. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "alchemy" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "alchemy" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • get_asset_transfers — Retrieve historical asset transfers for Ethereum mainnet addresses through Alchemy.
  • get_nft_metadata — Retrieve metadata for a specific NFT from Alchemy Ethereum mainnet.
  • get_nfts_for_owner — Retrieve NFTs currently owned by an address from Alchemy Ethereum mainnet.
  • get_token_balances — Retrieve ERC-20 token balances for a wallet address from Alchemy Ethereum mainnet.
  • get_token_metadata — Retrieve ERC-20 token metadata for one contract from Alchemy Ethereum mainnet.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Alchemy state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Alchemy is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=alchemy

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources