API_KEY
exceptionless_api_key
Developer setup
No fields declared in this snapshot.
User connection
- Project Client API Keygeneric_api_key · stringRequired
EXCEPTIONLESS
Exceptionless provides one-project event ingestion and client configuration using a project-bound client API key.
Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.
Pakkawork boundary
Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.
4
Action summaries
Display-only definitions
0
Trigger types
Not installed instances
1
Auth modes
Field names, never values
No
Execution
No runtime adapter
Authentication map
API_KEY
No fields declared in this snapshot.
Capability index
Showing 1–4 of 4 actions
EXCEPTIONLESS_CLOSE_SESSION
Close an active session in the Exceptionless project bound to the connected client API key. This records irreversible session-closure telemetry and returns only an acceptance confirmation.
Untrusted display-only summary
EXCEPTIONLESS_GET_CLIENT_CONFIGURATION
Return the configuration for the single Exceptionless project bound to the connected client API key. Configuration values can contain sensitive project settings; request and expose them only when needed.
Untrusted display-only summary
EXCEPTIONLESS_SUBMIT_EVENT
Submit one structured telemetry event to the Exceptionless project bound to the connected client API key. Acceptance is asynchronous and does not confirm that the event was processed or persisted.
Untrusted display-only summary
EXCEPTIONLESS_SUBMIT_SESSION_HEARTBEAT
Record an active session heartbeat in the Exceptionless project bound to the connected client API key. Use Close Session separately when the session ends. Despite using GET upstream, this tool writes telemetry.
Untrusted display-only summary
Provenance
The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.
Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.