Mac · Home
Requests and decisions, in plain words.
A local record of who asked, what you decided, and when.
2FA + Credential Escrow for Agents
Context-aware agent authentication
Innkeeper lets your agents make authenticated and authorized requests without ever receiving a credential.
Send Maria the corrected August invoice.
I’ll ask Innkeeper to authorize the email first.
mail.send · waiting for your phone
How it works
Your agents make blank Authorization header requests that you sign.
- 01
Your Mac + your iPhone
Pair once.
Scan the QR code the app shows you. Your phone makes a key in the Secure Enclave, and that key is the whole account. No password.
- 02
› payments.send
Waiting for your phone
The agent asks.
A flagged call stops, and your phone gets the request: the tool, the arguments as they were written, who is asking, and how long it has left.
- 03
The exact request. Your signature.
You read it. Face ID.
Approve signs the exact bytes you read, with a key that never leaves the enclave. Change one character and the signature no longer matches. Deny needs no face.
- 04
Decision recorded
- Verdict
- Approved
- Credential
- Not shared
It goes back signed.
The verdict returns to the agent as an ordinary tool result. Innkeeper attaches the credential, so the agent never holds it. Every call is written down.
The apps
On your Mac.
On your iPhone.
Connect your agents and keep the log on your Mac. Store your credentials and review requests on your iPhone.
Mac · MCP settings
Connect your agents.
Mac · Menu-bar detail
Close the window. Keep it running.
iPhone · Approvals
The context before your yes.
Read the action, who it’s for, and what it will send. Your credentials are stored on the phone.
Why
Context-aware agent authentication
(because MFA isn't enough)
MFA proves a person is at the keyboard, once, at login. An agent working for you is never at the keyboard. It acts as you all day, through credentials it was handed, and a factor checked at the door has nothing to say about any of it. What that needs is authentication that knows the context of every call: what the action is, who is asking, on whose behalf, and whether it looks like something you would do.
Innkeeper is the first piece of that. A call that spends a credential, sends as you, or cannot be taken back stops on your phone. The request names who is asking and why, your answer is a signature over the exact bytes, and the agent never holds the credential. Every answer is written down, who, what, when, and how long you took, and that record is the shape of how you work.
That is what we are building. This is the part that stops the call and asks you.
Good to know
Less guesswork.
More control.
Does my agent get my credentials?
No. It can make approved requests without receiving them.
Can I say no?
Yes. You can deny a request from your iPhone.
Can I see what happened?
Yes. Review activity on your Mac.
Pricing
Start with what you need.
Individual
One person. One Mac. One iPhone.
$0
Forever. No card.
Enterprise
Custom approval rules, integrations, and support.
Custom
Let’s scope it together.
Human-approved 2FA for agents.
Pair a phone, point Innkeeper at your server, and let your agents make authorized requests, securely.