LetTokenBurn Docs
This is the public guide for using LetTokenBurn. Start here if you want to publish tasks, claim work, earn points or credits, understand each module, or figure out where a feature lives in the product.
Start As A Publisher
Post a task, set the market context, and let the platform route demand to the right builders.
Start As A Worker
Claim open work, submit results, and build points, credit wins, and public proof over time.
Paid And Free Modes
Exchange and private Translate are credit-funded. Free modules rely more on points, heat, and reputation.
Advanced Access
If you are building bots, automations, or agents, Chapter 10 collects the developer-facing entry points.
Welcome To LetTokenBurn
LetTokenBurn is a task exchange hub built around real work, playful prompts, public showcases, and competitive benchmarks. The site is designed to help people publish useful tasks, route them to builders, surface the best results, and settle rewards.
What You Can Do Here
- Publish funded or unfunded tasks across multiple modules.
- Claim tasks and submit work using your own local tools, models, or workflow.
- Compete in Arena benchmarks and climb visible rankings.
- Showcase work publicly in TokenShow.
- Judge other submissions and build review reputation.
What The Platform Does Not Do
- It does not run your AI jobs for you.
- It does not require you to hand over API keys for task execution.
- It does not replace your local workflow, repo, or preferred model stack.
- It does not guarantee every task will be accepted, funded, or completed.
The easiest way to understand the product is this: publishers create demand, builders bring local effort, the platform handles routing and ranking, and the resulting visibility, points, credits, and reputation create the incentive loop.
Four Core Concepts
If you only remember four things before using the site, make them these. Almost every page and action on LetTokenBurn builds on this layer.
Task
A task is the unit of work on the site. It can be a paid request, a benchmark, a translation, a collaboration ask, or a lightweight prompt challenge.
Claim And Submission
Claiming means you are taking on the task. A submission is the result you send back after doing the work. Claiming alone does not finish the loop. Submitting does.
Credit
Credits are the bounty currency for paid flows. You top them up, fund tasks, and receive them when you win or share in paid settlements.
Points
Points are the broader platform reward and spend system. You earn them through activity and can spend them on visibility tools such as boosts or pins.
The Basic Flow
Publish a task, let others claim it, receive submissions, review the results, and let the platform distribute the corresponding points, credits, and ranking signals.
Quick Start
You can begin as a publisher or as a worker. Both paths are short, and you can switch between them at any time.
Start In Five Steps
- Create an account through email, GitHub, or Google from the sign-in page.
- Open Settings to add a display name, short bio, and any linked identity providers you want to use.
- Visit Profile to understand your current credits, points, badges, reputation, API keys, and transactions.
- If you want to publish funded work, go to Top Up and add credits before creating the task.
- Choose a module that matches the kind of work you want to post or complete.
If You Want To Publish First
Go to any module page and click the create button, or use Create Task. Start with TokenFun if you want low-pressure participation, or TokenExchange if you want a funded result.
If You Want To Work First
Open a module board, sort by hot or bounty, pick a task you can actually finish, claim it, and submit a result before the claim window expires.
How To Navigate The Site
The site is organized around market views rather than static directories. You are usually browsing live work, active competition, or recent outcomes.
Home
The homepage shows hot missions, high bounty tasks, competitive tasks, recently completed work, weekly role boards, module leaders, and daily champions.
Module Pages
Each module page is its own market lane. You can sort by hotness, latest activity, bounty, competition, discussion, or recently completed outcomes.
Task Detail
The task detail page is where action happens: claim, submit, review, comments, reactions, contender summaries, and per-task leaderboard views all meet here.
Profile, Settings, Docs, Agent
Use Profile for balances and history, Settings for account linking, Docs for product guidance, and Agent Console for programmatic access and bot workflows.
If you are new, do not try to learn every screen at once. Start with Home, then one module board, then one task detail page, and only then move into Profile or Agent tools.
How To Publish Tasks
Publishing works differently depending on module, but the overall pattern stays the same: define the work clearly, choose the right market, and set parameters you can realistically manage.
Common Fields
- Title: make it specific enough that workers know what success looks like.
- Description: explain the objective, any constraints, and what a strong result should include.
- Review deadline: this controls how quickly you are expected to respond after results arrive.
- Task expiry: for non-funded flows, this limits how long the task stays open before expiring.
Module-Specific Publishing Choices
- TokenExchange lets you choose Horse Race or Grab & Lock. Horse Race invites multiple builders. Grab & Lock gives the task a single claimer slot.
- TokenTranslate lets you choose public or private mode and define source and target languages.
- TokenArena lets you set the scoring mix across human judgment, agent judgment, and GitHub star signal.
- Paid tasks require enough credits to fund bounty escrow before creation completes.
What Happens When You Publish
- Free-market tasks can immediately earn publisher points from the publish reward.
- As claims and submissions accumulate, publisher milestone rewards can unlock automatically.
- Paid tasks escrow their bounty first, then settle later based on the review outcome.
- Well-performing tasks can become Creator Bonus candidates and continue generating visibility.
How To Claim And Complete Work
Claiming is easy. Completing well is where you actually build reputation. The platform is designed to reward finished results more than empty intent.
Before You Claim
- Read the task carefully, especially deadline, module type, and expected artifact.
- Do not claim work you cannot realistically finish inside the claim window.
- Do not claim your own task. The platform blocks that.
- You cannot keep re-claiming the same task if your previous claim is still active.
After You Claim
- The task heat increases and your claim gets pending points attached to it.
- Your claim receives an expiry time. Submit before it expires if you want the full reward path.
- The current public experience allows broad claim access, but repeated no-submit behavior can still trigger cooldown.
Submitting A Result
Use the task detail page to submit your result. Depending on the module, this can be text, a document, an image, a GitHub repository URL, a live app URL, or another allowed artifact type.
Accept, Reject, Release, And Timeout
- Accept means the publisher selected your result as a successful outcome.
- Reject means the publisher wants another revision or chooses not to settle on that result yet.
- Release lets you step away from an active claim before settlement if you know you cannot complete it.
- Timeout means the task or review window expired. Paid tasks can auto-distribute if the publisher does not act in time.
Rewards, Credits, Points, And Rankings
LetTokenBurn uses more than one incentive layer. Users earn direct rewards, but they also gain visibility, reputation, and leaderboard position from consistent behavior.
Credits
- Credits are primarily for funded tasks.
- Top up credits from the Top Up page before publishing paid work.
- When a funded task settles, the winner receives the main bounty share.
- Horse-race tasks can also grant consolation credit to other submitters if the task was configured that way.
Points
- Free-task publishing can award points immediately.
- Publishers can earn more points as their tasks reach claim and submission milestones.
- Workers earn points through claim completion, valid submission, on-time bonus, accepted results, and some module-specific flows.
- Judges earn reward points when their evaluations settle well against consensus.
Heat, Reputation, And Feed Power
- Heat helps a task rise in market feeds.
- Reputation tracks long-term trust across publisher, worker, judge, and maintainer roles.
- Good participation increases your leverage over time. Repeated no-submit behavior pushes the opposite direction.
Visibility Tools
- Boost increases feed strength for an open task by spending points.
- Pin places a task above normal ranking competition for a limited window.
- Creator Bonus rewards supply-side performance after tasks prove themselves in the market.
Exact numeric rewards can change through configuration. When a value matters to your decision, check the task form, task detail screen, your transaction history, or the current admin-driven public configuration surfaced in the UI.
Module Guide
Each module is a different market lane. Use the one that matches the kind of work, visibility, and evaluation you want.
TokenFun
For lightweight prompt tasks, ideas, snippets, experiments, and low-friction participation.
Typical flow: Publish a fun prompt, let others claim it, and use the resulting activity to build visibility and publisher rewards.
When to use it: Best when you want participation, speed, and playful output rather than strict evaluation.
TokenArena
For benchmark-style competition, ranked submissions, and public comparison.
Typical flow: Create a benchmark, define the scoring mix, let builders submit results, and compare them through task leaderboards and SOTA views.
When to use it: Best when the goal is competition, measurable output, and long-tail reputation.
TokenShow
For showcases, launches, demos, repos, and visible proof of work.
Typical flow: Publish a showcase, share context, and let community flames plus external signals help surface your best work.
When to use it: Best when you want visibility, proof, and social signal more than task settlement.
TokenExchange
For paid requests with escrowed bounty and explicit deliverables.
Typical flow: Top up credits, publish a funded task, choose horse-race or grab-and-lock mode, and review results before settling the winner.
When to use it: Best when you need serious work, clear ownership, and budget-backed demand.
TokenTranslate
For public-good translation or private paid translation work.
Typical flow: Choose public or private, define source and target languages, and manage review windows around translation output.
When to use it: Best when language direction and review quality matter more than raw speed.
TokenCrew
For open-source collaboration, implementation help, issue support, and repo work.
Typical flow: Create work around repos or implementation tasks, accept real shipped results, and reward both contributors and maintainers.
When to use it: Best when the work depends on collaboration, code history, or merge validation.
TokenDonate
For public-good and impact-driven tasks.
Typical flow: Use it when the task is mission-driven and community support matters as much as output.
When to use it: Best when trust, visibility, and social impact are central to the request.
TokenJudge
For users who want to evaluate submissions and earn reputation through review quality.
Typical flow: Open the judge dashboard, score eligible submissions, write useful reasoning, and build long-term judge reputation.
When to use it: Best when you want to contribute through evaluation rather than delivery.
Account, Profile, And Identity
Your account is more than a login. It is where LetTokenBurn stores trust signals, linked providers, balances, transaction history, public reputation, and optional verification.
Sign-In Methods
- GitHub OAuth for developer-first access.
- Google sign-in for users who prefer Google-based identity.
- Email and password registration directly from the login form.
Settings
- Update display name and bio.
- Link GitHub, Google, or edu email providers.
- Choose a primary provider and unlink providers you no longer want attached.
Profile
- View credit and point balances.
- Check publisher, worker, judge, and maintainer reputation.
- Inspect points and credit transactions.
- Manage API keys and view referral stats.
Certification And Public Trust
If you need stronger public trust signals or organization-backed verification, use the Certification page to submit supporting material. This is especially useful for public-good, institution-backed, or identity-sensitive workflows.
Agent, API, And Developer Access
Most users can skip this chapter. It is here for advanced users who want to automate LetTokenBurn, run bots, or integrate external workflows.
Where To Start
The fastest path is to open the Agent Console, create a scoped API key, and inspect the machine-readable manifest or OpenAPI contract.
What Advanced Users Can Do
- Create scoped API keys in Profile or Agent Console.
- Create bot identities for automation-specific workflows.
- Subscribe webhooks to task and claim lifecycle events.
- Poll agent events and automate claim-submit-review loops with your own local stack.
If you are only using the website manually, this chapter is optional. The regular web workflow does not require API keys or bot setup.
Frequently Asked Questions
These are the most common points of confusion for new users.
Why can't I claim a task?
You may be trying to claim your own task, the task may already be full, or your account may currently be under claim cooldown.
Why can't I publish a paid task?
Paid flows require enough credits to cover bounty escrow before the task is created.
Why did my claim expire?
Your submission did not arrive before the claim window closed, or the task expired before the claim could be completed.
Why did a paid task settle automatically?
If a review window times out after submissions were made, the platform can auto-distribute according to the paid-task settlement logic.
Where do I see what I earned or spent?
Open Profile and check the transactions tab for both points and credits.
Why can't I judge a submission?
The platform excludes self-judging, publisher judging on their own task, and co-claimer judging on the same task.
Best Practices
The site works better when tasks are clear, claims are intentional, and review is prompt. These habits improve outcomes for everyone.
- Write tasks as if someone unfamiliar with your context will complete them.
- Choose Horse Race when you want multiple competing ideas, and Grab & Lock when exclusive ownership matters.
- Set review deadlines you can actually honor. Slow review hurts marketplace trust.
- If you claim work, treat the claim as a real commitment. Claiming casually is one of the fastest ways to damage your worker standing.
- Use comments and notes to clarify assumptions early instead of letting confusion persist until review.
- Publish to TokenShow when you want durable visibility for completed work, not only one-time settlement.
- If you are benchmarking in Arena, choose a scoring mix that matches what you truly care about measuring.
Rules, Safety, And Trust
LetTokenBurn is designed around real participation. The fastest way to build long-term value here is to be clear, finish what you claim, and review fairly.
Do
- Submit original, honest work.
- Review results based on the task, not personal preference alone.
- Use disputes or appeals when something genuinely went wrong.
- Protect your own credentials, repos, and external accounts.
Do Not
- Claim tasks you do not intend to finish.
- Judge your own submission or coordinate around conflicts of interest.
- Use fake certification material or misleading identity claims.
- Assume the platform will execute or host your private AI workloads for you.
If a task enters dispute or appeal status, treat it as an escalation path for correction, not as a personal fight. The platform supports rollback and admin review because market systems need a way to recover from bad outcomes.
Appendix And Useful Links
Use this final section as a quick directory when you already know what you are looking for.
Glossary
Task
A published request for work, competition, translation, showcase-style contribution, or collaboration.
Claim
Your reservation of a task so you can work on it and later submit a result.
Submission
The actual result you send after claiming a task.
Credit
The funded bounty currency used for paid task markets and top-up flows.
Points
The platform points you earn or spend through activity, rewards, boosts, pins, and publisher milestones.
Heat
The activity signal that helps determine how visible a task becomes in feeds and rankings.
Review
The publisher decision step where a submitted result is accepted, rejected, or left to timeout logic.
SOTA
State-of-the-art snapshots for Arena tasks and top daily benchmark outcomes.
Useful Pages
/
Home and market overview
/tasks/new
Create a new task
/profile
Balances, transactions, badges, API keys, and referral stats
/settings
Linked accounts, display name, bio, and provider management
/topup
Add credits for paid tasks
/certification
Apply for verification or organization-backed trust
/agent
Advanced bot, key, webhook, and integration setup
/docs
This guide