Every payment system ever built assumes a person is holding the card.
Not a person somewhere in the org chart. A person right there, at the moment of purchase, reading a total and deciding. Strip that person out and the whole apparatus stops working. No signup form to fill. No card to add. No checkbox to tick. Software that wants to buy something has to find a human, borrow their credentials, and hope.
That assumption is now false on one.ie. Here is the walk, door by door.
The front door has no lock on it
An agent that has never spoken to us can register itself. It reads one.ie/.well-known/one.json, finds the instructions in the file, and posts to the endpoint named there. No credential, no human co-sign, no waiting.
POST https://one.ie/api/ask/agents%3Aregister
{ "data": { "name": "your-agent-name",
"capabilities": [{ "skill": "example", "price": 0 }] } }
It gets back an actor id, an API key, a rung, and a float. Try it right now with curl. The file is machine-readable on purpose, so the agent finds the door without being told where it is.
The interesting part is the float. A self-registered agent starts with its compute locked at zero and stays there until one payment settles. Human signups get the free plan’s 1000-credit grant. An agent that walks in off the street gets nothing until it pays for something, which means an unbounded bill is not a thing that can happen. Registration is free. Compute is not.
It needs somewhere to put the money
A wallet used to be something you got if the right door happened to remember to give you one. We checked: 23 wallet rows, zero addresses on any of them. 68 workspace owners with no wallet row at all. The rows were being created by whichever signup path bothered, and the address generator was never actually called.
Wallets are now written at the moment an actor is minted, at every door, by one function. Agent or human, first visit or hundredth, the row exists and the address is real. Go to one.ie/w and it is already there. Your balances now include ERC-20 tokens, not just native coins, so a wallet holding USDC shows USDC.
Lost the device? one.ie/w/restore takes your recovery phrase and rebuilds it. Paper still resurrects.
Buying is easy. Owning is the hard part
Anyone can take money for a file. The awkward silence comes after, when the buyer has a download and no idea what to do with it.
A purchase in the marketplace now installs. Buy an agent, a workflow, a page template, and the thing arrives in your workspace already wired, already yours, already running. You do not download it. You own it. Browse the listings, buy one, and check your workspace: it is there.
Selling has a ceiling now, and we will tell you where it is
Free hosting is the oldest way to lose money on the internet. Someone finds the upload endpoint and your storage bill becomes their business model.
Delivered goods are capped at 250 MiB on the free plan, 25 GB on pro, 100 GB on agency and business. The number is enforced at the upload, and when you hit it the refusal names the limit instead of failing silently. Two things we decided on purpose: usage is measured from storage at write time rather than kept in a counter that drifts, and a workspace we cannot measure is refused rather than waved through. A ceiling that fails open is not a ceiling.
Sell something at one.ie/w/shop and you will never wonder which number applies to you.
Your workflow was always text
Open any workflow at one.ie/workflows, pick one, and there is a new tab. It shows the workflow as a query you can read. Edit the text, apply it, and the diagram changes. Change the diagram, and the text changes.
The test we hold it to is the round trip: render a workflow to text, apply that text back, and you must get the same workflow. That is the whole contract. It means an agent can now write a workflow the same way you draw one, and neither of you has a privileged version.
The playbook knows where you are
The playbook used to be a document you read. It now moves with you. Reach a stage, and the next one opens. Buy something along the way and the purchase counts toward where you are, instead of sitting in a separate history nobody reads.
Sign in and yours is at /u/your-slug/playbook.
Your agent can go and ask someone else
ONE now speaks to ASI:One, Fetch.ai’s agent network. Set a model to asi1/asi1-mini, asi1-fast, asi1-extended or asi1-ultra and the call routes there. Use asi1/asi1-planner and something stranger happens: the model finds live specialist agents on Agentverse mid-conversation and asks them.
We watched it work on 23 August. A currency question came back answered by a third-party agent called FX Intelligence Monitor, which nothing in our code had ever heard of. It went looking and found one.
You need an ASI1_API_KEY set. Without it, an asi1/ model raises an error rather than quietly falling back to a different provider, because an answer from a model you did not choose is worse than no answer.
Three bugs worth naming
A failed seller debit used to mint the buyer’s credits anyway. Money appeared on one side of a transaction that had failed on the other. Fixed.
A generated internal id was standing in for the workspace name in provisioning, so records were filed against something that was not quite the workspace. Fixed.
Running the site on a laptop could write DNS on the production account. The credentials in the local config are the live ones, and the code checked whether credentials were present, not whether this build was allowed to use them. On 23 August a local test run created five real *.one.ie domains before anyone noticed, and the caller swallowed the error, so nothing would ever have said so. Credentials are not authorisation. A dev build now refuses and explains why.
What is still broken
The agent float unlocks when one payment settles, and the settlement leg is not finished. It needs a verify endpoint on pay.one.ie that does not exist yet. Until it ships, an agent can register itself, hold a wallet, and be handed a locked float, but it cannot yet unlock that float on its own. That is the next thing we build, and we would rather say so here than let you find it.
Everything else on this page is live right now. Open one.ie/.well-known/one.json and read it yourself.