Speed FAQs

Question 1

Does Speed store my personal private blockchain key?

Accepted Answer

No, Speed explicitly states that the server never touches your `PRIVATE_KEY`. This key remains securely stored locally in your `~/.speed/.env` file, with Speed only facilitating the secure exchange of *API keys* for blockchain services, not your personal wallet private key.

Question 2

How does Speed ensure the security of API keys?

Accepted Answer

Speed enhances security by centralizing API key management on a server, meaning keys are never stored on client machines or accessed by agents. It utilizes secure API key handshakes and encrypted credential transfer (RSA-OAEP-AES256GCM) to protect keys during transit, ensuring only the intended client can decrypt them.

Question 3

Can Speed be used for remote connections and access?

Accepted Answer

Yes, Speed supports remote connections. By configuring the server with Streamable HTTP, clients on different machines can securely connect to access API keys, ensuring that your sensitive credentials remain on a trusted server while still providing remote agents with necessary access.

Question 4

What is Speed and its primary purpose?

Accepted Answer

Speed is a developer tool designed to facilitate secure and automated API key exchange for blockchain services. It allows Speed-CLI and agents to access services like Alchemy, 0x, Squid, and OpenSea without requiring manual setup or local storage of sensitive API keys on client machines.

Question 5

Which blockchain API providers can Speed integrate with?

Accepted Answer

Speed offers out-of-the-box integration with major blockchain API providers including Alchemy, 0x, Squid, and OpenSea. This enables automated access to services like fetching balances, swap/bridge quotes, and performing actions via Speed-CLI.

Speed

Speed

Key Features

Use Cases

Key Features

Use Cases