Introduction

Mint is OMP's local credential-containment primitive.

It keeps transferable vendor API-key bytes out of agent-accessible surfaces.

The category

Mint is a containment boundary.

It authenticates a workload and binds credential use to an intended destination.

It performs the credentialed effect inside the broker.

It returns only a scrubbed result.

Mint does not decide whether an action is appropriate.

That decision belongs to an external authority or execution layer.

The invariant

Raw vendor credentials may exist only in three places:

1. The configured custody backend.
2. Mint or a genuinely isolated executor.
3. The intended protocol peer during the request.

The agent must not receive, inherit, mount, inspect, or read those bytes.

A short-lived token remains a raw credential.

Mint has no generic secret export or checkout path for agents.

The request pattern

The caller sends a normal request to Mint's egress proxy.

The request carries a harmless placeholder instead of a vendor credential.

Mint authenticates the workload and validates containment rules.

Mint resolves the alias inside the broker.

Mint forwards the request and scrubs the response.

Mint records a secret-free audit event.

The caller sees the request result, not the credential bytes.

Continue

Evaluate Mint explains fit, limits, and prerequisites.

Vision and scope explains the boundary and direction.

Quickstart demonstrates one synthetic loopback flow.

Source map

• VISION.md, lines 1–8
• VISION.md, lines 29–52
• VISION.md, lines 86–99
• README.md, lines 1–6