Summary
There is a setting in openclaw.json to set the Exa api key as documented in: https://docs.openclaw.ai/tools/exa-search#exa-search, however, unlike other websearch credentials, Exa is missing from secretRef as shown in: https://docs.openclaw.ai/reference/secretref-credential-surface#secretref-credential-surface
Problem to solve
Users are unable to set Exa apiKey via secretRef if they want to use Exa as webSearch tool
Proposed solution
Add Exa apiKey to secretRef support. Document this added supported to secretRef's documentation.
Alternatives considered
No response
Impact
Affected: Users who want to set Exa apiKey via secretRef
Severity: blocks workflow
Frequency: always
Consequences: blocked
Evidence/examples
No response
Additional information
No response
Summary
There is a setting in openclaw.json to set the Exa api key as documented in: https://docs.openclaw.ai/tools/exa-search#exa-search, however, unlike other websearch credentials, Exa is missing from secretRef as shown in: https://docs.openclaw.ai/reference/secretref-credential-surface#secretref-credential-surface
Problem to solve
Users are unable to set Exa apiKey via secretRef if they want to use Exa as webSearch tool
Proposed solution
Add Exa apiKey to secretRef support. Document this added supported to secretRef's documentation.
Alternatives considered
No response
Impact
Affected: Users who want to set Exa apiKey via secretRef
Severity: blocks workflow
Frequency: always
Consequences: blocked
Evidence/examples
No response
Additional information
No response