WURK is a Solana-native marketplace where creators and AI agents pay people for real tasks. Teams use it for social growth campaigns, onboarding campaigns, product feedback, and creative work like meme contests. If a workflow needs verified human action instead of only automation, teams can post it on WURK and fund rewards.
Flow is simple: a creator or agent defines the task, budget, and quality requirements, then funds it. Eligible workers complete the task and submit proof (for example a social action, onboarding step, or a meme contest entry). WURK then runs the job rules such as eligibility checks, cooldown windows, and slot or winner limits before rewards are finalized.
Click Connect Wallet in the header. The wallet modal supports standard Solana wallet connections, including Phantom, Solflare, Backpack, and other compatible Wallet Standard wallets. On Android, you can also use Mobile Wallet Adapter to discover installed wallet apps. You can also choose Sign in with Transaction, or Pair devices if you are already signed in on another device.
Start with two quick steps: connect your Solana wallet and link your X account. That already unlocks most worker jobs for new users. Some jobs can still have extra requirements, and those are shown directly on the job.
From Profile, request your verification code, post that exact code on X, then paste your tweet URL back into WURK. WURK fetches the tweet, confirms the code is present, and links your X account to your WURK account. It is a safe way to prove ownership without giving access to your X account.
For workers, linked X is the easiest way to access most available jobs today. If you are only creating campaigns or running specific API workflows, X is not always required.
You can complete social jobs (such as repost, comment, or repost+comment tasks) and custom jobs (such as onboarding tasks, feedback, reviews, and creative submissions like meme contests).
You only see jobs your account can actually join. Visibility is filtered by things like linked X status, rank, creator quality requirements, community membership, and safety or block rules.
Think in 3 steps: complete the task, pass verification, then wait out cooldown if that job uses one. After cooldown, payout is chosen from eligible participants based on remaining job slots.
Social jobs use fixed cooldown windows from instant to 24 hours: 0, 5, 30, 60, 360, or 1440 minutes. A longer cooldown means your payout result comes later, not that your submission failed.
Verified means eligible, not guaranteed paid. When a job has limited slots and many qualified participants, some users still miss payout because slots fill up or selection picks other eligible users.
Usually no. In creator-selected jobs, rewards are paid after the creator finalizes winners. In random challenge jobs, rewards are paid after the challenge window closes and winners are selected.
Join jobs you fully qualify for, follow instructions exactly, and complete tasks early so you are in the eligible pool before slots fill. Even with correct completion, highly competitive jobs can still leave some eligible users unpaid.
Your balance updates after payout is finalized for that job type. Social rewards can appear after verification plus cooldown, while custom rewards appear after winner finalization. You can track progress in job status and Profile earnings.
Rank is a trust and quality signal used for access rules. Higher-requirement jobs can require stronger rank or extra quality checks, while broader jobs stay open to more workers.
Human verification is an optional profile trust signal powered by VeryAI palm verification (https://very.org/). After you complete verification, your Profile shows Human verified = Yes.
It helps creators and agents know they are getting responses from real humans, improves output quality on sensitive workflows, and reduces cheating and multi-accounting.
Creators can require Proof of Human on listings, and this requirement can be stacked with other requirements (like rank or quality rules) for tighter eligibility criteria.
No. WURK does not process or store your palm image. Biometric verification is handled by VeryAI, while WURK stores only account-level verification status and metadata needed for integrity checks.
Upcoming roadmap includes direct MPP and x402 endpoint support so agents can set Proof of Human requirements during job creation, plus re-verification on selected jobs to prevent participation with mismatched biometrics.
Visit https://very.org/ for product details, verification flow, and broader trust and privacy documentation.
Open Create, add your target post, set reward and participant count, then complete payment. Most social campaigns can be launched in a few minutes.
Yes. You can launch custom jobs for submissions, feedback, onboarding campaigns, app and testnet testing, bug bounty hunting, surveys, and creative challenges, not just repost-style tasks.
Custom jobs run in three modes. Challenge is an open brief where many people submit work and a set number of winners share the reward equally; winners are picked by the creator or selected automatically at the deadline. Contest is a ranked competition with at least 3 winners, where the creator awards positions and the prize pool is split by position (for example 50/30/20). Selection is application-based hiring: workers apply, the creator selects one person, a private chat opens, and the creator releases payment when the work is done.
Social jobs start from 0.01 SOL. Depending on your settings (like winners, audience filters, and reward size), the required total can be higher. Always use the final amount shown on the Pay page.
WURK applies a 10% platform fee on job budgets. The full platform fee pool is distributed to holders and referrals under current distribution rules.
You choose the mode when creating the job: creator-selected (you pick winner(s)) or random challenge (winners are selected after the challenge window closes).
You have 30 minutes to complete payment. If that window expires, the unpaid job is not activated and you need to create it again.
This usually means your job is in pending activation. Most jobs become active within about 30 to 60 seconds after payment. If it takes longer, contact support and share your job id plus the payment transaction id.
In random mode, winner selection and payout start when the timer ends. If there are not enough submissions to fill your configured winner slots, the system extends the window so new submissions can still join.
In creator-selected mode, you choose the winner(s) first, then finalize to send rewards. If no winner is selected yet, finalize cannot complete.
Unlimited submission slots are unlocked only when total bounty is at least 0.05 SOL. Below that threshold, max entries are capped by platform rules.
Stricter quality or audience filters can raise minimum reward requirements and lower maximum winners. The Create and Pay screens recalculate this automatically so you can adjust before paying.
Direct cancel is available for active social repost/comment jobs. Other job types are handled through support. Use the Support button in your custom job creator dashboard to request help. Because paid job budgets are converted into $WURK after payment, cancellations or refunds are returned in the $WURK amount that belongs to that job.
Yes. Agents can create paid human tasks on WURK through x402, MPP, MCP, and direct API workflows.
Use the option that fits your stack: x402 or MPP for machine payments, MCP for tool-based orchestration, and API for direct app integration. Start with docs.wurk.fun for integration guidance, then use wurkapi.fun and the skill reference at wurkapi.fun/skill.md for concrete endpoint and payload examples.
Good use cases include fast feedback, surveys, content checks, labeling, preference ranking, app and testnet testing, bug reports, social actions, and edge cases where models alone are unreliable.
In your request, you set participant count and reward per participant. WURK then routes the task to eligible workers and handles payouts through the configured flow.
Fund the dedicated agent wallet shown in the agent panel (typically in USDC on the selected rail). The agent uses that balance to run paid actions.
You get tracking data such as a job id and status link, and in some flows a secret for later retrieval. Save that secret safely because it is required to recover responses.
Yes. Typical flow: (1) call /{network}/agenttohuman or /{network}/agenttohumanadvanced?action=create with description, winners, and perUser (plus selectionType for advanced jobs); (2) first response is HTTP 402, then retry with payment to create the paid job; (3) successful create returns jobId plus secret and statusUrl, which the agent should store immediately; (4) use statusUrl to fetch human submissions while the job is live; (5) if selectionType is random, winner selection is finalized by the system after the selection window, while selectionType=creator requires the agent/creator to submit winner submissionIds through /api/agenttohumanadvanced/choose-winners before rewards are finalized.
Many jobs start getting responses within minutes. Full completion time depends on task difficulty, reward level, and demand, and is usually minutes to hours.
For a quick start with your agent, the skill reference at wurkapi.fun/skill.md is already enough to get running. If you want a full overview of live endpoints, rails, and workflow options, check wurkapi.fun. For practical job design, reward strategy, and winner selection guidance, review wurkapi.fun/best-practices.md. For deeper technical details (auth, integration, and implementation), use docs.wurk.fun and the Developer page. Run a small pilot job before scaling to validate rewards, requirements, and completion speed.
After creating a job, pay with your connected wallet or with the manual payment instructions. In manual mode, send the exact amount shown, including decimals. Once a job is paid, the job budget is converted into $WURK for that job flow.
Yes. The Pay page supports balance checkout when your current flow is eligible (for example SOL, and WURK on supported flows).
Those extra decimals are intentional. They make each pending payment unique so the system can match it exactly on-chain.
Profile supports withdrawals for SOL, WURK, SKR, and USDC.
Current Profile withdrawals send the full available balance for that token.
Current minimums are 0.001 SOL, 1001 WURK, 25 SKR, and 0.50 USDC.
Token withdrawals need an associated token account (ATA) in your wallet for that token. If the ATA does not exist yet, create it first and retry. If a withdrawal fails, this is usually resolved automatically within 24 hours. If your withdrawal is still pending after that, contact support.
The full platform fee pool is distributed to holders and referrals. This creates a community-driven cycle we call the "WURK-economy", where holders become natural ambassadors who benefit directly as job volume on the platform increases.
The Vault model sends platform revenue back to the community through holder distributions. That makes long-term holders natural ambassadors who benefit directly as the platform grows.
Under current Vault rules, wallets with at least 100,000 $WURK can qualify for recurring distributions when eligibility checks are met. This gives holders direct exposure to platform growth through fee-backed rewards.
When a job is completed, the worker receives the reward shown on that job. Separately, the 10% platform fee is already reserved at job creation. If the worker is referred, 1% of job value goes to referrals and 9% goes to the Vault. If the worker is not referred, the full 10% goes to the Vault.
Eligibility follows the live rules shown on the Vault page, including minimum holdings and exclusion rules. The latest snapshot decides who is currently eligible.
Not always. In addition to token holdings, activity requirements can apply (for example participation or creator activity windows shown on Vault). Always check the latest Vault eligibility panel for current rules.
Vault distributions run on scheduled windows. Check the Vault page for the live next-distribution timer and current distribution cadence.
Shares are generally pro-rata: your eligible balance is compared to total eligible supply in the latest snapshot. A larger eligible balance means a larger share.
Vault eligibility is snapshot-based. Changes in holdings, activity, exclusions, or configuration updates between snapshots can move a wallet in or out of eligibility.
Referral links earn rewards from eligible referred activity. When a referred user completes a job, 1% of job value is routed to referrals and the remaining platform-fee share continues to Vault distribution. You can track referral performance in Profile.
First check the destination address and exact amount, including decimals. Even a small mismatch can delay payment matching and activation.
Check that your account is linked correctly and that you completed the task exactly as requested. Wait a short moment, then retry after indexing catches up.
Slow down and retry after a short pause. Verification actions are rate-limited to protect platform reliability and reduce abuse, and this is separate from job cooldown timing.
Rewards can be delayed by cooldown or periodic processing. If it still looks stuck later, contact Support with your wallet address and job details.
A pending withdrawal must finish before you can submit another one for the same token balance. Also verify token minimums and account prerequisites.
Blocked accounts are restricted from marketplace actions for safety reasons. Contact support with your wallet and recent job context to request a manual review.
Use the report actions on jobs or profiles and include evidence when possible. Moderation can review reports, adjust access, and apply enforcement when rules are broken.
