launchlab01 / Source
Start with
your code.
Bring a supported public GitHub repo. Pin a version. Give every experiment a clear starting point.
Static packages with a launchlab.json manifest.
A LAUNCH STACK FOR WEB3
From code.
To what’s next.
Your repo, a working preview, and a reason
to build the next version.
Local prototype. No wallet required.
Everything connects.
Take it apart. See what each layer can do.
Start with
02 / Preview
Make it
something real.
Give that version an isolated local preview. Check that it works before asking someone to try it.
Local static previews today. Public hosting is planned.
03 / Missions
One task.
Useful attempts.
Invite your testers. Reserve a place. Reward honest attempts, including the ones that uncover a problem.
Demo credits have no cash value. Recruitment and real payouts are planned.
04 / Feedback
Find the friction.
Move forward.
Keep observations tied to their release. Review the evidence and take a better question into the next version.
Illustrative feedback. Paid participation alone does not validate demand.
05 / Agent
Your intent.
Connected.
Let your agent connect the repo, preview, mission and findings through local MCP tools. You stay in control of the plan.
A brief is a draft. It does not start a run or move funds.
USE CASES
Start with a question and a repo
New task / LaunchLab
Draft
Describe your project, include your GitHub repository, and tell your agent
what you want to learn.
Does the idea
make sense?
Find out whether a first-time visitor understands your prototype.
Where do
people get stuck?
Test a static onboarding flow with your invited cohort.
Can the loop
work with my agent?
Connect a supported project to a mission and return the evidence.
WHY OKX
Where agents
become customers.
Our next step: bring the launch loop to the agent economy through OKX AI and X Layer.
Explore OKX AIDiscover
A planned OKX AI listing to help agents find LaunchLab.
Commission
Exploring A2A jobs and x402 calls for useful work.
Settle
A future payment path on X Layer, verified step by step.
Planned integrations. Public hosting, tester recruitment and real rewards are not connected. Independent project; no OKX endorsement.
GOOD TO KNOW
Before you begin.
What can I try right now?
The local demo can import a compatible public GitHub project or the included example, create a versioned static preview, open a test mission and collect feedback. Rewards use demo credits with no cash value.
Does LaunchLab host any Web3 application?
The current adapter supports static projects with a LaunchLab manifest. Backend execution, smart-contract deployment, wallet-enabled previews and managed public hosting are future capabilities. The included example is ready to try.
How will I use LaunchLab through OKX AI?
OKX’s current service pages guide you to copy a service prompt into your own agent. We’re preparing that handoff for LaunchLab. You can draft your brief now; a verified listing and service ID will be added when the integration is ready. Read the official setup guide ↗
Where do the testers and rewards come from?
For the first pilot, builders invite their own cohort. LaunchLab records the task, participation and evidence. Recruitment from an external tester network and real onchain payouts are not connected yet. Honest reports of failure should qualify just as useful successful attempts do.
Does a successful test validate demand?
A test can reveal usability problems and whether someone can complete a task. Paid participation alone does not prove organic demand or willingness to buy. Keep those questions separate when interpreting the results.
BUILD. TEST. LEARN.