<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Notatki z 50heads</title>
    <link>https://50heads.com/pl/blog</link>
    <description>O dobrym pytaniu, uczciwym odpowiadaniu i uczciwym płaceniu ludziom.</description>
    <language>pl</language>
    <lastBuildDate>Tue, 22 Sep 2026 09:00:00 GMT</lastBuildDate>
    <atom:link href="https://50heads.com/pl/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Moving from MTurk to 50heads</title>
      <link>https://50heads.com/pl/blog/moving-from-mturk</link>
      <guid isPermaLink="true">https://50heads.com/pl/blog/moving-from-mturk</guid>
      <pubDate>Tue, 22 Sep 2026 09:00:00 GMT</pubDate>
      <description>What changes when you move quick human judgments from Mechanical Turk to 50heads, what stays the same, and how to do it in an afternoon.</description>
      <dc:creator>Peter Chapman</dc:creator>
      <category>guides</category>
      <category>requesters</category>
      <category>mturk</category>
      <content:encoded><![CDATA[<p>Mechanical Turk has been the default place to get a quick human answer for nearly twenty years. It is flexible, cheap at the bottom end and familiar. It is also, for the kind of question we care about, hard work: you design a HIT, set qualifications, guess a fair reward, wait, then clean the data because a share of it came from scripts, farms or people clicking through.</p>
<p>50heads does one narrower thing. You ask one short question with a few options, and fifty verified people answer it on their phones in about ten minutes. If that is most of what you used MTurk for, this guide is for you.</p>
<h2 id="what-maps-to-what">What maps to what</h2>
<div class="table-wrap" tabindex="0"><table>
<thead>
<tr>
<th>On MTurk</th>
<th>On 50heads</th>
</tr>
</thead>
<tbody><tr>
<td>A HIT with one question</td>
<td>A question</td>
</tr>
<tr>
<td>Assignments per HIT</td>
<td>Heads (10 to 5,000 on the web)</td>
</tr>
<tr>
<td>Workers</td>
<td>Heads</td>
</tr>
<tr>
<td>Qualifications and Masters</td>
<td>Tiers: phone-verified, ID-verified, trusted panel</td>
</tr>
<tr>
<td>Reward plus 20–40% fee</td>
<td>One price per answer, fee included, shown before you ask</td>
</tr>
<tr>
<td>Approve or reject each assignment</td>
<td>Nothing to review: checks happen before an answer counts</td>
</tr>
<tr>
<td>Your own results page</td>
<td>A split, a winner and a confidence line</td>
</tr>
</tbody></table></div>
<h2 id="the-price-side-by-side">The price, side by side</h2>
<p>On MTurk you set the reward and Amazon adds its commission: 20%, rising to 40% on HITs with ten or more assignments. A fifty-assignment HIT at $0.10 a response costs $7.00 before you have thrown anything away.</p>
<p>On 50heads a Tier 1 answer is €0.24, and fifty of them cost €11.80. The price covers verification, the head&#39;s pay and our margin. Heads get 60% of it. You see the total and the time before you post, and if fewer heads answer than you asked for, the rest goes straight back to your balance.</p>
<h2 id="what-you-stop-doing">What you stop doing</h2>
<p><strong>Screening for bots.</strong> Every answer on 50heads is signed by the secure hardware in the phone that gave it. Emulators and modified apps can&#39;t answer at all. Tier 1 heads have one real phone number each; Tier 2 heads have passed an ID and live-face check. You don&#39;t need attention checks, and you shouldn&#39;t add them: they make the question longer, and longer questions cost more.</p>
<p><strong>Approving and rejecting.</strong> We run known-answer questions and timing checks on our side. If an answer is thrown out after it counted, you get the credit back automatically.</p>
<p><strong>Writing reward math.</strong> The price is worked out from the tier, how long the question is to read and the kind of answer. The estimate is free and never spends anything.</p>
<h2 id="what-you-need-to-change">What you need to change</h2>
<p>Most MTurk HITs that fit 50heads are one of four shapes:</p>
<ol>
<li><strong>Pick one of several.</strong> Names, headlines, thumbnails. This is the default question type.</li>
<li><strong>A or B with images.</strong> Two pictures, one tap.</li>
<li><strong>A 1–5 rating.</strong> Use sparingly; a choice usually tells you more.</li>
<li><strong>A short free-text reason.</strong> Available from Tier 2, up to 200 characters.</li>
</ol>
<p>Longer tasks (transcription, tagging hundreds of items, multi-page surveys) don&#39;t fit. Keep MTurk or a research panel for those.</p>
<p>Keep questions short. Heads answer in about five seconds, on a phone, between other things. If your HIT has a paragraph of instructions, the question isn&#39;t ready yet. Our guide to <a href="https://50heads.com/pl/help/asking/writing-good-questions">writing questions that get clear answers</a> covers the rules we use ourselves.</p>
<h2 id="doing-it-in-an-afternoon">Doing it in an afternoon</h2>
<ol>
<li><a href="https://50heads.com/app">Sign in</a> and add credits. Packs start at €24.</li>
<li>Take your most common HIT and rewrite it as one question with two to eight options. Run it through the <a href="https://50heads.com/pl/pricing">estimator</a> to see the price and the time.</li>
<li>Ask it to fifty Tier 1 heads and compare the result with your last MTurk batch.</li>
<li>If you call MTurk from code, swap the call for the 50heads API or add the MCP server to your agent. There is a <a href="https://50heads.com/pl/docs">quick start</a> with curl, TypeScript and Python.</li>
</ol>
<pre class="code" data-copy><code class="language-sh">curl https://api.50heads.com/v1/billing/estimate \
  -H &quot;Content-Type: application/json&quot; \
  -d '{&quot;draft&quot;:{&quot;type&quot;:&quot;single_choice&quot;,&quot;text&quot;:&quot;Which name would you trust with your savings?&quot;,&quot;options&quot;:[{&quot;label&quot;:&quot;Northway&quot;},{&quot;label&quot;:&quot;Keel&quot;}],&quot;n&quot;:50,&quot;tier&quot;:1}}'</code></pre>
<h2 id="when-mturk-is-still-the-better-tool">When MTurk is still the better tool</h2>
<p>If you need someone to do work rather than give a judgment, or you need hundreds of steps from the same person, or you are running an academic study with its own consent flow, a general-purpose marketplace or a research panel will serve you better. We would rather tell you that now than have you find out halfway through.</p>
<p>For everything that is really one question with an answer you&#39;ll act on this afternoon, fifty heads are better than one.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How we know every answer comes from a person</title>
      <link>https://50heads.com/pl/blog/how-we-verify</link>
      <guid isPermaLink="true">https://50heads.com/pl/blog/how-we-verify</guid>
      <pubDate>Sun, 20 Sep 2026 09:00:00 GMT</pubDate>
      <description>Device attestation, one phone per head, ID checks at Tier 2 and the checks that keep running afterwards. What we do, what we keep, and why we publish it.</description>
      <dc:creator>Peter Chapman</dc:creator>
      <category>trust</category>
      <category>verification</category>
      <category>heads</category>
      <content:encoded><![CDATA[<p>Every panel says its answers come from real people. Almost none say how they know. We think that should be the first thing you ask, so here is the whole answer.</p>
<h2 id="the-problem-we-are-solving">The problem we are solving</h2>
<p>Paying strangers for opinions attracts three kinds of cheating. Scripts that answer at machine speed. Farms of phones run by one person. And people who are real but not paying attention. Each one needs a different check, and the checks only work if they are hard to fake cheaply.</p>
<h2 id="check-one-the-phone-is-a-real-phone">Check one: the phone is a real phone</h2>
<p>Every modern iPhone and Android phone has a small sealed chip that can sign a message in a way software can&#39;t imitate. When a head answers, the 50heads app asks that chip to vouch for three things:</p>
<ul>
<li>this is a real, physical device, not an emulator;</li>
<li>it hasn&#39;t been rooted, jailbroken or tampered with;</li>
<li>the app sending the answer is the one we published, unmodified.</li>
</ul>
<p>Apple or Google checks the signature and tells us whether to believe it. If it doesn&#39;t check out, the answer never reaches you and the head isn&#39;t paid. This is why a script on a server can&#39;t answer 50heads questions at all, however clever it is.</p>
<p>Each answer in your results carries an attestation reference. It proves the answer came from a checked device without saying whose.</p>
<h2 id="check-two-one-real-phone-number-per-head">Check two: one real phone number per head</h2>
<p>To be paid, a head verifies a phone number with a code by text or WhatsApp. Virtual numbers and VoIP numbers are refused. A number can belong to one account only.</p>
<p>Numbers are cheap in some places, so we don&#39;t stop there. Every month, a Tier 1 head who earned in that month confirms the same number again. It takes ten seconds for someone who still has their phone; it is expensive for a farm that rotates SIM cards.</p>
<h2 id="check-three-a-real-identity-at-tier-2">Check three: a real identity, at Tier 2</h2>
<p>Heads who want the higher-paying Tier 2 questions pass an ID and live-face check, once. It is run by a specialist provider, not by us. The provider checks the document, checks that the face in front of the camera matches it and is live, and checks the face against every other account so one person can&#39;t hold two.</p>
<p>We receive a yes or a no. The ID and face photos are deleted by the provider after its decision, within 30 days. We never see them. Tier 2 heads also get a three-second face check at random afterwards, so an account can&#39;t be verified once and then handed on.</p>
<h2 id="check-four-attention">Check four: attention</h2>
<p>A verified person can still click without reading. So a few questions each day have answers we already know. Heads who get too many of them wrong stop seeing paid questions. We also hold back answers that arrive faster than the question could have been read, or in lockstep with other accounts, and review them.</p>
<h2 id="what-happens-when-we-get-it-wrong">What happens when we get it wrong</h2>
<p>Automated checks make mistakes, and the people on the other end of them deserve a way out. Any head can appeal once a month, a person reads every appeal, and we publish how many we receive and uphold each quarter in our <a href="https://50heads.com/pl/transparency">transparency note</a>.</p>
<p>If we remove an answer after it has counted towards your result, you get the credit back and the result is recalculated.</p>
<h2 id="what-we-keep">What we keep</h2>
<p>We keep as little as the checks need, for as long as they need it:</p>
<div class="table-wrap" tabindex="0"><table>
<thead>
<tr>
<th>What</th>
<th>How long</th>
</tr>
</thead>
<tbody><tr>
<td>ID and face photos</td>
<td>Not kept by us; the provider deletes them within 30 days</td>
</tr>
<tr>
<td>Face match for duplicate accounts</td>
<td>With the provider while the account exists</td>
</tr>
<tr>
<td>Phone number</td>
<td>While the account exists, plus a scrambled copy for 12 months</td>
</tr>
<tr>
<td>Touch and timing signals</td>
<td>90 days; summary patterns for up to 24 months</td>
</tr>
<tr>
<td>Answers</td>
<td>Never shown with a name</td>
</tr>
</tbody></table></div>
<p>The full detail is in our <a href="https://50heads.com/pl/legal/privacy">privacy notice</a> and on <a href="https://50heads.com/pl/verification">how we verify</a>.</p>
<h2 id="why-publish-it">Why publish it</h2>
<p>Because &quot;trust us&quot; is not a verification method. If you can read how the checks work, you can decide whether they are good enough for your question, and you can hold us to them.</p>
]]></content:encoded>
    </item>
    <item>
      <title>What heads earn, and why we publish it</title>
      <link>https://50heads.com/pl/blog/what-heads-earn</link>
      <guid isPermaLink="true">https://50heads.com/pl/blog/what-heads-earn</guid>
      <pubDate>Fri, 18 Sep 2026 09:00:00 GMT</pubDate>
      <description>Our pay rates, the share of every answer that goes to the head, how payouts work, and the honest line about what answering questions is and isn&apos;t.</description>
      <dc:creator>Peter Chapman</dc:creator>
      <category>heads</category>
      <category>pay</category>
      <category>earn</category>
      <content:encoded><![CDATA[<p>Most platforms that pay people for small pieces of work keep the numbers vague. We would rather you could check our sums. This post sets out what a question pays, where the money goes, and what you should and shouldn&#39;t expect.</p>
<h2 id="the-short-version">The short version</h2>
<ul>
<li>A Tier 1 answer pays €0.14. A Tier 2 answer pays €0.30, about 2.1 times as much. Tier 3 pays €0.57.</li>
<li>Heads get 60% of every answer&#39;s price. The rest pays for verification, the platform and the company.</li>
<li>You see what a question pays before you answer it.</li>
<li>New earnings clear in up to 7 days (3 at Tier 3). After that you can withdraw from €6, or let us pay you automatically at the end of the month.</li>
</ul>
<h2 id="where-the-money-goes">Where the money goes</h2>
<p>A requester pays €0.24 for a Tier 1 answer. Of that, €0.14 goes to the head who gave it. The remainder covers the device and phone checks on every answer, the ID provider for Tier 2, payment fees, the servers, support, and the people who build and run 50heads.</p>
<p>We picked a fixed share because it is easy to check: if a requester pays more for a question (a longer one, or one with images, or a rush), the head gets more too, in proportion.</p>
<h2 id="pay-is-the-same-everywhere">Pay is the same everywhere</h2>
<p>We pay the same rate in every country we pay, before currency conversion. We looked hard at adjusting pay by country and decided against it. The work is the same, and a five-second answer from Manila is worth as much to a requester as one from Manchester. The <a href="https://50heads.com/pl/earn/rates">pay rates by country</a> page shows the rates in local currency, the payout methods in each country and the smallest withdrawal.</p>
<h2 id="getting-paid">Getting paid</h2>
<p>Heads can withdraw to PayPal, a UK bank account or Wise, depending on the country. The first withdrawal each month is free. The Withdraw screen shows exactly what will arrive, after any fees and currency conversion, before you confirm.</p>
<p>Why the holding period? Because some checks can only run after the fact: known-answer questions, timing patterns across many answers, and requester disputes. Holding new earnings for up to a week lets us catch fraud without clawing money back from people who did nothing wrong.</p>
<h2 id="the-honest-line">The honest line</h2>
<p>Answering questions on 50heads is not a full-time income, and we won&#39;t pretend it is. It is five-second questions in spare minutes: on the bus, in a queue, while the kettle boils. How much you earn depends mostly on how many questions there are in your language at the time, and we tell you when there&#39;s nothing waiting rather than filling the gap with unpaid busywork.</p>
<p>What we can promise is that every accepted answer pays what it said it would, that the rates are public, and that you can always see what is pending and what is ready to withdraw.</p>
<h2 id="what-we-publish-and-when">What we publish, and when</h2>
<p>Our <a href="https://50heads.com/pl/earn/fair-pay">fair pay statement</a> sets out the floor we won&#39;t go below and how we&#39;ll tell heads before any rate changes. Our <a href="https://50heads.com/pl/transparency">transparency note</a> reports appeals received and upheld each quarter.</p>
<p>If you think a rate is wrong, or a payout didn&#39;t arrive, <a href="https://50heads.com/pl/contact">tell us</a>. A person will reply.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
