This is a human-readable page. If you're an agent, fetch /vendor/alchemy/AgentRouting.json or /vendor/alchemy/AgentContext.json directly.

alchemy.com

last checked 2026-06-29

Overview

Does alchemy.com support MCP?

Yes. alchemy.com has a confirmed MCP implementation. Read-only and analytical access to blockchain data across 100+ networks via 168 tools, covering token prices, NFT metadata, transaction history, smart contract simulation and tracing, account abstraction, ENS resolution, Solana DAS, and wallet portfolio queries.

What agentic protocols does alchemy.com support?

As of 2026-06-29, alchemy.com has confirmed support for ACP, MCP, MPP, and proprietary.

Is alchemy.com's API publicly accessible or partner-gated?

Open.

Does alchemy.com explicitly prohibit automated access?

Yes. alchemy.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.

Is alchemy.com agent-ready?

Yes. alchemy.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.

Protocols

A2A unable to verify

No usable finding available for this protocol (no legitimate scan available within the candidate window).

ACP confirmed present

Unified ACP acceptance layer via AgentPay product — Alchemy's agentpay.alchemy.com explicitly lists ACP as one of several agent payment protocols it handles, enabling merchants/businesses to accept ACP-mediated checkout alongside x402, MPP, and UCP through a single integration point.

Alchemy's AgentPay product (agentpay.alchemy.com) explicitly lists ACP (Agentic Commerce Protocol) as a supported protocol alongside x402, MPP, and UCP, positioning itself as a unified agent payment proxy. Alchemy is not a named launch partner in the OpenAI/Stripe ACP announcement (those include URBN, Coach, Revolve, Ashley Furniture), but self-documents ACP support as part of its own product offering. Vendor-specific evidence is confirmed on Alchemy's own domain.

AP2 not found

No evidence found that alchemy.com is among AP2's 60+ launch partners or has any stated AP2 integration. Alchemy.com (a blockchain infrastructure/API provider) publicly supports x402 and MPP for agent payments, and its AgentPay product is described as protocol-agnostic, but AP2 is not mentioned in any Alchemy documentation or announcement found. Named AP2 launch partners include Mastercard, American Express, PayPal, Adyen, Coinbase, Etsy, Forter, Intuit, Revolut, Salesforce, and Worldpay — alchemy.com is not among them.

MCP confirmed present

Read-only and analytical access to blockchain data across 100+ networks via 168 tools, covering token prices, NFT metadata, transaction history, smart contract simulation and tracing, account abstraction, ENS resolution, Solana DAS, and wallet portfolio queries. No write/transaction-submission capability described in official docs.

Alchemy operates an officially documented, hosted MCP server at https://mcp.alchemy.com/mcp (docs: https://www.alchemy.com/docs/alchemy-mcp-server), with a corresponding open-source reference implementation on GitHub at https://github.com/alchemyplatform/alchemy-mcp-server. The server is confirmed compatible with Claude Desktop, Cursor, VS Code Copilot, and Claude Code via an official plugin. Access is open to any Alchemy account holder via OAuth browser login with no separate partner enrollment required.

MPP confirmed present

Listed as a launch-day MPP-integrated service provider, allowing AI agents to purchase Alchemy credits (developer infrastructure/API credits) via Stripe credit cards through the Tempo settlement layer; scope is Alchemy's own API credit purchasing surface, not a broader payments reseller role.

Alchemy confirmed as a named launch partner in the MPP payment directory, which included over 100 services at launch covering developer infrastructure. Alchemy's own blog post (https://www.alchemy.com/blog/tempo-mainnet-alchemy) describes agents purchasing Alchemy credits via Stripe credit cards through the Tempo/MPP rail. Evidence is vendor-specific (Alchemy's own publication) supporting confirmed_present.

NLWeb not found

Microsoft's NLWeb launch partners list (as documented by Microsoft's own announcements) includes Inception, Chicago Public Media, Common Sense Media, DDM (Allrecipes & Serious Eats), Milvus, Shopify, and Snowflake. Alchemy.com does not appear among any named NLWeb pioneers or partner lists. No vendor-specific evidence of NLWeb adoption at alchemy.com was found.

UCP not found

