u/Alexpplay

Building AXON 402 — infrastructure for AI agent commerce.

AI agents are about to start transacting with the internet directly.

The current stack for that is honestly terrifying: raw API keys, unrestricted wallets, no governance, no audit layer.

We’re building the control + payment runtime for autonomous software:
policy-controlled wallets
approval flows
spend governance
risk analysis
receipts/audit trails
machine-to-machine payments (HTTP 402 / x402)
MCP-native agent workflows

Already:
- live on Base mainnet
- open-source
- working prototypes
- strong technical direction
- OpenClaw plugin
- CLI
- MCP

I’m now looking for a business/finance-oriented cofounder to help push this to the next level:
- fundraising
- investor relations
- GTM strategy
- partnerships
- helping close the round

Important:
I’m not looking for a pure “business guy” disconnected from the technology.

You should understand:
> AI agents / agentic workflows
> LLM fundamentals
> why autonomous commerce is emerging
developer infrastructure dynamics
technical products at a strategic level

You do NOT need to code full-time, but you should be able to deeply engage with the product and communicate the vision credibly to investors and partners.

Background:
I’m based in Zurich and have been building across AI systems, agent infrastructure, workflow tooling, and growth/product engineering.
Looking for someone long-term and ambitious.
Not interested in building another wrapper SaaS.

reddit.com
u/Alexpplay — 5 days ago

I built a way for AI agents to buy and sell paid APIs/tools

I’ve been working on Axon402, a project around payments for AI agents.

The basic idea: if agents are going to do real work, they’ll eventually need to buy things like APIs, data, files, tools, compute, or services. But giving an agent raw wallet/card/API-key access feels unsafe, and keeping a human in every payment step kills the point of automation.

So I’m building a system where:

  • sellers can expose APIs, files, or tools that agents can pay for
  • agents get scoped spending access instead of raw wallet power
  • operators can set budgets, limits, and allowed resources
  • risky purchases can pause for approval
  • every payment gets a receipt / audit trail

The demo flow is:

seller creates paid resource -> agent tries to buy it -> policy check -> approval if needed -> payment -> receipt

I’m still validating whether this is a near-term problem or mostly early infrastructure for where agents are heading.

I’d love honest feedback:

  1. Are any of you building agents that need paid APIs/tools/data?
  2. Would you let an agent spend money if it had strict limits and approvals?
  3. If you sell APIs or tools, would you want a simple way to charge agents per request?
  4. Does this feel useful now, or too early?

Project: https://axon402.com

Happy to share more details if useful.

reddit.com
u/Alexpplay — 8 days ago

Are any of you letting agents spend money yet?

Hey everyone,

I’m trying to understand how people are thinking about payments for AI agents.

Right now, most agent workflows I see either:

- don’t spend money at all

- use API keys / credits behind the scenes

- experiment with wallets, but without much control around them

I’m the founder of a startup which tries to solve this problem.

The core idea is to separate operator agents from runtime agents.

The operator / orchestrator can:

  • create wallets or spending contexts
  • assign budgets
  • define policies
  • approve risky requests
  • manage seller resources

Runtime agents / subagents can:

  • spend only from their assigned wallet
  • follow a specific policy
  • call paid APIs, files, or tools
  • request approval when needed
  • produce receipts and audit trails

So in a multi-agent system, the orchestrator can provision controlled spending environments for subagents, without giving every worker agent full financial authority.

So the basic loop is:

`seller creates paid resource -> agent tries to buy it -> policy check -> approval if needed -> payment -> receipt`

I’m still trying to validate whether this is an actual near-term pain or mostly a future problem. My intuition is that as agents start doing more real work, companies won’t be comfortable giving them raw wallets, cards, or unrestricted API credentials.

Curious how people here are handling this today:

  1. Do your agents ever need to pay for APIs, data, tools, compute, or services?

  2. If yes, how do you control / approve that spend?

  3. Would something like scoped wallets + policies + receipts be useful, or overkill right now?

  4. If you are building agent tools, would you want a simple way to sell them per request?

Not trying to hard-sell. Mostly looking for honest feedback from people actually building with agents.

Also, if anyone does really use payments already on their agents and want to have a chat please DM me, I really want to find out if I am into something or not.

reddit.com
u/Alexpplay — 9 days ago
▲ 3 r/AIAssisted+1 crossposts

I’m curious how people here think “agentic commerce” might evolve in practice.

Most examples I’ve seen are fairly simple: an agent pays for an API call, a file, some data, or a tool invocation. That seems plausible, but I’m not sure whether it captures the whole space or just the first obvious use case.

If agents become more common in business workflows, what do you think they will actually buy, sell, request, or delegate?

Some open questions:

- Will this mostly look like paid APIs and metered tool use?

- Will agents transact with other agents directly, or mostly through existing SaaS/products?

- What kinds of things would be hard to express as a simple API call?

- Where do trust, identity, permissions, and audit logs matter most?

- Do you expect marketplaces, private networks, vendor-style relationships, or something else?

- What would make you comfortable, or uncomfortable, letting an agent spend money or request work?

I’m interested in broad opinions, including skeptical ones. I’m trying to get a better mental model for what this could become beyond the current demos and buzzwords.

reddit.com
u/Alexpplay — 18 days ago

Every SRS app I've tried (Anki, Duolingo, etc.) treats each flashcard as its own thing. If you learn "möchten" in one sentence and see it in another, the app doesn't connect them. Two separate cards, zero shared knowledge.

I'm building an app that fixes this.

Every phrase you review updates the mastery of each individual word inside it. The system builds a graph of your entire vocabulary and schedules reviews based on your weakest words, not your oldest cards.

The other core feature: big button, say what you want to say in your language, get it translated + broken down word by word. No pre-made lessons. You learn the vocab you actually need.

Got a rough demo working. Curious if this resonates with anyone or if I'm overthinking it. What would make you try something like this?

Does this already exists?

reddit.com
u/Alexpplay — 22 days ago