Back to Details

alchemy-codex

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Alchemy Codex

Alchemy Codex

Use this skill when the user wants to build with Alchemy in Codex but has not yet chosen how requests should be authenticated.
This skill routes to:
  • alchemy-api
    for standard API key-based access to Alchemy JSON-RPC, Data APIs, Webhooks, and Wallets
  • agentic-gateway
    for gateway-based access using an API key or wallet-based payment flows
当用户希望在Codex中使用Alchemy进行开发，但尚未选定请求认证方式时，请使用此技能。
本技能可路由至：
  • alchemy-api
    ：通过标准API密钥访问Alchemy JSON-RPC、数据API、Webhooks和钱包服务
  • agentic-gateway
    ：通过API密钥或基于钱包的支付流程实现网关访问

Required first question

必问首题

Before making a network call or implementation choice, ask:
Do you want to use an existing Alchemy API key, or should I use the agentic gateway flow instead?
Then route as follows:
  • If the user chooses an API key, switch to 
    alchemy-api
  • If the user chooses the gateway flow, switch to 
    agentic-gateway
在发起网络请求或确定实现方案前，询问：
你想要使用现有的Alchemy API密钥，还是我应该改用agentic gateway流程？
随后按如下规则路由：
  • 若用户选择API密钥，切换至
    alchemy-api
  • 若用户选择网关流程，切换至
    agentic-gateway

Use this skill for

适用场景

  • broad Alchemy integration requests where auth is still undecided
  • onboarding a developer to the right Alchemy access path
  • routing requests that mention Alchemy generally rather than a specific API surface
  • 认证方式尚未确定的泛Alchemy集成需求
  • 引导开发者选择合适的Alchemy访问路径
  • 路由仅泛泛提及Alchemy而非特定API接口的请求

Typical tasks after routing

路由后的典型任务

  • JSON-RPC reads and writes
  • Token, NFT, Transfers, Prices, and Portfolio APIs
  • transaction simulation and traces
  • Webhooks / Notify setup
  • Account Kit and wallet infrastructure
  • agentic gateway access via x402 or MPP
  • JSON-RPC读写操作
  • 代币、NFT、转账、价格和投资组合相关API调用
  • 交易模拟与追踪
  • Webhooks / 通知功能配置
  • Account Kit和钱包基础设施搭建
  • 通过x402或MPP访问agentic gateway