Project keys

One key per client project. Every tool behind it.

Give each client project a single keyone key that works across the whole catalog. No provider accounts, cards or keys to set up for each client.

No monthly subscription. Add funds when you’re ready to run.

Project keys

One key works for every tool in the catalog. Rotate if a key leaks.

Issue additionalRotate
  • kone_live_a2••••••••ActiveproductionLast used 2:14 PMRevoke
  • kone_live_a7••••••••ActivestagingLast used yesterdayRevoke
  • kone_live_3b••••••••Revokedold n8n flowRevoked Sep 26

Durand Construction · Quote generator · 2 active keys

The problem

Ten clients, four tools each: forty API keys to manage.

A key for every tool, for every client

Each new client means a new OpenAI key, a new Anthropic key, a new Perplexity key. You create and store all of them.

Keys scattered everywhere

They live in .env files, n8n credentials and Make connections. Nobody has the full list.

Offboarding breaks things

Revoke a key that two clients turned out to share, and the wrong automation stops.


Every key you can’t place is a risk.

A key nobody remembers creating still works. If it leaks, it spends against your account until someone notices, and finding out which workflow used it takes longer than replacing it.

40+

keys to create, store, rotate and revoke once you run four tools for ten clients.

1

shared key is enough to make a client impossible to offboard cleanly.

?

is the honest answer to “where is this key used?” for most of them.

The solution

A key that maps to the work.

keyone holds the provider access. Your agency has one account and one wallet, and each client project has one key.

Issue, rotate and revoke per project

Every key belongs to one client project. Replace a leaked key or offboard a client without touching anyone else.

  • Onboard a client in a minute: create the project, copy the key
  • Rotate or revoke a key from its project page
  • Several keys per project when environments need their own

Clients /

Durand Construction

Active

Projects

One key per project, valid for every tool
  • Quote generator

    kone_live_a2••••••••

    Budget

    $80.00/mo

    This month

    $43.05

  • Site reports

    kone_live_7c••••••••

    Budget

    $60.00/mo

    This month

    $36.26

  • Supplier emails

    kone_live_e9••••••••

    Budget

    $40.00/mo

    This month

    $43.19

3 projects · 3 keys · 0 provider accounts

New project

A drop-in for the SDKs you already use

Change the base URL and the key in your OpenAI or Anthropic SDK. The same key then reaches every other tool in the catalog.

  • Works with the OpenAI and Anthropic SDKs
  • Streaming, tools and provider headers pass through
  • Add a tool to a client’s workflow without a new key
from openai import OpenAI
from anthropic import Anthropic

client = OpenAI(
    base_url="https://getkeyone.com/api/proxy/openai/v1",
    api_key="kone_live_a2…",  # Durand · Quote generator
)

# Same key, another tool: no new account, no new secret
claude = Anthropic(
    base_url="https://getkeyone.com/api/proxy/anthropic",
    api_key="kone_live_a2…",
)

Stored as hashes

A key is shown once when it is issued. keyone keeps only its hash, never the readable value.

Scoped to what the project needs

Restrict each project to the tools and models it should use, so a key can’t wander.

Agents can set themselves up

Point Claude Code or Cursor at keyone’s skill file and it installs the key and wires the project.

How it works

Live in minutes.

01

Create the project

Add the client, then a project for each workflow you run for them.

02

Copy its key

The project key is issued on the spot and works for every tool.

03

Swap it in

Replace the provider keys in that automation with the project key and base URL.

Project keys: questions.

Pick one client.
Know what their AI costs.

Connect a project, set its budget, and see its usage in one place.

Start with one client project

No monthly subscription. Add funds when you’re ready to run. Or book a demo