Original Summary

Jobven went live on two API marketplaces this week, Apify and RapidAPI. It's a side project of mine that collects job postings straight from employer career pages: about 1.2 million open jobs from more than 7,500 employers. Both marketplaces bill the buyer for you and pay out a share. Handy, except the billing code is still yours, running against someone else's meter. So before publishing, I set AI agents on each integration, three at a time, each with one job: leak my internal key, get jobs without paying, or knock the service over for everyone else. Every finding had to come with a failing test. Some of what they found: Billed twice. Apify's pay-per-event setup includes a default charge for every item a run saves. Alongside my own per-job charge, every job would have been billed twice. The actor now refuses to run while its pricing is set up that way. Charged again on restart. A run that migrates to another server, or that the buyer resurrects, started from page one and charged the same jobs a second time. It saves its place after every page. A $0 spending limit meant unlimited. The SDK reads 0 as "no limit". A buyer who sets 0 gets nothing. Errors that still cost money. On RapidAPI, a request with no billing header counts as one unit, so a 404 or a malformed request cost the buyer. Every error there bills zero. None of these show up in a happy-path test. They're all about what the other system does around your code. One call I'm still unsure about, and happy to be argued out of: A 50,000-job cap per run. A run stops at 50,000 jobs even if the buyer's spending limit allows more. It keeps every run a manageable size. It also means a big buyer starts several runs. Both listings are up. The first test run on Apify returned 100 jobs and recorded exactly 100 job charges, which after all that was a nice thing to see.   submitted by   /u/ConstIsNull [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/18 06:35:52