Credentials

​

Overview

Ardor’s credential system allows you to:

• Generate API keys for accessing Ardor’s core platform
• Connect to third-party services
• Create custom credentials for your specific needs
• Securely manage all your authentication tokens in one place

​

Types of Credentials

​

Ardor Credentials

Ardor credentials provide access to your agentic applications APIs deplyed at Ardor, enabling secure interaction with them.

Example how to make request to your agentic application via API:

curl https://apes2thisisexample7ysn3nbf5jye.ardor.cloud/api/v1/prediction/ \
     -X POST \
     -d '{"question": "Hey, how are you?"}' \
     -H "Content-Type: application/json" \
     -H "Authorization: Bearer 1wcFNzExAMPleToKen1cAMrHz3VMT95RLaEo"

​

Third Party Credentials

Use third party services to extend capabilities of your agentic applications.

These provide pre-configured keys formats for external services (e.g., OpenAI), allowing seamless integration with supported third-party functions.

​

Custom Credentials

Define your own credentials for custom integrations specific to your needs.

​

Delete Credential

Click on option menu (⋯) and select Delete and confirm the deletion.

​

Credential Security

​

Sensitive Data

• API keys
• Passwords
• Access tokens
• Secret keys
• etc.

Sensitive data is:

• Never displayed in plain text in the UI
• Shown as dots (••••••••••••) when viewing credentials
• Encrypted at rest in the database
• Transmitted securely when used by agents or applications

​

Non-Sensitive Data

• Credential names
• Hostnames
• Usernames
• Port numbers
• Creation dates
• etc.

Non-sensitive data is visible in the UI and can be freely viewed and edited.

​

Creating New Credentials

To create a new credential:

1. Navigate to the Credentials tab in your Ardor workspace
2. Select the credential type (Ardor, Third Party, or Custom)
3. For Ardor credentials:
   • Enter a name for your credential
   • Click “Create key”
4. For Third Party or Custom credentials:
   • Enter the required information for the specific service
   • Configure any additional settings
   • Save your changes

​

Creating Third Party Credentials

To create a third-party credential:

1. Navigate to the Credentials tab in your Ardor workspace
2. Select the Third Party tab
3. You’ll see a description: “Pre-configured keys for external services (e.g., OpenAI), allowing seamless integration with supported third-party nodes.”
4. Select a service provider from the dropdown or search field:
   • The platform supports 200+ applications
5. After selecting a provider, you’ll be prompted to enter the required credentials for that service
6. Enter the required information and click the “Create key” button to create the credential

Once created, the third-party credential will appear in your credentials list and can be used by your agentic applications to interact with the selected service.

​

Managing Existing Credentials

Your credentials appear in the list on the right side of the Credentials page. For each credential, you can:

• View the creation date
• View or copy the credential’s non-sensitive values
• Access additional options via the menu (⋯)
• Edit or remove credentials as needed

​

Editing Credentials

When editing a credential:

1. Click the menu (⋯) next to the credential you want to modify
2. Select Edit from the dropdown menu
3. An edit form will appear with the credential’s current values:
   • Non-sensitive fields (like key name, host, port, etc) will display their actual values
   • Sensitive fields (like passwords, API keys) will be masked with dots (••••••••••••)
4. Make your changes to any field
5. Click Update to save your changes or Cancel to discard them

​

Using Credentials

​

In Agents

When configuring agents, you can select from your available credentials to grant the agent access to specific services.

​

Security Best Practices

• Never expose your credential keys in client-side code
• Use environment variables to store credential keys
• Regularly rotate credentials for sensitive services
• Grant the minimum necessary permissions for each use case
• Delete unused credentials promptly