Give your agents
a card
for real work.

You issue a KIFF Card to a named agent. It says which actions the agent may take, under what conditions, and how much. KIFF checks each proposal before your system runs the action, keeps the balance, and lets you revoke the card at any time.

See the card → Issue a card

A card narrows actions your domain and permissions already allow. It cannot grant an action on its own. KIFF authorizes; your system executes.

three cards · one named holder
KIFF Card · issued
active
support-agent card-refund · example
may do REFUND_ORDER
only when the order is PAID
up to €5,000 per calendar day
€4,000 used€1,000 remaining
REFUND_ORDER on ord_8812 −€4,000 authorized
Only the owner can change the ceiling or revoke this card.

The €4,000 movement records an authorization. The refund itself runs in your system.

KIFF Card · issued
active
support-agent subscription-plan-change · example
may do CHANGE_PLAN
only when the subscription is ACTIVE
up to 40 changes per day
9 used31 remaining
CHANGE_PLAN on sub_4471 1 change authorized
Only the owner can change the ceiling or revoke this card.

KIFF authorizes the change. Your billing system applies it.

KIFF Card · issued
active
support-agent retention-credit · example
may do ISSUE_STORE_CREDIT
only when the customer is ELIGIBLE
up to €2,000 per calendar day
€750 used€1,250 remaining
ISSUE_STORE_CREDIT for cus_2048 −€250 authorized
Only the owner can change the ceiling or revoke this card.

KIFF authorizes the credit. Your commerce system issues it.

One holder. Separate cards. Give each job its own card. Change or revoke it without touching the others.

a KIFF Card, from issue to revoke

You decide what it may do. The card carries that decision.

When an action requires a card, the agent must present one. The card narrows existing permissions. It never grants new ones.

01 · Issue

Name the holder. Set actions, conditions, ceiling, window and expiry.

02 · Use

Each authorization draws before your system runs the action.

03 · See

See the ceiling, drawn amount and remaining authority.

04 · Change the ceiling

Draws already made still count; raising the ceiling adds only the difference, and the revision records who made the change.

05 · Revoke

Take it back. The next action that requires it is refused.

what this card can do that a payment card cannot
It bounds actions and conditions It knows REFUND_ORDER and PAID. A payment card only knows merchant and amount.
Money is one unit Cap three customer deletions an hour or two deploys a day.
The holder cannot raise it Only an owner can add room. Every change is recorded.
What a KIFF Card can and cannot say →
the queue nobody planned for

Your agent proposes it. A human still clicks it.

Every proposal enters the same queue: open, skim, agree, click. The agent runs faster; deployment still runs on human throughput.

A credential cannot settle whether an action is authorized now. That takes shared state, permissions, approvals, and cumulative limits.

These are two different mechanisms. A domain approval is one case a person grants or denies, and work resumes on the next proposal. A card's ceiling is cumulative: once it is drawn down, nothing about the next proposal is wrong, so there is no case to approve, an owner has to raise the ceiling before that agent can act again.

Review the exceptions. Let the card clear the routine. allowed work runs · approval cases wait for a grant · a spent ceiling refuses until an owner raises it
the same month, twice
today
agent proposesa person clicks
agent proposesa person clicks
agent proposesa person clicks
agent proposesa person clicks
every one, every month
with KIFF
agent proposesruns
agent proposesruns
agent proposesruns
agent proposesa person
the exception waits for a grant, in the Control Room or your own flow
01 The review is not free Someone reads work the rules could settle.
02 The review stops being one Repetition turns approval into muscle memory.
03 So the agent stays caged A per-call check cannot say what every path has already drawn today.
why the checks you have are not enough

Ten correct decisions can still be a wrong day.

Each check helps. Only the last controls the whole day.

1
Scope the token Refund calls only. Static. It cannot see an earlier refund.
2
Check state in the agent Read the order first. The agent can be talked out of its own check.
3
Decide outside the agent KIFF does this A service answers before execution. It still sees one call, not the day.
4
Count what it has drawn KIFF does this One balance across every run, process, machine and channel the same holder acts through.

Only the fourth sees the day. There is no approve button: more room is a raised limit, and the change is recorded.

what the fourth one has to survive
Two at once The ledger locks the balance before either proceeds.
A retry is not a second refund The same proposal draws once, however often it arrives.
Unreadable is not zero An unreadable balance refuses the action.
Approval draws too A person-approved refund still draws on the day.
What a card can and cannot say →
why a card has one balance

A card is only a card when it counts in one place.

A balance that lived with the agent would reset every time the agent did. Restart it, scale it out, run it from somewhere else, and a ceiling of five a day becomes five per copy. Cloud holds the one balance every run and every machine draws from, together with the state the decision needs. Restarting or scaling the holder does not reset its card; a different holder receives its own card against the same domain.

Explore the real KIFF appFully navigable · sample data
One balance per card Counted across every run, process and machine
Current state What is true now, rebuilt from events
Shared domains One lifecycle every actor understands
Human authority Risky work waits for the right person
One history Every proposal, decision, and result
Build the foundation free. Operate it on Cloud. Cloud meters the operations it runs-never the number of domains, agents, frameworks, or teams that reuse them.
See pricing →
start with one agent

Issue your first card for one real action.

Choose the holder, an action it already has permission to take, the conditions and a ceiling. Connect Guard where that action runs. KIFF checks the next proposal against the card and records what it drew.

Issue a card → Build the first one with us

Start with authority for one action. The domain and permissions still decide whether the action itself is legal.

first card one agent
01
Name the holder

The agent's actor id appears on every proposal and on its card.

02
Set the terms

Choose the action, allowed states, ceiling, window and expiry.

03
Connect the action

Guard asks KIFF before your system performs it.

04
Read the statement

See authorizations, the balance remaining and any refusal in activity.

built for your stack

One seam, in front of the action, in whatever you already run.

Guard connects Agno, LangGraph, OpenAI, Google ADK, Strands, n8n, or your own stack to the same operational domain, the state, actions, authority and evidence a card narrows against. Your coding agent can author that domain directly.

See the full integration guide → The five-line integration → Read the domain grammar →
where teams put the first one

Two places an agent is already acting.

Not a list of markets. These are the two where the action is already being taken without a person, and the total is countable, euros in the first, how many times in the second. Start with one action in one of them.

Customer operations
Issue refundsApply creditsCancel ordersChange plans
Cloud & infrastructure
Restart servicesScale resourcesRoll back a deployRotate credentials
Start with your first one →
ask AI about KIFF

Open your assistant with a prompt to read llms-full.txt and answer from it.

ChatGPT Claude Perplexity Google AI Grok
one named holder per card

Give it room to work. Keep the right to take that room back.

Issue a card for an action your agent already has permission to take. See each authorization draw on the balance. Change its ceiling or revoke it when the work changes.

Issue a card → Build the first one with us
Running on your own infrastructure? The framework is open source →