*I BUILT A PRODUCT THAT YOU CAN USE TO START EARNING MONEY WITH @primus_labs TODAY* read through, and halfway down there's a prompt to give your agent to get started👇 > we all know web3 has a larping problem. > people ask freelancers to start work before they’ve shown they can cover the first invoice > this creates an easy service to sell using Primus' poof of funds: A client funding check for Web3 freelancers, creators and small agencies. 1) A freelancer or small agency enters the first invoice amount. Their prospective client receives a link and proves that they held at least that amount in USDT at the time of verification. They never have to reveal their exact balance or hand over an exchange password or API key. If the first invoice comes to $2,500, the claim just says: This account held at least 2,500 USDT at the time of verification. 2) The freelancer or small agency receive a timestamped result. They can decide whether to accept the work, ask for a deposit, or turn it down. 3) This is the simplest possible concept to sell using Primus, especially for those without a network of trading desks or funds. You can call the service Client Funding Check, Private Proof of Funds or Fund Verification - whatever you want. 3) The client generates the proof themselves through the Primus browser extension. Your service doesn’t ask for their password or API credentials - it just makes one request then outputs a report on the other end. 4) To build it, create a Primus project and choose a data template for the account balance you want to verify in the Primus Developer Hub. If the marketplace doesn’t have the exact source and balance field you need, create that template first. Give your coding agent this: Build a small web app called Client Funding Check using Primus’s zkTLS-JS-SDK. Start from Primus’s official DApp example rather than creating the integration from scratch. The app needs a freelancer view with fields for: - project name - first invoice amount - asset - client email Keep the Primus template ID and balance field in configuration. Do not let users enter arbitrary URLs. When the freelancer submits the form: 1. Create a unique verification request. 2. Turn the invoice amount into a Primus condition: balance >= invoice amount 3. Send the client a private verification link. 4. Let the client complete the proof in their own browser. 5. Verify the returned Primus attestation. 6. Show PASS or FAIL with the source, threshold, timestamp and task ID. 7. Generate a readable report and let the user download the raw attestation. 8. Keep the Primus app secret on the server. 9. Use a sample result when credentials are absent so the product still works as a preview. Use the official Primus SDK methods and add a README explaining how to run the app and configure the project. The agent should produce a small app with a request screen, a client-facing verification screen and a report screen. That’s enough for the first version. You don’t need billing, a complicated dashboard or a perfect automation system before you talk to anyone. 5) Once the workflow works, pitch it to anyone who might already be receiving inbound web3 work. You can charge per check, or charge a small monthly fee for repeated use. 6) Primus handles private data verification. Your app handles the part people should pay for - aka collecting the invoice amount, sending the request, and presenting the result. 7) you can use bot to outreach to your ICP, or your agent of choice.