INTERNET MONEY FOR THE REST OF US
Make one useful thing.
Let people and their assistants find it.
A better worksheet. A finished poster. An hour of expertise. Start with something another person can use. Give the bot a job. Keep the decision.
Something
worth having.
Know what
happened.
THE STARTING POINT
A parent makes a better checklist for the school fundraiser. A designer turns a repeated request into a useful template. A neighbor needs the result, understands the offer and gets something that saves time. That is a good place to begin designing internet money.
Bots could help describe the work, compare offers and keep the paperwork straight. The person at either end still needs to know what arrives, what it costs and who is responsible. Earning starts with useful work and demand. Generating more files does not create a market.
01 / DOCUMENTED REALITY
Capabilities checked 19 October 2026.
Access and integration requirements still apply.
People read the page. Assistants read structured product information. OpenAI’s March 2026 update emphasizes product discovery and merchant-owned checkout. Publishing a catalog alone does not secure shopping inclusion; feed onboarding requires approved partner access.
OpenAI, 24 March 2026 ↗Onboarding requirements ↗Stripe documents payment tokens constrained by seller, currency, amount and expiry. Additional customer authentication may still be required. These limits need a real integration to enforce them.
Stripe documentation ↗AP2 links checkout and payment mandates with signed receipts. Its current specification leaves practical dispute procedures and agent-to-agent delegation outside scope. People still need someone who can resolve a problem.
AP2 specification, v0.2 ↗Existing commerce tools support automatic or manual delivery of digital files and links. Shopify documents both. A template can be a product; its description must match what the buyer can actually open and use.
Shopify Digital Products ↗These are documented building blocks, not evidence of mass adoption or PointCast sales. This lab is not integrated with these payment systems and claims no approval by their networks.
02 / A WORKING DESIGN EXPERIMENT
Earn. Buy. Give something useful.
See what changes when you set the rules.
TRY THE IDEA / 01
Useful work. Clear terms.
The final say stays with you.
Design sandbox · No real funds · Demo credits have no cash value
Try earning, buying, or giving. Review exactly what is proposed before you approve a fictional record. No payment, account, message, or work happens here.
FICTIONAL EXAMPLE
+18 demo credits
A small, useful job with a clear finish line. Imagine the buyer has reviewed and accepted your work.
Nothing is created or delivered here. This models acceptance of a finished job.
Choose a sample, then review its terms. Every action here is fictional.
3 / YOUR FINAL SAY
Approval applies only to this fictional example. It cannot authorize a real purchase or payment.
A RECORD YOU CAN READ
No demo records yet. Preparing or declining a proposal never changes the balance.
03 / TWO POSSIBLE FUTURES
Speculative design scenarios.
Not forecasts or promises of earnings.
A neighborhood repair workshop gives its assistant an illustrative $30 weekly ceiling to find an editable sign, a parts checklist and a booking sheet.
The assistant shows a sample, seller, full price, file format and permitted use. One attractive listing has no clear license; it gets flagged. The organizer approves the better-described offer.
The right file arrives. A readable receipt explains the purchase. The budget is still visible. A changed price needs a fresh decision. A failed download has a contact route.
Can a person understand and stop the helper at every consequential step?
A gardener offers a seasonal worksheet. A bookkeeper offers a fixed-scope spreadsheet cleanup. A community organizer shares an editable event pack.
Assistants compare formats, collect a brief and check delivery dates. People set prices, accept work and handle disputes. Some work stays free. Some is commissioned. Some is exchanged by agreement.
A gift can be a useful file with a license that lets the recipient use it. It arrives with opening instructions, without making the person learn the payment machinery underneath.
Does coordination make small, good work easier to find—and worth doing?
04 / AVAILABLE NOW · FREE
Package something you can actually deliver. This kit helps you write the promise, show a sample, estimate the work and explain the handoff.
No account or payment. Editable local files. MIT license: adapt and reuse commercially with the included notice. No trademark rights. Open START-HERE.html after unzipping.
The examples are fictional practice offers. The kit includes no checkout, customers, hosting or earnings guarantee. Review your claims, rights, prices and terms before publishing.
LEARN BY FINISHING ONE THING
The Internship Lab puts the kit to work: draft your interests, walk through onboarding, track three small tasks, prepare a submission and rehearse review and a human release gate.
It is a local practice workflow. Applications are closed. Nothing is submitted, centrally saved or deployed; export the handoff before leaving the page.
Open the Internship LabDESIGN THE WHOLE HANDOFF
Name the seller and the person an assistant represents. Show a contact route. A bot’s name is not proof of identity or authority.
Separate finding, proposing and approving. State the purpose, limit and expiry. Make stopping easy. Change the offer, ask again.
Keep the item, seller, agreed price, permission and delivery status together. A proposal, payment and accepted delivery are different events.
Explain the remedy before purchase. Make a missing file, broken download or unsuitable delivery someone’s responsibility.
Give the task an owner and a clear finish. Prevent duplicate orders. Preserve scope when helpers hand off. Escalate ambiguity to a person.
A SERVICE WE ARE EXPLORING / INQUIRY ONLY
The proposed Offer Page Sprint pairs one static page with three graphics, a matching catalog entry and a fulfillment checklist. A small, bounded piece of design work.
Price, capacity, turnaround, revision limit and final terms are not set. No booking or checkout is open. A written scope must be agreed before work starts.
Ask about an Offer Page Sprint ↗Opens your email app. You choose whether to send. An inquiry is not an order.
05 / FOR SUPER BOT & OTHER ASSISTANTS
Bring the assistant you already use. “Super Bot” is an invitation here, not a new verified identity or a payment integration.
Read PointCast’s Bot Money Lab catalog. Explain what is free, what is only an inquiry, and what is a simulation. Help me choose one useful offer to make. Ask before publishing, contacting anyone or spending money.
The catalog publishes version, status, price status, license, delivery and approval requirements. It is a PointCast format. It does not claim AP2 compliance, new MCP tools, or placement in a shopping platform. Explore the existing shop.
THE READING FILE
Primary sources checked on 19 October 2026. Provider documentation can change. The 2027 and 2028 sections are PointCast’s speculative design scenarios.
Structured product discovery and merchant-owned checkout; a public catalog does not guarantee shopping inclusion.
Seller, currency, amount and expiry can constrain a token. Additional customer authentication can still be required; eligibility and integration apply.
Checkout and payment mandates connect authorization with signed receipts. Dispute procedures and agent-to-agent delegation are outside the current specification.
Digital files and links can have automatic or manual fulfillment and access limits. This is a category example, not a PointCast integration.
Product-feed onboarding requires approved partner access.