Four targeted searches found no evidence that alchemy.com (a Web3 blockchain developer platform) has implemented or announced support for the Universal Commerce Protocol. Searches surfaced only general UCP ecosystem content (Google, Shopify, ucp.dev) and unrelated alchemy.com products (AgentCard, AgentPay, Web3 wallet tools). No alchemy.com documentation, blog post, or partnership announcement references UCP integration; the not_found classification reflects an actual search of available material rather than a blocked or inaccessible check.

WebMCP not found

No evidence found that alchemy.com has implemented or announced WebMCP support. Alchemy does maintain a standard MCP server (mcp.alchemy.com) exposing blockchain API tools, but this is a remote server-side protocol, not the browser-layer WebMCP API. Known WebMCP early-preview participants are documented by Google/Chrome and Cloudflare; alchemy.com does not appear among them.

x402 not found

Alchemy (alchemy.com) published an educational blog post explaining x402 (https://www.alchemy.com/blog/how-x402-brings-real-time-crypto-payments-to-the-web), but this is editorial content only — no evidence that Alchemy has implemented x402 on its own API endpoints or joined the x402 Foundation as a member. Named founding members of the x402 Foundation include Google, Visa, Stripe, AWS, Mastercard, Circle, Microsoft, Shopify, and Cloudflare; Alchemy does not appear among them. Choosing not_found rather than confirmed_absent because no vendor-specific deprecation or opt-out statement was found — absence of evidence of adoption is the basis.

openai_apps_sdk not found

Alchemy (alchemy.com) previously built a ChatGPT Plugin for OpenAI's Plugin Marketplace (announced ~2023) that provided real-time blockchain data via natural language queries, but that plugin platform was deprecated by OpenAI in early 2024 and replaced by GPTs/Apps. No evidence was found that Alchemy subsequently published an integration specifically built on OpenAI's Apps SDK (the newer MCP-backed framework announced in 2025). Alchemy does have active AI agent infrastructure (alchemy.com/alchemy-ai) but no ChatGPT Apps SDK listing or documentation was identified.

proprietary confirmed present

Node RPC endpoint layer (JSON-RPC 2.0 over HTTPS/WSS to blockchain nodes, with Alchemy-specific enhanced methods such as `alchemy_getTokenBalances`, `alchemy_getAssetTransfers`, WebSocket subscriptions) and separate indexed Data APIs (NFT metadata/ownership, token balances, transaction history) and Account Kit smart-wallet APIs (smart account deployment, gas sponsorship, batch transactions) — three distinct proprietary sub-surfaces all requiring an Alchemy API key

Alchemy exposes multiple proprietary API surfaces under docs.alchemy.com: (1) enhanced JSON-RPC node endpoints with Alchemy-prefixed methods alongside standard ETH methods, (2) REST Data APIs (NFT, token, transaction history) with OpenAPI specs published at dev-docs.alchemy.com, and (3) Account Kit / Smart Wallets APIs for smart account abstraction. All surfaces require a self-serve API key obtained via dashboard.alchemy.com; free tier is available with paid/enterprise tiers above it. None of these surfaces are named standards — they are Alchemy-proprietary.

self_declared_discovery unable to verify

No usable finding available for this protocol (no legitimate scan available within the candidate window).

Summary

Has agent interface: true

Prioritize integration via Alchemy's officially documented MCP server (https://mcp.alchemy.com/mcp) using OAuth browser login — this is the most mature, openly accessible agent interface. For payment/commerce use cases, review AgentPay (agentpay.alchemy.com) for ACP and MPP protocol support. Verify ACP self-documentation against any upstream ACP specification to confirm interoperability before relying on it for routing.

AgentContext

Five discrepancy categories were checked for alchemy.com (Alchemy Insights, Inc.): pricing deception, availability/inventory misrepresentation, merchant-of-record identity, policy enforcement gaps, and undisclosed mid-transaction constraints. Searches across all five categories returned no qualifying findings — no regulatory actions, court filings, FTC complaints, or independently verified consumer reports surfaced for any category. Minor items noted (compute-unit pricing complexity, case-by-case refund handling, free-tier rate limits) were either self-disclosed in Alchemy's own documentation or did not meet the threshold for a verified discrepancy. Because no findings were generated, no human handoff triggers can be grounded in this evidence base.