Probe templates
Build a credential check once, then apply it to every path that holds that kind of credential — rotating the secret never touches the template.
A template is a saved probe configuration you can apply to any path. Work out once how to verify a Gemini key — which endpoint, which header, what counts as success — and every project storing a Gemini key gets that check without anyone reconstructing it.
Why templates exist#
The flexible probes (Generic HTTP Bearer, Custom HTTP) let you validate any token-based API, because you supply the endpoint. That flexibility has a cost: whoever configures the next path has to know the right endpoint, the right header and the right success condition all over again — and will get it subtly wrong.
A template removes that. The person who worked it out saves it; everyone else picks it from a list.
Referencing the path's keys#
A template must not contain a secret — it is applied to many paths, each with its own credential. So instead of a value, you reference the key by name:
Header Authorization: Bearer {{items.api_key}}When the template is applied to a path, {{items.api_key}} resolves to the key called api_key
stored under that path. The same template works everywhere that key name exists, and it holds no
credential of its own.
Because the template points at a key rather than a value, rotating the credential is an ordinary secret write. The template is unchanged, every path using it keeps validating, and nothing needs re-approving.
Use {{items.<key>}} anywhere the probe takes text — URL, headers, or request body.
Creating one#
Configure a path's validation until it works — Validate now proves it before you commit — then
save that configuration as a template and name it for what it verifies (Gemini API key,
Internal billing API). Names are what people choose from later.
You can also start from a built-in template: PulsVault ships a few for common providers, ready to apply directly or to copy and adjust.
Scope: one project, or the whole space#
A template can be pinned to a project or left available across your whole space.
- Pin it when the check is specific to that project's infrastructure — an internal service only that team calls.
- Leave it space-wide when it verifies a third-party credential any project might hold. A provider's token endpoint does not change per project.
Applying one#
Open the path, choose Apply template, and pick from the list. The template's probe and settings are copied onto the path, and PulsVault records which template it came from.
From that moment the configuration belongs to the path: editing it there does not alter the template or any other path using it. That is deliberate — one path needing a longer timeout should never change a check other teams depend on.
Changing a template later#
Editing a template affects paths configured from now on. Paths already using it keep the settings they were given.
If you fix a mistake in a template that is already in use, re-apply it to the affected paths so they pick up the correction.