Testing access

How qualified teams can request a scoped 24-hour rpc edge test window.

Testing access is a short, scoped evaluation window for teams that want to benchmark rpc edge before subscribing.

We normally enable a 24-hour test window so you can validate endpoint reachability, client integration, latency, bandwidth, and the filter shape you expect to use in production.

What you can test

Testing access can cover:

  • HTTP JSON-RPC reads and simulations within shared-path limits;
  • WebSocket PubSub;
  • Yellowstone gRPC streams;
  • transaction sending through JSON-RPC or the relay client where enabled for your key;
  • decoded shreds (SubscribeDeshred) for qualified Desk or Custom evaluations.

Raw shred redistribution, archive/history RPC, broad account scans, and unbounded firehose tests are not part of the default testing window.

How to request access

  1. Create an account in the dashboard.
  2. Join Telegram and send a testing request with the same email or customer label used in the dashboard.
  3. Tell us what you want to test:
    • service path: RPC, WebSocket, Yellowstone gRPC, decoded shreds, or transaction sender;
    • preferred start time and timezone;
    • expected region and where your client runs;
    • rough filter shape, method mix, stream count, or transaction route;
    • whether you need IP allowlist access.
  4. We enable a scoped key or plan window and watch the first traffic with you when needed.

Terms

  • Prepare your client and filters before the window starts.
  • The standard testing window expires automatically after 24 hours.
  • You can upgrade to Trader, Desk, or Custom at any time.
  • Paid accounts and Custom evaluations are handled manually.
  • Longer vetted Trader trials may be available for deeper benchmarks, but they are not anonymous and are granted manually.
Testing access · rpc edge docs