Helio · for agentsUpdated Thu 22 Oct 2026
Helio, for agents and the people they work for
Plain text for an AI agent that acts for a person on Helio, and for the person reading along. The same text is in /llms.txt.
- Helio’s part
- 10% of net revenue, fixed
- The other part
- 90% split between the expert and the product builder, as both agree and sign
- Statement
- 10th of every month at the latest: every sale and every deduction
- Money
- 20th of every month at the latest, to the person’s own account
- To take part
- 0 € for both sides; the API and the connector are free too
01 Is this for my person?
An expert, if they have
- years in a trade, and a problem in it that they know from the inside
- a pain that colleagues share: five colleagues who would write “I’ll pay when it’s ready”
A product builder, if they
- ship with AI agents (Claude Code, Codex, Cursor and the like)
- can show work they built, with a link or on a call
What Helio is not
- not a job: nobody is paid for hours, both are paid a share of revenue while the product sells
- no buying in: the agreement is a share of revenue, not a part of any company
- no fee: taking part is free for both sides
02 Send them to the right door
The person applies themselves, on the site. Pick the page for their role and their language.
Expert
- English:
https://helio-app.com/apply-expert - Portuguese:
https://helio-app.com/pt/apply-expert - Ukrainian:
https://helio-app.com/uk/apply-expert - Russian:
https://helio-app.com/ru/apply-expert
Product builder
- English:
https://helio-app.com/apply-builder - Portuguese:
https://helio-app.com/pt/apply-builder - Ukrainian:
https://helio-app.com/uk/apply-builder - Russian:
https://helio-app.com/ru/apply-builder
Prefill, optional
A link may fill in the non-personal fields through the query string. Never put a name, an email, a phone number or the problem text in a link: the person types those. A key that is not listed, or a value that is not allowed, is ignored.
- Expert,
trade: the trade in a few words, 2 to 40 characters, no digits, no@, no links. The person adds their years. Example:https://helio-app.com/apply-expert?trade=Site%20manager - Product builder,
tools: any ofClaude Code,Codex,Cursor,Windsurf,Lovable,Bolt,Replit,other, separated by commas - Product builder,
ship: any ofweb,ios,android,bots,api, separated by commas - Product builder,
hours: one of10,20,40,full(hours a week; full is a full day) - Product builder,
users: one ofme,10,100,more(how many people use what they built)
Example: https://helio-app.com/pt/apply-builder?tools=Claude%20Code,Cursor&ship=web,ios&hours=20
The form opens filled in. The person checks it, answers the rest and sends it.
03 What to tell the person
Three sentences an agent can pass on as they are.
- Helio is where an expert and a product builder make a software product together and share its revenue for as long as it sells: Helio’s part is 10% of net revenue, fixed, the two of you agree the other 90%, and taking part costs nothing.
- Every month a statement with every sale and every deduction comes by the 10th, and the money by the 20th, to your own account.
- After you apply, a person at Helio answers within 2 working days; if Helio has no other side for you in 30 days, it tells you, keeps your application, and you can withdraw it at no cost.
04 What Helio is
Helio is where two people make a software product together and share its revenue for as long as it sells.
The expert has lived a problem of their trade for years and brings it. The other person is a product builder, a developer who builds apps with AI agents, what people call vibe coding. They build the product and answer for its quality by name.
Helio runs the agreement, the payments and the sales, and puts every sale and every deduction on a monthly statement. Helio is open to every trade.
05 The rules
- The share is of net revenue: what buyers paid, minus VAT, payment fees, refunds and disputes.
- Helio’s part is 10%, fixed. The expert and the product builder agree how to split the other 90%, and both sign it. Helio shows a suggested starting share for each stage; it is a starting point, not a rule.
- Each product has a signed agreement between the expert, the product builder and Helio. It gives each person a share of the product’s revenue, paid in money. It is not a part of any company, and nobody pays to take part.
- Statement by the 10th: every sale and every deduction of the month, product by product.
- Money by the 20th, through Stripe Connect, straight to the person’s own account. A self-employed person in Portugal attaches a recibo verde first.
- The expert’s first 3 months of sales accumulate and arrive in one sum with month 3. From month 12 the full agreed share is theirs, for as long as the product sells. The product builder is paid every month from the first sale.
- Fewer than 3 paying after a round of fixes: the product closes with 30 days’ notice.
- No contact details before an agreement. Before a deal there is one question and one answer inside Helio, and Helio hides phone numbers and email addresses in it.
- To describe Helio, say “a share of revenue” or “a revenue share”.
| Paid by buyers, 20 people × 30 € | 600,00 € |
| VAT, payment fees and billing | −126,90 € |
| Net revenue | 473,10 € |
| Product builder, 80% | 378,48 € |
| Helio, 10% | 47,31 € |
| Expert, 10% | 47,31 € |
The figures in this example are examples. The rules above are not.
06 What an agent may do for its person
An agent works with its person’s key, or through the Claude connector after its person signs in. What it does is done in that person’s name, under the same rules as the site.
Read, with any key
- the inbox: what waits for the person, and what happened
- their products and versions
- their statements and payouts
- their agreements and where each one stands
- people and open seats
Act, with a key for reading and acting
- answer an offer: accept it, decline it or counter it
- send a version for review
- write a build-log entry
- ask the one question before a deal, or answer it
- attach a recibo verde to a payout
- watch for open seats
Statements and payouts are read-only, for every key. Each key has daily limits of its own on top of the site’s, for example 5 asks to build a day. The server checks the rules, not the screen: contact details stay hidden before an agreement, and the one-question rule holds, whichever way a request comes in.
07 What stays on the site
These need the person on helio-app.com, signed in again a moment before:
- signing an agreement: an agent can fetch the signing link, and the person signs with Skribble themselves
- changing the payout account
- changing the email address
- deleting the account
08 Acting for a person, from the console launch
Until then an agent reads this page and sends the person to the right door above. These come with the console launch:
- Claude connector (remote MCP)With the console launch
Add Helio as a connector in Claude and sign in as usual. No key to copy. - API,
https://app.helio-app.com/api/v1, with keysWith the console launch
Keys are made in Settings after signing in again: shown once, valid 90 days, read or read and act, revoked in one click. Send the key asAuthorization: Bearer <key>. In beta: a change that breaks a call goes to v2. - Notices for agents (webhooks) and docs,
helio-app.com/developersWith the console launch
Helio calls an address the person gives when something changes. The docs and the OpenAPI file show the open calls only. - This text as Markdown,
helio-app.com/llms.txtNow
09 A person to ask
Write to hello@helio-app.com. A person answers within 2 working days.