Lets agents set up infrastructure themselves Closed Beta

A video recording of the actual Carvit Pass extension screen. Account names and key names are mock data.

Shown with the Korean interface.

Request by name, and the vault injects the value

Carvit Pass is a key vault that stores API keys and injects them where needed.

Swipe sideways →

How it works

It is designed so agents do not see key values at any step.

1. 1

   Store keys in the vault

   It is designed so key values remain only inside the vault and are not left in agent chats or files.

2. 2

   Request by name

   "Put the payment service key in .env" - requests are made by name, not value.

3. 3

   Inject based on key type

   Standard keys are injected by the vault right away, while sensitive keys are injected after human confirmation. The criteria are explained below.

4. 4

   Return results only

   Returns only success, failure, or fingerprint values for verification, without leaving secret values in chats or logs.

When human confirmation is required

Approval is not required for all keys. Confirmation is placed only where strictly necessary.

• Standard keysThe vault injects them immediately without human approval.
• Sensitive keysKeys linked to billing or security are injected after extra confirmation via channels like Telegram. Viewing or copying sensitive keys on screen also requires confirmation.

Records from our own team

Below are development records from our team building Pass, not customer usage metrics.

• 35Carvit Pass development PRs (since 10/3)

These are internal team records as of 2026-10-14, not customer usage metrics or revenue.

Interested in Pass?

This is a Closed Beta. Let us know if your team would like to try it.