Skip to the card

Card 427 of 9972026-09-10 issue

Observed arrival · 2026-09-10

Slifer Key Locker Keeps the Real API Key Away from the Agent

keylocker.dev Observed source
Editorial interest 78/100 Selection signal · not a rating of the site

A local-first broker gives apps and coding agents scoped stand-in tokens while holding provider credentials inside an encrypted vault.

Landing page captured for the 2026-09-10 issue.

Field notes

Slifer separates the less-trusted client from the upstream credential by issuing scoped skl_tok_v1 tokens and keeping the provider key in encrypted local vault data. Its policy model names the provider, secret alias, HTTP methods, paths, headers, egress host, rate ceiling, concurrency cap, and expiry, with deny-by-default behavior. The page says unlocking requires both a passphrase and a generated Vault Secret Key, while acknowledging that the project remains private, pre-release, and currently limited to an OpenAI brokered path.

Observed signals

Read the marks

Editorial observations of this landing page, not a rating.

OpenPublic substance visible
PrettyNotable craft visible
ProPolished or operationally mature
NicheUnusually specific use

One card from the complete issue

All Approaches to Piccadilly

405,063 arrived 1,000 judged 997 catalogued Enter the complete issue
keylocker.dev

Landing page observed 2026-09-10. The live site may have changed.