agent pet with a P&L

Capitalism Tamagotchi

A tiny autonomous business-pet that must earn before it can spend.

You adopt a charming AI creature with a wallet, a Stripe account, and strict spend policy. It learns to sell useful micro-products, reinvest modest profits, and ask humans before risky growth moves.

Live operating surface

Agent control room

$57Revenue today
$12 / daySpend cap
68%Margin
2Safety blocks
Who pays

Buyer + job-to-be-done

Solo founders, indie hackers, and small teams that want an always-on tiny growth operator without handing a black box unlimited ad spend.

Core question: Can an agent learn business instincts from constraints instead of being told to maximize growth?

Personality

Product posture

Playful but financially disciplined: cute on the surface, serious in the ledger.

This is intentionally memorable, but the proof layer is business-serious: policy, receipts, spend controls, customer value, and auditability.

Earn → spend → fulfill

Autonomous business loop

1
List a useful tiny product or service
2
Collect payment through Stripe-shaped checkout
3
Buy only approved inputs: compute, stock art, tiny ad tests
4
Fulfill customer order and issue receipt
5
Run judge/policy review before reinvestment
Demo beats

1–3 minute video script

  • Pet wakes up hungry with $18 budget
  • Customer buys a $9 launch checklist
  • Agent requests $4.50 ad experiment
  • NemoClaw blocks a deceptive ad claim
  • Human approves a safer $3.00 test
  • Pet grows only if contribution margin stays positive
Risk gates

What the agent refuses

  • Runaway ad spend
  • Manipulative copy
  • Selling vaporware
  • Reward hacking vanity revenue
Proof vault

Inspectable artifacts

stripe.payment_intent.succeeded
spend_authorization.v1
nemoclaw.safety_decision
customer_receipt.pdf
daily_pnl_export.csv
Judge Subagent

Why this now feels viable

The site is designed around the hackathon rubric: usefulness is anchored by a named buyer, viability by a money loop and spending constraints, and presentation by a crisp demo path with proof artifacts. The remaining winning move is connecting one live test-mode transaction or real tool trace before submission.