Create or update an HTTP node
Creates or updates an HTTP RPC node for one of the authenticated provider’s plans. The URL must be a public http(s) endpoint (loopback, private, and link-local hosts are rejected). The node is screened before persistence; the request fails with 400 when a mandatory screening test does not pass. Returns the upserted node set to a healthy status.
Authorizations
Management token from the RouteMesh dashboard (Settings → Management Tokens). Required for customer API endpoints (/api-keys, /usage). Tokens are prefixed rmtm_ and scoped to your account. Authenticate by passing the token in the X-Api-Key header. Separate from RPC service keys (rm_), which authenticate dApp traffic to the routing layer.
Body
Plan ID the node belongs to (must be owned by the provider).
Public http(s) endpoint URL of the node.
Virtual machine type, e.g. evm.
Requests per interval (0 = unlimited).
Rate limit window in seconds.
Node source (default provider).
provider, website, erpc, node_request, new_chain_request 
