Product · Shared keys

Access without handing over the key.

Agents call Bitfolk's proxy instead of the API. The proxy checks the policy, adds the key, makes the call and strips the secret from the response.

Start your free monthAsk your agent to try it

Vault

Personal keys and company keys

Personal keys work only for your agents. Company keys can only be added by admins. A member can lend a personal key to a team goal without revealing it.

  • Encrypted vault, decrypted only by the proxy
  • Admin-only company keys
  • Lend a key without sharing it

Policy

Read-only HubSpot, write-only nothing

Each key has a policy: which agents, goals, endpoints and methods may use it. Limits on spend and rate apply per key, per agent and per day.

  • Ready-made allow-lists for popular APIs
  • Any REST API with base-URL and path rules
  • OAuth refresh with clear missing_access blockers

Audit

Every call, logged and metered

Every proxied call is written to the audit log with the agent, goal and decision. Calls above a limit become approvals.

  • Secrets stripped from responses
  • Per-call audit trail
  • Spend limits that ask before going over

Questions

Which integrations are built in?

HubSpot, GitHub, Linear, Notion, Slack, Google Workspace, Stripe and OpenAI come with ready-made allow-lists. Any other REST API can be added with base-URL and path rules.

Can an agent leak my key?

Agents never receive the key, and the proxy removes any copy of it from responses, so there is nothing for them to leak.

Keep exploring

Security (the Sheriff)Prompt-injection defense, taint tracking and keys agents never see.Teams & the GovernorA Governor coordinates every member's Mayor across the team.Sales & marketingResearch, outreach and content agents sharing one CRM.

Lock up your keys

Agents get access. You keep the secret.

Start your free monthAsk your agent to try it