-
Notifications
You must be signed in to change notification settings - Fork 21
Flow of Funds
Christopher David edited this page Dec 22, 2023
·
11 revisions
- Pay bitcoin to as many people as possible, as much as possible, as fast as possible, with the easiest user experience.
- Make it as easy as possible for end-users to pay for agent usage.
- Individual users paying for agent usage via our self-serve web platform
- Companies buying agent usage in bulk
- Compute providers
- Model authors
- Data providers/curators
- Algorithm authors
- App developers
- Referrers
- Educators
- Users maintain a balance and can top up with Bitcoin, Lightning or credit card
- Contributors earn sats that get added to their balance
- Contributors can withdraw their balance via Bitcoin or Lightning
- Each agent can have its own revenue split
- Any part of an agent module may have an associated cost that is paid to one or more contributors
- Example:
- Alice adds "Resolve GitHub Pull Request" to the agent Skills database. The skill uses a specific chain of calls to APIs, LLMs, and vector databases.
- Bob configures his AutoDev agent to use that skill. He pays 12000 sats (USD ~$5.00) to run the agent job.
- Alice earns 2000 sats because she assembled the skill.
- Carol earns 1000 sats for providing compute for the vector embeddings and open model calls via her workerbee client.
- Dave earns 500 sats because his API key was used for the one call to GPT-4.
- Eve earns 120 sats because she referred Alice to sign up months ago.
- Frank earns 120 sats because he referred Bob to sign up yesterday.
- Grace earns 300 sats because her finetuned model was used in the skill flow.
- Heidi earns 300 sats because her custom dataset was used in the skill flow.
- OpenAgents keeps the rest because we're a business and want to grow our bitcoin stack too!
- Credit card top-ups:
- May require additional verification
- May not be withdrawn via Bitcoin/Lightning
- Will not be refunded
- Withdrawals may be disabled on a per-user basis for compliance reasons
- All payment code will remain open-source in this repo.
- Anonymized/aggregate payment data will be visible on our public accounting dashboard.