# 12.3 Static API Keys & Service Secrets

When authority is cryptographic and scoped, static API keys become obsolete.

***

### Legacy API Key Model vs PTERI

| Category              | Traditional Model               | Problems                                  | PTERI Replacement                                                                      |
| --------------------- | ------------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------- |
| Authentication Method | Long-lived API keys             | Key leakage                               | <mark style="color:$primary;">**Signed requests**</mark>                               |
| Storage Model         | Stored in environment variables | Secrets exposed in logs, CI/CD, or memory | <mark style="color:$primary;">**No stored secrets**</mark>                             |
| Service Architecture  | Shared across services          | No attribution                            | <mark style="color:$primary;">**Machines have unique cryptographic identities**</mark> |
| Authorization Model   | Key grants ambient authority    | No intent verification                    | <mark style="color:$primary;">**Scoped authority per request**</mark>                  |
| Key Lifecycle         | Manual rotation required        | Difficult rotation                        | <mark style="color:$primary;">**No rotation needed (no reusable secret)**</mark>       |
| Auditability          | Key use not tied to intent      | Cannot prove who approved what            | <mark style="color:$primary;">**Deterministic verification**</mark>                    |

***

### Core Principle

> *"Machines become cryptographic identities, not secret holders."*

When every request is signed, authority is explicit, scoped, and verifiable — not embedded in static secrets.

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kakrlabs.com/12.-comparisons-and-obsolescence/12.3-static-api-keys-and-service-secrets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.