Alchemy

The Alchemy integration generates one Endpoint per network in the Gateway catalog and applies your Alchemy API key as the Endpoint credential. It uses the Gateway’s catalog independently of the apps in your Alchemy dashboard.

Credential

Provide an Alchemy API key.

The key is written into each synchronized Endpoint as a path credential and appended to the generated URL when the Gateway forwards a request. Enable the key for every selected network in your Alchemy plan, then run the Endpoint health checks.

Network coverage

This covers every combination in Supported networks. TRON networks produce two Endpoints, one for JSON-RPC and one for the native HTTP API.

Synchronization behavior

Synchronization starts from a built-in network table and then refines it with the Alchemy public network catalog. Generated Endpoint URLs use the form https://<network-subdomain>.g.alchemy.com/v2, with the API key applied as a path credential.

The built-in network set remains available when the public catalog is temporarily unavailable. In that mode, synchronization publishes created and updated Endpoints while preserving existing inventory.

Verification checklist

• Keep the selected networks enabled for the API key in the Alchemy dashboard.
• Include every required network in the Provider selection.
• Run synchronization, review Activity, then run the health check for each synchronized Endpoint.

See the Alchemy RPC integration overview for how synchronized Endpoints are used in Routes. Return to the Providers overview for the shared synchronization workflow and Endpoint lifecycle.