Signpath
for LuumenAI

Read your SignPath certificates, projects, and signing policies in context

When a release stalls on code signing, you need facts fast. Connect SignPath with an API key and Luumen answers from your organization directly: which certificates exist, what projects are configured, what a signing policy actually requires, and whether the API is healthy. Read-only, so nothing changes in SignPath.

The Signpath toolbox

5 tools, all read-only. They answer instantly, and every call is logged.

  • ReadGet Health CheckCheck if the SignPath API is healthy and operational.
  • ReadList CertificatesRetrieve all certificates available in a SignPath organization.
  • ReadList ProjectsList all projects for an organization.
  • ReadRetrieve Signing Policy DetailsRetrieve signing policy details for code signing operations.
  • ReadRetrieve System InfoRetrieves SignPath system information including the application version and the web UI base URL.

Questions

How does LuumenAI connect to Signpath?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Signpath on its own?

No. Every one of the 5 tools LuumenAI has for Signpath is read-only, so it can answer questions from Signpath but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.

Who gets access to the integration?

You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.

Is there an audit trail?

Every call to Signpath is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Signpath to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.