What to do:
Test whether developers can quickly understand Kielo's unified API for accessing 100+ open-source LLMs and locate the API documentation needed to make their first request.
Navigate to https://kielo.in/ and locate the primary call-to-action for API access without signing in or joining waitlist
Identify and read the curl example showing the API endpoint structure and required authorization header format
Find and click through to view the list of 100+ available models mentioned on the homepage
Locate the 'Models' navigation link and verify it displays supported model names like llama-3.3-70b, Mistral, and DeepSeek
Assess whether the homepage clearly explains the difference between the GPU earning feature and the LLM API access feature
Evidence: Record screen navigation from homepage through API documentation discovery. Write findings on: (1) clarity of API value proposition vs. GPU earning, (2) ease of locating model list and curl example, (3) missing or unclear information blocking first API call attempt.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
Send video evidence for every issue in the accepted tester chat.
Record your screen and microphone audio for the full test. Narrate your actions, every error you find, and anything confusing, poor, or worth improving.
Attach the narrated video as an MP4, MOV, or WebM no larger than 75 MB, plus at least one representative screenshot.
For each issue include a short title, a severity (critical/high/medium/low), and exact steps to reproduce.
Submissions are reviewed automatically. $4.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://kielo.in/
Test whether developers can quickly understand Kielo's unified API for accessing 100+ open-source LLMs and locate the API documentation needed to make their first request.
1. Navigate to https://kielo.in/ and locate the primary call-to-action for API access without signing in or joining waitlist
2. Identify and read the curl example showing the API endpoint structure and required authorization header format
3. Find and click through to view the list of 100+ available models mentioned on the homepage
4. Locate the 'Models' navigation link and verify it displays supported model names like llama-3.3-70b, Mistral, and DeepSeek
5. Assess whether the homepage clearly explains the difference between the GPU earning feature and the LLM API access feature
Evidence: Record screen navigation from homepage through API documentation discovery. Write findings on: (1) clarity of API value proposition vs. GPU earning, (2) ease of locating model list and curl example, (3) missing or unclear information blocking first API call attempt.
Keep the test to five minutes. Do not sign in, enter private credentials, complete a purchase, or make destructive changes.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
1Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
2Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
3Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
4Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 75 MB with spoken microphone narration throughout, plus at least one representative screenshot. Captions, written narration, and on-screen text do not replace the required microphone audio.
5Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
6Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
7Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
•
Access to a device that can open the target URL
•
Report every issue with a severity and exact reproduction steps
•
Only submit evidence you captured yourself during this run