UseAgentINTEGRATION · VIA MCP
Integrate
anything.
If UseAgent doesn't have a native integration, add the API key as a secret. Your agent can embed it in code, curl external services, or pass it to scripts.
Org secrets storage
Write-only secrets scoped to your org. Never shown in logs or artifacts.
Runtime injection
Secrets are injected into the agent's environment. Agent can use them in scripts or API calls.
Redaction
Secrets are redacted from response logs before persistence. Audit trail is clean.
Straight talk: This is a power-user escape hatch. If you find yourself using secrets for common integrations, we'd like to know: it signals what to build next.
Questions, answered.
Are secrets encrypted?
Yes. Encrypted at rest and in transit. Decrypted only when injected into a run.
Can I rotate secrets without re-entering them?
Yes. Update the secret value in Settings. New runs use the new value immediately.
Do secrets count toward security compliance?
Secrets are org-scoped and write-only from the API. No cross-org leakage. But treat them like passwords: use strong, unique values.
Start with one task.
See what you can hand off.
Explore a completed run, or join the early-access list to hear about getting your team started.