The product
Gatekyper puts an enforceable control plane between machine identities and the provider credentials they need. Each request is identified, scoped, checked, and recorded before it reaches an upstream API.
Control plane
One protected credential can serve many apps, agents, workers, projects, and environments without being copied into each caller.
01 / Store
Add a provider credential through the authenticated admin surface. Gatekyper encrypts it with AES-256-GCM, binds the ciphertext to its organization and credential context, and stores only a redacted hint for later identification.
Test a candidate credential, activate it, retire the previous version, and revoke it when the transition is complete.
02 / Issue
Give each app or agent a high-entropy gk_live_, gk_test_, or gk_tmp_ token.
The plaintext appears once. Gatekyper keeps a public lookup identifier and a peppered HMAC—not a reusable token secret.
Product modules
Gatekyper’s dashboard is the place to describe access. The gateway is the place where those decisions become real.
Restrict providers, capabilities, models, endpoints, environments, required metadata, expiration, rate, and production access. Policies are deny-by-default.
Reserve budget before forwarding, then settle to observed usage. Daily and monthly windows can observe, warn, or hard-stop according to policy.
MCP-connected agents can inspect their own access and request a temporary token. Requests outside a bounded safe template wait for a human approval.
Proxied requests become usage events. Requests blocked before the provider call become separate denial events, so the two ledgers do not blur together.
Switch the active upstream credential while Gate Tokens remain stable. Applications keep the same internal identity through a provider-key rotation.
Revoke a token or stop access by actor, project, provider, environment, agent-created token class, or the entire gateway—with an audit event for the action.
Request path
The dashboard is not in the hot path. The gateway validates the caller, resolves a provider route, applies policy, and only then unlocks the active provider credential.
Provider adapters
Gatekyper supports native provider behavior instead of pretending every API has the same shape.
Chat, responses, embeddings, images, transcription, and speech
Native Messages API
OpenAI-compatible chat and embeddings
Account-scoped chat and image routes
Native prediction creation and status
Allowlisted repository-oriented REST routes
Unknown paths are denied instead of being forwarded as an arbitrary URL proxy. OpenAI and OpenRouter can use the OpenAI-compatible gateway surface; Anthropic and the other adapters retain provider-prefixed native routes.
Agent access
An agent can ask for a capability without gaining the authority to silently grant itself broad access.
List available capabilities, token metadata, personal usage, budget status, and safe denial explanations.
Submit purpose, provider, capability, budget, expiration, estimated calls, and task context for a temporary token.
A human can review, edit, approve, or deny requests that do not match a configured low-risk template.
The requesting actor can collect an approved Gate Token once through MCP. Later status checks return metadata only.
Real keys in. Scoped tokens out.
Start with one provider credential and one tightly scoped test token. Expand the boundary only when the work requires it.
