API / OAuth Management
Last updated
Last updated
Evolve Network WebApp allows you to use API and OAuth management to enable users to equip their agents with the ability to execute real-world tasks securely. Let's talk about how users can add API keys, manage OAuth tokens, and securely link them to their Web3 wallets to ensure that sensitive information is protected and only accessible when needed.
API Key and OAuth Token Management: Users can add and manage API keys and OAuth tokens for third-party tools within the Evolve WebApp.
Web3 Wallet Integration: API keys and OAuth tokens are securely linked to users’ Web3 wallets and are not stored in the Evolve Network database.
Secure Access: API keys and tokens are hashed and encrypted, making them available only when users connect their Web3 wallets.
Users can navigate to the API management section of the WebApp to add API keys and OAuth tokens. The interface allows users to enter the necessary credentials and select the corresponding third-party tools.
Encryption and Hashing:
When users add an API key or OAuth token, the WebApp hashes and encrypts the credentials using a robust encryption algorithm (e.g., AES-256). The encrypted credentials are then linked to the user's Web3 wallet address.
Web3 Wallet Integration:
Users are required to connect their Web3 wallets to the WebApp for accessing any third party services by their agent workflows developed on the platform.
The encrypted API keys and OAuth tokens are stored as part of the user's wallet metadata, leveraging blockchain technology to ensure security and immutability.
No Storage in Database:
The WebApp does not store API keys or OAuth tokens in its database, reducing the risk of data breaches. Instead, encrypted credentials are stored in the user’s Web3 wallet, ensuring that only the user can access them.
Secure Access only during Wallet Connection: When users need to use their API keys or OAuth tokens, they must connect their Web3 wallet to the WebApp.
Transaction Signing: All actions involving API keys or OAuth tokens require transaction signing with the user’s private key to ensure that only the owner of the Web3 wallet can authorize the use of their credentials.