> alchemy-deploy-integration
Deploy Alchemy-powered Web3 applications to Vercel, Cloud Run, and AWS. Use when deploying dApps with server-side Alchemy SDK access, configuring API key secrets, or setting up RPC proxy endpoints. Trigger: "deploy alchemy", "alchemy Vercel", "alchemy Cloud Run", "alchemy production deploy", "dApp deploy".
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/alchemy-deploy-integration?format=md"Alchemy Deploy Integration
Overview
Deploy Alchemy-powered dApps with proper API key security. The API key must stay server-side — never ship it to the browser.
Instructions
Step 1: Vercel Deployment
# Add Alchemy API key as Vercel secret
vercel secrets add alchemy_api_key "your-api-key"
vercel link
vercel --prod
// vercel.json
{
"env": { "ALCHEMY_API_KEY": "@alchemy_api_key" },
"functions": { "api/**/*.ts": { "maxDuration": 30 } }
}
// api/balance/[address].ts — Vercel serverless function
import { Alchemy, Network } from 'alchemy-sdk';
const alchemy = new Alchemy({
apiKey: process.env.ALCHEMY_API_KEY,
network: Network.ETH_MAINNET,
});
export default async function handler(req: any, res: any) {
const { address } = req.query;
if (!/^0x[a-fA-F0-9]{40}$/.test(address)) {
return res.status(400).json({ error: 'Invalid address' });
}
const balance = await alchemy.core.getBalance(address);
res.json({ balance: balance.toString() });
}
Step 2: Cloud Run Deployment
# Build and deploy
gcloud builds submit --tag gcr.io/${PROJECT_ID}/alchemy-dapp
gcloud run deploy alchemy-dapp \
--image gcr.io/${PROJECT_ID}/alchemy-dapp \
--region us-central1 \
--set-secrets=ALCHEMY_API_KEY=alchemy-api-key:latest \
--allow-unauthenticated
Step 3: Health Check
// api/health.ts
import { Alchemy, Network } from 'alchemy-sdk';
export default async function handler(_req: any, res: any) {
try {
const alchemy = new Alchemy({ apiKey: process.env.ALCHEMY_API_KEY, network: Network.ETH_MAINNET });
const block = await alchemy.core.getBlockNumber();
res.json({ status: 'healthy', latestBlock: block });
} catch {
res.status(503).json({ status: 'unhealthy' });
}
}
Output
- Vercel deployment with API key in server-side functions
- Cloud Run with GCP Secret Manager
- Health check endpoint verifying Alchemy connectivity
Resources
Next Steps
For webhook handling, see alchemy-webhooks-events.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".