We're hiring at @KleePay.
We're building payment infrastructure for AI agents and looking for AI-native builders across engineering, product, growth, operations, and internships.
You don't need 10 years of experience, but you do need to move fast, learn fast, and figure things out without being told exactly what to do.
We care more about proof of work than credentials.
Competitive base salary + meaningful equity.
DM me your GitHub, X account, portfolio, side project, or anything you've built.
We're hiring at @KleePay.
We're building payment infrastructure for AI agents and looking for AI-native builders across engineering, product, growth, operations, and internships.
You don't need 10 years of experience, but you do need to move fast, learn fast, and figure things out without being told exactly what to do.
We care more about proof of work than credentials.
Competitive base salary + meaningful equity.
DM me your GitHub, X account, portfolio, side project, or anything you've built.
@WickJh007@KleePay we dont need to trust AI itself, and tbh humans make payment mistakes every day.
the question is whether AI can operate within better controls than humans.
AI agents are moving from answering questions to taking actions, but the moment an agent needs to spend money, the stack breaks.
you either give it raw payment credentials, which is unsafe, or you keep a human in the loop, which breaks automation.
@KleePay exists for the third path, we are building the control layer between AI agents and real-world payments, agents should not hold card numbers, private keys, or open-ended financial authority.
they should be able to request permission to spend, within clear rules: amount, merchant, time window, card, and workflow context.
cards are the bridge.
control is the product.
agent payments are the category.
before hiring our next team member, our 4 ppl founding team somehow became engineers, product managers, hr, finance, marketing, sales, community and operations.
thanks, @claudeai.