More freedom to act. Clear limits by design.More freedom to act.Clear limits by design.Give agents a mandate.Keep every decision accountable.Money can move.Control stays with you.Hand over the spending.Never the authority.More freedom to act.Clear limits by design.
Give AI agents and people room to spend within a mandate you understand and control. Every request stays accountable from permission to outcome.
The current pilot begins with SaaS seats, API credits, Cloud services, Approved vendors, Software renewals, Operational tools.
SaaS seats
API credits
Cloud services
Approved vendors
Software renewals
Operational tools
SaaS seats
API credits
Cloud services
Approved vendors
Software renewals
Operational tools
Everything a delegate needs to move. Everything you need to stay in control.
Access is not authority. Klard gives every person or agent a clear boundary, resolves the request against it, and keeps the outcome accountable.
Intent
Start with the purpose, not an unrestricted payment method.
New requestReady
Purpose
Research tools
Requested by
Ops agent
Maximum
$600
Guardrails
Set vendor, amount, timing, and approval conditions before spend happens.
MandateActive
✓VendorApproved
✓Monthly amount$600
✓Owner presenceWhen required
Approval
Bring the accountable person in only when the current limit requires it.
Needs reviewPending
Above limit+$84.16
Reason
Current boundary
Owner
Finance ops
Evidence
Keep the actor, mandate, request, decision, and outcome together.
Decision recordLinked
IdentityConfirmed
MandateMatched
OutcomeRecorded
AT REQUEST TIME
Every request meets its mandate.
A request is resolved to a delegate, a mandate, and an accountable owner before it can cause spend. Policy answers with allow, decline, or a human approval — and when Klard can't resolve the chain, it fails closed.
fail-closed by default
re-checked at authorization
revocable any time
spend.intent · research-agent-02
vendor
openai.com
amount
$240.00 USD
purpose
API credits · Q3 eval run
mandate
v3 · ceiling $500/mo · expires Aug 31
→policy v41REQUIRE_APPROVAL
→approved · S. Chen · passkey · 09:16
→grant issued · card ····4291 · cap $240 · single use
One authority model. Any rail.
The mandate, decision, approval, and evidence chain stay consistent. The connected path may change; Klard discloses the control coverage that applies before it is used.
Purpose-bound virtual card
Each approved request materializes a single-use virtual card carrying the strongest controls the issuer supports — amount cap, expiry, merchant restriction — and Klard answers the live issuer authorization itself, fail-closed.
Amount ceiling and tolerance
Direct Klard prevention
Single use and expiry
Direct Klard prevention
Merchant and category lock
Provider-enforced where supported
Re-check at authorization
Direct Klard prevention
Human checkout & step-up
People execute with assigned cards and secure checkout; 3-D Secure and step-up bring the human back into the loop when policy asks for presence.
Budgets and approval thresholds
Direct Klard prevention
Cardholder verification
Provider-enforced
Receipts and settlement
Observe-and-reconcile
Cost-causing action gateway
Cloud, SaaS, and advertising actions create spend without a checkout. The gateway evaluates them as spend intents and executes through parameter-bound credentials.
Action allow or deny
Direct at the gateway
Committed-spend estimate
Observe-and-reconcile
Platform-side limits
Provider-enforced where exposed
Invoice & bank transfer
Approval-gated invoices and AP transfers under the same mandate, decision, and evidence chain.
Pre-execution approval
Direct at the adapter
Transfer execution
Provider-enforced
Settlement facts
Observe-and-reconcile
Agentic checkout tokens
Shared payment tokens for agentic commerce, bound to a Klard grant when the program is available in a served market.
Token scope
Provider-enforced
Intent-to-token binding
Direct Klard prevention
Merchant outcome
Observe-and-reconcile
AP2 mandates
Signed Agent Payments Protocol mandates map to Klard authority as portable protocol evidence — never as a replacement for policy.
Mandate proof
Protocol evidence, verified
Policy and financial state
Direct Klard prevention
Processor settlement
Provider-enforced
Network agent tokens
Network-issued agent tokens bind to Klard authority when supported issuer and processor programs make the path available.
Token issuance
Provider-enforced
Authority binding
Direct Klard prevention
Network lifecycle events
Observe-and-reconcile
x402 machine payments
Per-request machine payments over HTTP payment challenges, with the Klard authority model governing the request before the connected path executes it.
Challenge routing
Direct at the adapter
Wallet custody
Provider-enforced
On-chain settlement
Observe-and-reconcile
Purpose-bound virtual card+
Purpose-bound virtual card
Each approved request materializes a single-use virtual card carrying the strongest controls the issuer supports — amount cap, expiry, merchant restriction — and Klard answers the live issuer authorization itself, fail-closed.
Amount ceiling and tolerance
Direct Klard prevention
Single use and expiry
Direct Klard prevention
Merchant and category lock
Provider-enforced where supported
Re-check at authorization
Direct Klard prevention
Human checkout & step-up+
Human checkout & step-up
People execute with assigned cards and secure checkout; 3-D Secure and step-up bring the human back into the loop when policy asks for presence.
Budgets and approval thresholds
Direct Klard prevention
Cardholder verification
Provider-enforced
Receipts and settlement
Observe-and-reconcile
Cost-causing action gateway+
Cost-causing action gateway
Cloud, SaaS, and advertising actions create spend without a checkout. The gateway evaluates them as spend intents and executes through parameter-bound credentials.
Action allow or deny
Direct at the gateway
Committed-spend estimate
Observe-and-reconcile
Platform-side limits
Provider-enforced where exposed
Invoice & bank transfer+
Invoice & bank transfer
Approval-gated invoices and AP transfers under the same mandate, decision, and evidence chain.
Pre-execution approval
Direct at the adapter
Transfer execution
Provider-enforced
Settlement facts
Observe-and-reconcile
Agentic checkout tokens+
Agentic checkout tokens
Shared payment tokens for agentic commerce, bound to a Klard grant when the program is available in a served market.
Token scope
Provider-enforced
Intent-to-token binding
Direct Klard prevention
Merchant outcome
Observe-and-reconcile
AP2 mandates+
AP2 mandates
Signed Agent Payments Protocol mandates map to Klard authority as portable protocol evidence — never as a replacement for policy.
Mandate proof
Protocol evidence, verified
Policy and financial state
Direct Klard prevention
Processor settlement
Provider-enforced
Network agent tokens+
Network agent tokens
Network-issued agent tokens bind to Klard authority when supported issuer and processor programs make the path available.
Token issuance
Provider-enforced
Authority binding
Direct Klard prevention
Network lifecycle events
Observe-and-reconcile
x402 machine payments+
x402 machine payments
Per-request machine payments over HTTP payment challenges, with the Klard authority model governing the request before the connected path executes it.
Challenge routing
Direct at the adapter
Wallet custody
Provider-enforced
On-chain settlement
Observe-and-reconcile
Bounded and accountable, whoever spends.
AI agents and people at work
Give agents, employees, and contractors room to buy the tools that keep work moving, under the same budgets and approvals.
Team mandateActive
Approved categories
SaaS · API · Cloud
Approval above
$600
Accountable owner
Finance ops
Shared responsibility in everyday life
Use the same principle anywhere one person spends for another: clear purpose, clear limits, and no unlimited access.
Shared taskClear
Purpose
Weekly essentials
Maximum
$180
Expires
Saturday
EVIDENCE
One linked record.
Delegate, authority, request, decision, execution — and what remains unresolved — stay connected. When something goes wrong, you retell the story instead of reconstructing it.
unresolved facts stay visible — nothing is invented away
What needs to be clear before authority moves.
What is Klard?
Klard helps people and organizations govern spending carried out by AI agents or trusted people. It lets an accountable owner give a delegate a bounded mandate without handing over unrestricted access.
Who is Klard for?
The current pilot is for AI-native and automation-heavy teams governing SaaS seats, API credits, and controlled vendor or tool purchases made by employees and AI agents.
Is Klard only for AI agents?
No. AI agents create the new urgency, but the same authority model applies to trusted people. An accountable person or organization remains responsible for the money and the purpose.
What does access is not authority mean?
An AI agent may be able to call tools, reach a checkout, or request a purchase. That does not give it financial authority. The accountable owner defines the purpose, budget, vendors, amount, timing, and approval rules.
How does Klard make a request-time decision?
At a connected or supported control point, Klard evaluates a request against the authority in place. It can allow the request, require human approval, or decline it. Klard does not claim to control every payment or purchase path.
What evidence does Klard keep?
Klard keeps the delegate, authority, request, decision, execution result, and outcome linked. Where facts remain missing, conflicting, or unresolved, that context stays visible rather than being filled in with a guess.
How do broader people and household use cases fit?
The same authority problem exists when an employee, contractor, assistant, caregiver, or family member spends for someone else. Broader personal and household workflows are part of Klard's direction, not a released household product today.
Is Klard a bank or a general-purpose card product?
No. Klard is not a bank or a general-purpose card product. A card may be one controlled route, but it is not the product category or a promise that a particular financial product is available.
What does applying for the pilot mean?
Applications are reviewed for limited pilot access. Applying does not guarantee acceptance or access, and we use the workflow context to decide whether the pilot is a fit.
Current limited pilot
Apply for the limited pilot.
We're onboarding a small set of teams whose people and agents buy tools. Tell us who spends on your behalf, and we'll review the fit.
More freedom to act. Clear limits by design.More freedom to act.Clear limits by design.Give agents a mandate.Keep every decision accountable.Money can move.Control stays with you.Hand over the spending.Never the authority.More freedom to act.Clear limits by design.
Give AI agents and people room to spend within a mandate you understand and control. Every request stays accountable from permission to outcome.
The current pilot begins with SaaS seats, API credits, Cloud services, Approved vendors, Software renewals, Operational tools.
SaaS seats
API credits
Cloud services
Approved vendors
Software renewals
Operational tools
SaaS seats
API credits
Cloud services
Approved vendors
Software renewals
Operational tools
Everything a delegate needs to move. Everything you need to stay in control.
Access is not authority. Klard gives every person or agent a clear boundary, resolves the request against it, and keeps the outcome accountable.
Intent
Start with the purpose, not an unrestricted payment method.
New requestReady
Purpose
Research tools
Requested by
Ops agent
Maximum
$600
Guardrails
Set vendor, amount, timing, and approval conditions before spend happens.
MandateActive
✓VendorApproved
✓Monthly amount$600
✓Owner presenceWhen required
Approval
Bring the accountable person in only when the current limit requires it.
Needs reviewPending
Above limit+$84.16
Reason
Current boundary
Owner
Finance ops
Evidence
Keep the actor, mandate, request, decision, and outcome together.
Decision recordLinked
IdentityConfirmed
MandateMatched
OutcomeRecorded
AT REQUEST TIME
Every request meets its mandate.
A request is resolved to a delegate, a mandate, and an accountable owner before it can cause spend. Policy answers with allow, decline, or a human approval — and when Klard can't resolve the chain, it fails closed.
fail-closed by default
re-checked at authorization
revocable any time
spend.intent · research-agent-02
vendor
openai.com
amount
$240.00 USD
purpose
API credits · Q3 eval run
mandate
v3 · ceiling $500/mo · expires Aug 31
→policy v41REQUIRE_APPROVAL
→approved · S. Chen · passkey · 09:16
→grant issued · card ····4291 · cap $240 · single use
One authority model. Any rail.
The mandate, decision, approval, and evidence chain stay consistent. The connected path may change; Klard discloses the control coverage that applies before it is used.
Purpose-bound virtual card
Each approved request materializes a single-use virtual card carrying the strongest controls the issuer supports — amount cap, expiry, merchant restriction — and Klard answers the live issuer authorization itself, fail-closed.
Amount ceiling and tolerance
Direct Klard prevention
Single use and expiry
Direct Klard prevention
Merchant and category lock
Provider-enforced where supported
Re-check at authorization
Direct Klard prevention
Human checkout & step-up
People execute with assigned cards and secure checkout; 3-D Secure and step-up bring the human back into the loop when policy asks for presence.
Budgets and approval thresholds
Direct Klard prevention
Cardholder verification
Provider-enforced
Receipts and settlement
Observe-and-reconcile
Cost-causing action gateway
Cloud, SaaS, and advertising actions create spend without a checkout. The gateway evaluates them as spend intents and executes through parameter-bound credentials.
Action allow or deny
Direct at the gateway
Committed-spend estimate
Observe-and-reconcile
Platform-side limits
Provider-enforced where exposed
Invoice & bank transfer
Approval-gated invoices and AP transfers under the same mandate, decision, and evidence chain.
Pre-execution approval
Direct at the adapter
Transfer execution
Provider-enforced
Settlement facts
Observe-and-reconcile
Agentic checkout tokens
Shared payment tokens for agentic commerce, bound to a Klard grant when the program is available in a served market.
Token scope
Provider-enforced
Intent-to-token binding
Direct Klard prevention
Merchant outcome
Observe-and-reconcile
AP2 mandates
Signed Agent Payments Protocol mandates map to Klard authority as portable protocol evidence — never as a replacement for policy.
Mandate proof
Protocol evidence, verified
Policy and financial state
Direct Klard prevention
Processor settlement
Provider-enforced
Network agent tokens
Network-issued agent tokens bind to Klard authority when supported issuer and processor programs make the path available.
Token issuance
Provider-enforced
Authority binding
Direct Klard prevention
Network lifecycle events
Observe-and-reconcile
x402 machine payments
Per-request machine payments over HTTP payment challenges, with the Klard authority model governing the request before the connected path executes it.
Challenge routing
Direct at the adapter
Wallet custody
Provider-enforced
On-chain settlement
Observe-and-reconcile
Purpose-bound virtual card+
Purpose-bound virtual card
Each approved request materializes a single-use virtual card carrying the strongest controls the issuer supports — amount cap, expiry, merchant restriction — and Klard answers the live issuer authorization itself, fail-closed.
Amount ceiling and tolerance
Direct Klard prevention
Single use and expiry
Direct Klard prevention
Merchant and category lock
Provider-enforced where supported
Re-check at authorization
Direct Klard prevention
Human checkout & step-up+
Human checkout & step-up
People execute with assigned cards and secure checkout; 3-D Secure and step-up bring the human back into the loop when policy asks for presence.
Budgets and approval thresholds
Direct Klard prevention
Cardholder verification
Provider-enforced
Receipts and settlement
Observe-and-reconcile
Cost-causing action gateway+
Cost-causing action gateway
Cloud, SaaS, and advertising actions create spend without a checkout. The gateway evaluates them as spend intents and executes through parameter-bound credentials.
Action allow or deny
Direct at the gateway
Committed-spend estimate
Observe-and-reconcile
Platform-side limits
Provider-enforced where exposed
Invoice & bank transfer+
Invoice & bank transfer
Approval-gated invoices and AP transfers under the same mandate, decision, and evidence chain.
Pre-execution approval
Direct at the adapter
Transfer execution
Provider-enforced
Settlement facts
Observe-and-reconcile
Agentic checkout tokens+
Agentic checkout tokens
Shared payment tokens for agentic commerce, bound to a Klard grant when the program is available in a served market.
Token scope
Provider-enforced
Intent-to-token binding
Direct Klard prevention
Merchant outcome
Observe-and-reconcile
AP2 mandates+
AP2 mandates
Signed Agent Payments Protocol mandates map to Klard authority as portable protocol evidence — never as a replacement for policy.
Mandate proof
Protocol evidence, verified
Policy and financial state
Direct Klard prevention
Processor settlement
Provider-enforced
Network agent tokens+
Network agent tokens
Network-issued agent tokens bind to Klard authority when supported issuer and processor programs make the path available.
Token issuance
Provider-enforced
Authority binding
Direct Klard prevention
Network lifecycle events
Observe-and-reconcile
x402 machine payments+
x402 machine payments
Per-request machine payments over HTTP payment challenges, with the Klard authority model governing the request before the connected path executes it.
Challenge routing
Direct at the adapter
Wallet custody
Provider-enforced
On-chain settlement
Observe-and-reconcile
Bounded and accountable, whoever spends.
AI agents and people at work
Give agents, employees, and contractors room to buy the tools that keep work moving, under the same budgets and approvals.
Team mandateActive
Approved categories
SaaS · API · Cloud
Approval above
$600
Accountable owner
Finance ops
Shared responsibility in everyday life
Use the same principle anywhere one person spends for another: clear purpose, clear limits, and no unlimited access.
Shared taskClear
Purpose
Weekly essentials
Maximum
$180
Expires
Saturday
EVIDENCE
One linked record.
Delegate, authority, request, decision, execution — and what remains unresolved — stay connected. When something goes wrong, you retell the story instead of reconstructing it.
unresolved facts stay visible — nothing is invented away
What needs to be clear before authority moves.
What is Klard?
Klard helps people and organizations govern spending carried out by AI agents or trusted people. It lets an accountable owner give a delegate a bounded mandate without handing over unrestricted access.
Who is Klard for?
The current pilot is for AI-native and automation-heavy teams governing SaaS seats, API credits, and controlled vendor or tool purchases made by employees and AI agents.
Is Klard only for AI agents?
No. AI agents create the new urgency, but the same authority model applies to trusted people. An accountable person or organization remains responsible for the money and the purpose.
What does access is not authority mean?
An AI agent may be able to call tools, reach a checkout, or request a purchase. That does not give it financial authority. The accountable owner defines the purpose, budget, vendors, amount, timing, and approval rules.
How does Klard make a request-time decision?
At a connected or supported control point, Klard evaluates a request against the authority in place. It can allow the request, require human approval, or decline it. Klard does not claim to control every payment or purchase path.
What evidence does Klard keep?
Klard keeps the delegate, authority, request, decision, execution result, and outcome linked. Where facts remain missing, conflicting, or unresolved, that context stays visible rather than being filled in with a guess.
How do broader people and household use cases fit?
The same authority problem exists when an employee, contractor, assistant, caregiver, or family member spends for someone else. Broader personal and household workflows are part of Klard's direction, not a released household product today.
Is Klard a bank or a general-purpose card product?
No. Klard is not a bank or a general-purpose card product. A card may be one controlled route, but it is not the product category or a promise that a particular financial product is available.
What does applying for the pilot mean?
Applications are reviewed for limited pilot access. Applying does not guarantee acceptance or access, and we use the workflow context to decide whether the pilot is a fit.
Current limited pilot
Apply for the limited pilot.
We're onboarding a small set of teams whose people and agents buy tools. Tell us who spends on your behalf, and we'll review the fit.
Klard - Financial Control for AI Agents and People