Earn

One membership. A shared pool. 90% to creators.

The whole economy on one page, for both of its sides: what a member's credits buy, and how extensions and services earn from the pool those credits split: with no telemetry anywhere, and a ledger anyone can read.

List your work Browse extensions

Credits

One membership. Two ways to spend it.

Almost everything in the gallery installs free, from anyone, with no cut taken from anybody. A membership adds credits, and a credit leaves your hands in exactly two places, both of which you trigger on purpose.

$20: a month
1,000: credits a day
15: credits to the cent

One-timePremium extensions

Back an extension by installing it

The install is the whole transaction. Nothing after it is counted, reported or charged for: using the thing you installed is free forever.

200credits, flat

Same number whatever you install, whoever made it. A price each listing could set would be the first thing anyone gamed.

1You approve the install, exactly like any other extension.
2200 credits go to the publisher named in the manifest.
3It is yours from then on: open it a thousand times, it never costs another credit.

A day's credits: 5 installs

If the donation cannot go through, the install stops. Nothing half-paid ever goes live.

Reinstalling charges nothing. An update can donate again, at most once a month.

Per runPremium services

Pay for a run that costs real money

Some tools are not a prompt and some glue: they call paid data APIs or burn real compute every time. Those are services, and they are metered per run.

Its own priceshown before you agree

Each service publishes what a run costs. The demo research run is 5 credits, so a day's allowance is 200 of them.

1Your agent finds one that fits and quotes the price and what is left today.
2You say yes in chat. One yes, one run.
3The platform makes the call for you: the provider never learns who you are, and you never hold its key.

A day's credits: 200 demo runs

If the service does not answer, your credits come straight back. A failed run costs nothing.

Every repeat needs its own yes. Nothing loops without asking you again.

90% reaches the creator

The same published share of a spent credit's value, whichever way you spent it. The rest runs the platform.

Capped at what you paid

Both draw on a daily allowance of 1,000 credits that resets at midnight UTC. You cannot direct more to creators than your membership provides, which prevents farming.

Nothing is metered

No usage counting anywhere, and none asked for. Installing is a choice you make; a run is one you approve. Credits you never spend pay nobody.

In practice

What a run looks like in chat.

Services aren't a store you browse. They arrive as an offer in the middle of real work. The offer follows the agent's standing etiquette, not its goodwill: name the service, quote the price and today's balance, wait for the yes, account for the run after. One yes covers one run; a run that fails to answer refunds itself.

The service here is invented. Each real one publishes its own price, shown like this before every run, and entered the catalog through a human review at the platform, not a signup form.

You

We're launching the beta next month. Which communities should we use, and when should we post?

Agent

I can scan the obvious subreddits myself for free. The catalog also lists a deeper option:

acme.reddit-researchPremium service

Audiences, posting windows and past results for your product.

40 credits per run · 1,000 left today

Want me to run it?

You

Go ahead.

Agent

Three communities stand out, each with a matching posting window. The full report is in research/launch-plan.md.

acme.reddit-research · one run · 40 credits · 960 left today

The platform makes the call; the provider never learns who you are. Fails to answer → credits come straight back.

A public monthly pool split by the credits members spend on install donations and service runs. Usage is never metered, free extensions never enter it and premium is opt-in.

The pool

Split by what members choose. Renewed monthly.

Creators don't set prices and members don't open wallets per tool. Memberships fill one pool, the credits members spend decide its split, and 90% of every spent credit's value reaches the creator it went to. Maintained work earns again: an update can donate again, at most once a month per install.

Get listed Maintain & grow

The rules

The whole deal, at a glance.

No telemetry, ever

The pool pays only on two deliberate acts: an install you approve and a run you approve. Your machine reports nothing.

The ledger is public

GET /pool/transparency, no login: every listing's donors, runs and earnings, and the split itself, month by month.

Failures refund themselves

Credits return the moment a service fails to answer — enforced in code before the call, not argued through a support queue.

The catalog is curated

Every service is admitted — and, if it goes bad, delisted — by the platform. No form puts an endpoint in front of your agent.

Farming can't profit

Support is capped at each member's own membership, so fake spend always costs more than it returns — at any scale.

Built in the open

Live now: memberships, donations, metered runs, the ledger. Next: payout rails — earnings accrue publicly until they land.

Read the fine print

Every tile above argued in full: the arithmetic, the design choices, and what exists today.

Build something worth backing.

The pool pays what members choose. The way in is the same as for anything else here: build it, list it, keep it good.

Build an extension Get listed