Providers

Create the connection

Open Endpoints, switch to Providers, select Connect provider, and configure:

• Name: identifies this connection in the dashboard;
• Vendor: Alchemy, QuickNode, Chainstack, dRPC, or Tenderly; it cannot be changed after creation;
• API key / secret: the credential issued by the vendor;
• Automatic sync: whether to refresh Endpoint inventory once per day;
• Networks: optionally limits synchronization to selected networks supported by the vendor.

The dashboard connection flow enables daily sync by default; you can turn it off before saving. The Management API defaults sync_enabled to false when the field is omitted. When daily sync is enabled, the platform assigns the account one of 96 UTC windows and synchronizes its Providers sequentially once per day. A missed window is not caught up; synchronization resumes in the next daily window. You can select Sync now whenever an immediate refresh is needed.

An account can have up to 6 undeleted Providers. Disabled Providers count toward this limit; deleting one frees the capacity.

Choose networks

Leave the selection empty to synchronize every network discovered by the vendor and supported by that Provider integration. Select one or more chain and network pairs to synchronize only those networks.

The selection narrows vendor discovery to networks already supported by the integration. Run synchronization again after changing it to apply the new scope.

Review the result

Synchronization can apply these Endpoint lifecycle changes internally:

The Provider row shows the last synchronization status:

• Never synced: synchronization has not run yet;
• Success: discovery and updates completed;
• Partial: usable results were published, but some Endpoints or vendor catalog data could not be processed completely;
• Failed: discovery failed and no destructive inventory changes were published.

Open the Provider row’s Activity tab to inspect persistent synchronization runs. A run records whether it was manual or scheduled, its queued and started times, its current queued, running, success, partial, or failed state, the aggregate number of Endpoint changes, and a failure message when applicable. The public run record does not expose a per-Endpoint action list; inspect the Provider’s Endpoints tab for the resulting inventory state.

An incomplete discovery does not bulk-archive Endpoints omitted from its response. When vendor metadata is missing for one Endpoint, its existing record is also preserved so a temporary vendor failure does not cause a destructive update. Vendors differ in what happens when their catalog is unreachable; see the vendor page for its exact behavior.

Add Endpoints to a Gateway Route

Open the Provider tab under Endpoints and review the synchronized records. The Provider manages connection details such as chain, network, URL, and authentication, so these fields cannot be edited like a manually created Endpoint.

For manual control, open the target App, select the Gateway for the same chain and network, and add the Endpoint to its default JSON-RPC Route. An Endpoint participates in routing, load balancing, and failover only after a Route references it.

Alternatively, select the Provider in the App creation flow. The App association publishes matching synchronized Endpoints to that App’s JSON-RPC and HTTP API Routes and keeps those automatically managed targets aligned with later Provider synchronizations. It does not change Routes belonging to another App. Clearing or replacing the App Provider removes the old Provider’s automatically managed targets; manually selected Route targets remain under manual control.