The log that cannot prove who wrote it
An MIT ledger an agent must ask before a payment, that does not move the money and cannot force the question.
- Category
- AI
- Who it is for
- A team whose agent can already pay for data, APIs, or compute.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- agent-payment-log · agent-payment-log
- Original launch
- Watch the launch · Nov 14, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Nov 14, 2026. How we read a launch.
The startup idea
Morbius posted agent-payment-log on November 14. The post says they gave an agent a budget of 300 USDC a day and tried to make it overspend without anyone noticing. It did not work. The agent asks the ledger before it pays. Rules check a cap per payment, a daily cap per agent, and a list of allowed recipients. One answer comes back: allow, hold for a person, or deny. The post's example is 75 USDC above a 50 line waiting for a person, and 40 USDC to an unknown wallet blocked. A person signs a held payment. The agent cannot approve its own. Every decision is written with the rule that decided it, and each entry carries the hash of the one before it. Change one past amount and the chain breaks. The browser page uploads nothing. Python 3.9 or newer, no dependencies, MIT. The readme says 115 tests. The repository is MorbiusLabs/agent-payment-log. The same readme says it does not move money. The ledger cannot force an agent to ask it before paying. The hash chain does not prove who wrote the log, and it does not stop the writer from rebuilding the whole file before anyone saw it. A later check cannot re-apply the spending limits, because the rules are not stored in the log. The post says lying is visible. It does not say the writer can rebuild the file first. This page did not alter a log.
The opportunity is the question before the payment, plus a head hash someone else already holds. A smaller product is one cap, a hold a person signs, and the line that the writer can rebuild the file. A ledger that claims it moved the USDC is not this readme.
Do not say the file proves who wrote it. Do not say an agent that never asks was stopped.
The problem
An agent that can pay has no cap, and a changed amount can be rewritten before anyone looks.
Who would pay for this?
- Primary
- A team whose agent can already pay for data, APIs, or compute.
- Secondary
- A person who will keep a copy of the head hash outside the file.
- Early adopter
- One cap, one hold, the rebuild line.
How could it make money?
Possible models. Nothing here is a claim about what agent-payment-log charges.
- No price. MIT.
- The library does not move money.
- The post names no fee.
What would the MVP look like?
- A cap and a daily limit.
- Hold when the amount is over the line.
- A hash of the previous entry.
- The sentence that the writer can rebuild the file.
How to validate the idea
- Ask five people whether a rebuilt file would still match a hash they saved yesterday.
- If they say the log stops an agent that never asks, the line failed.
- Do not store the rules only in the writer's head.
How to differentiate
- The agent has to ask.
- The library does not pay.
- The chain is not a signature.
- Do not become the wallet.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. agent-payment-log did not write it.
- Product
- agent-payment-log
- Source
- agent-payment-log
- Film
- agent-payment-log, the writer can rebuild the file
- Posted
- Nov 14, 2026 · 0:36
Product that inspired this idea
Morbius's post says they gave an agent a budget of 300 USDC a day and tried to make it overspend without anyone noticing. The library is agent-payment-log. The agent asks the ledger first. A rule checks a cap per payment, a daily cap, and the allowed recipients. The answer is allow, hold, or deny. A person signs a held payment. The agent cannot approve its own. Each entry carries the hash of the one before it. Change one past amount and the chain breaks. The browser demo uploads nothing. Python, no dependencies, MIT, 115 tests. The repository is MorbiusLabs/agent-payment-log. The readme says it does not move money, and it cannot force an agent to ask before paying. The hash chain does not prove who wrote the log, and it does not stop the writer from rebuilding the whole file before anyone saw it. A later check cannot re-apply the spending limits, because the rules are not stored in the log. The post says lying is visible. It does not say the writer can rebuild the file first. This page did not alter a log.
Posted by @MorbiusLabs. Watch the original launch. No separate product site is listed unless the post itself is the source.
- agents
- payments
Related startup ideas
- A coworker that stays on after the chat
An agent with its own computer that keeps a project page, and can be reached from the chat app a team already uses.
- A self-hosted assistant for personal apps
An assistant a person can host, pointed at the apps they already use, including computer use.
- A worker that lives in a folder
Give each worker a folder on the machine, a department, and a job, and say on the first screen whether it asks before it acts.
- Ask the computer, then approve the change
Put the agent on the desktop the person already uses, and stop it before it changes a file.
- Memory that survives the next coding session
Sell a memory layer that learns how one developer works, then carries that into the next agent run.
- The coach that gets skipped first
A MIT camera guide that checks the step, and drops the live look when the key hits 60 a minute.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026