Luxailux.ca

Articles · Money & Agents

The key that never dies

Machine-to-machine access still runs on shared secret keys that work forever once they leak. Caller Identity for APIs gives every calling system an identity of its own instead.

By Lucian · Lux Automations

The problem

Most systems still let other systems in the same way they did years ago: with a static API key. The key is a shared secret. Whoever holds it is believed, wherever they are calling from, for as long as the key stays valid. That is a comfortable arrangement right up until the key is copied somewhere it should never have been.

Keys get copied into code repositories, into images, and into chat logs, often by someone who was in a hurry rather than someone doing harm. GitGuardian found that 70% of secrets leaked in 2022 were still valid years later, and that 100,000 valid secrets were sitting in 15 million public Docker images. A leaked key does not expire on its own. And because the key is shared, revoking it is painful in a different way: turn it off, and every honest caller who shares it stops working too. So teams hesitate, the old key stays alive, and the door stays open to anyone who found it.

The technology

Caller Identity for APIs replaces the shared secret with an issued identity for each caller. Every system that calls you holds its own keypair. The public half is registered, so the door knows which caller it belongs to. The private half never travels, never gets pasted into a file, and never gets committed to a repository. There is nothing shared to leak, and nothing to rotate by hand.

That is the house engine pointed at APIs. Amos checks who is knocking: this caller, with this key, not a bearer holding a copied secret. SeamGuard checks the joins between systems. And each call class leaves a signed receipt saying who called, and what for. If one caller misbehaves, or its key is somehow compromised, you revoke that one caller, precisely. The rest of the callers never notice, because they were never sharing its identity in the first place.

What it changes

For the team running the API, the hard choice disappears. Today, dealing with a suspect key means choosing between leaving a risk in place and breaking everyone who shares the key. With an identity per caller, the answer is small and specific: revoke the one that is in question, and let the others carry on. A security worry stops being an outage waiting to be scheduled.

For everyone who has to answer questions afterwards, the receipts change the conversation. Instead of reconstructing what might have called, and when, the record says who called and what the call was for, in a form that was signed at the time. We sell the check, never custody: your systems, your data, and your callers stay yours. What Caller Identity adds is a door that knows each caller by name, and a record that can prove it.

See it

Retire the shared secret key, and give every caller an identity of its own. Caller Identity for APIs — the product page · All the house articles · Lux Automations — ailux.ca