DOCUMENTATION / Reference
Connection referenceWhich key do I need?
One reference for account, agent, provider and deployment credentials.
- Runs on
- The service or installation you explicitly select
- Before you start
- A credential issued for that exact destination
These credentials are not interchangeable. External customers should never receive company Trigger, provider, deployment or VPS credentials.
On this page
| Connection | Use | Does not do |
|---|---|---|
| Hosted API | Account → API keys on 10signals.xyz; Bearer header | Install code or access a Trigger project |
| Hosted MCP | Client OAuth consent to your hosted account | Accept an account API key as an OAuth token |
| Team Trigger CLI | Team-approved environment key; configure or TRIGGER_SECRET_KEY | Deploy tools or install the app |
| Trigger deployment | Operator login, or PAT in protected CI | Replace the runtime key for our report client |
| Research provider | Local AI provider screen OR Trigger OPENAI_API_KEY | Authenticate an agent to 10Signals |
Identify the destination first
Choose your local installation, the managed 10Signals service, or a trusted Trigger environment. A successful sign-in to one does not configure the others.
Start with the minimum access
Use read-only account or MCP scopes for a first connection test. Trigger environment keys have a wider trust boundary: give them only to authorized teammates and agents.
Keep lifecycle actions separate
Client logout, connection revocation and provider-key rotation have different effects. Revoke at the issuing service, remove stale environment variables and verify that new requests fail. Do not assume previously returned data is erased.