What to do:
Evaluate whether startup founders can understand Agent 37's API-first agent deployment model and locate pricing for creating agents via the /v1/instances endpoint.
Navigate to the homepage and identify the two deployment methods (one-click vs API) presented in section [01]
Locate and read the API code example showing POST /v1/instances with the agent37-hermes template
Find the pricing section and identify the per-agent per-month cost listed for API-based deployments
Click 'See all integrations' and verify at least three integration categories (Gmail, Slack, GitHub) are displayed
Attempt to access the Pricing page from the main navigation and confirm pricing tiers for both deployment methods are visible
Evidence: Record screen navigation from homepage through pricing and integrations sections. Document: (1) whether API deployment model was clearly distinguished from one-click, (2) pricing visibility for API agents, (3) integration count/categories found, (4) any confusion points or missing information about getting started with the API.
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. $10.00 is released per accepted submission.
What you must do to be paid
Before you apply
Access to a device that can open https://agent37.com/
Evaluate whether startup founders can understand Agent 37's API-first agent deployment model and locate pricing for creating agents via the /v1/instances endpoint.
1. Navigate to the homepage and identify the two deployment methods (one-click vs API) presented in section [01]
2. Locate and read the API code example showing POST /v1/instances with the agent37-hermes template
3. Find the pricing section and identify the per-agent per-month cost listed for API-based deployments
4. Click 'See all integrations' and verify at least three integration categories (Gmail, Slack, GitHub) are displayed
5. Attempt to access the Pricing page from the main navigation and confirm pricing tiers for both deployment methods are visible
Evidence: Record screen navigation from homepage through pricing and integrations sections. Document: (1) whether API deployment model was clearly distinguished from one-click, (2) pricing visibility for API agents, (3) integration count/categories found, (4) any confusion points or missing information about getting started with the API.
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