Developer Tools · Integration
Alchemy
Add Alchemy to your product for your customers, and give your AI agents governed access to it.
Alchemy is developer infrastructure for blockchain applications, so this category is the least-wrong fit: it has services and API keys, but no builds or deployments in the CI sense. Access is per-network and the key is embedded in the host path, for example eth-mainnet.g.alchemy.com/v2/<key>, which means one customer credential is really a set of per-network endpoints and a mainnet key will simply not serve a testnet request. On top of standard JSON-RPC it exposes enhanced endpoints such as asset transfer history and token and NFT metadata that return paged results with a cursor, and those are the calls most products actually need because plain JSON-RPC cannot answer "what did this address do". Usage is metered in compute units rather than request counts, so one heavy log query can cost far more than many light balance reads and rate limiting shows up as HTTP 429 well before a request quota looks exhausted. Webhooks for address activity are configured per app, not per key, which trips up teams that assume one credential covers notifications too. fastn keeps each customer's Alchemy keys and network selection on their own connection and maintains the endpoints as networks are added or retired.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Alchemy app so chain reads run on their compute units and their rate limits
Show a wallet's token balances and transfer history inside your product without running your own node
Backfill NFT ownership and metadata for a collection your customer tracks, paging through the cursor to completion
Surface a per-network health view so a customer can see when a testnet key is being used against mainnet by mistake
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to trace recent transfers for a treasury address and summarise counterparties
Have an agent check whether a contract address has activity on the networks a tenant has configured, with each read audited per tenant
Let an agent report which of a tenant's Alchemy apps is consuming the most compute units this month
Example prompt
What transfers has our treasury wallet made on Ethereum mainnet in the past fortnight?
Set up Alchemy in 4 steps
- 01Enable the Alchemy connector from your fastn dashboard.
- 02Have each customer authorise their own Alchemy account, so calls run under their credentials rather than a shared key.
- 03Decide which services, builds and deployments your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Alchemy integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Alchemy integration without building it. Your customers connect their own Alchemy account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Alchemy update is not your on-call problem.
- One integration serves your product and your agents. The same governed Alchemy connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
Often used alongside
Tools the same teams tend to run next to Alchemy, across other categories.
Alchemy integration FAQ
How do I add an Alchemy integration to my product?
Enable the Alchemy connector in your fastn dashboard, then let each customer authenticate their own Alchemy account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Alchemy client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Alchemy account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Alchemy account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Alchemy integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to trace recent transfers for a treasury address and summarise counterparties
Who maintains the Alchemy integration?
fastn does. When Alchemy changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Alchemy events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Alchemy?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Alchemy integration?
A common starting point: let a customer connect their own Alchemy app so chain reads run on their compute units and their rate limits. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Alchemy integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Alchemy does not change your per-connector cost. You can start free with 3 connected accounts.
Add Alchemy to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.