Repository navigation
Replies: 3 comments
|
Hi Mike, thanks for asking first. Much appreciated.
Good luck with the launch! |
|
Hi Mike — following up on my promise to let you know in advance. I've launched commercial API plans: freehire.me/jobs-api. What changes
Current keyless limits (per IP): 600/min for public reads, 300/min for No rush on your side: your current setup keeps working as-is until November 19, 2026. After that, please move Commuter onto an API key. Thanks again for asking the right way from the start. |
|
Hi Mike, a quick update on the keyless limits I said I'd announce here. As of today (October 30) the keyless budget is 120 requests/minute and 2,000/day per IP, shared across the public read endpoints. This doesn't affect Commuter. From our logs you make about 10 requests a day, far inside the new limit, so your setup keeps working as-is. The November 19 date for moving to a key still stands. A key now raises the budget even without a paid plan. Any full-access key (or a signed-in MCP/CLI connection) is budgeted per account instead of per IP:
Sorry this note lands on the day rather than before it. |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I run Commuter (commuter.dev), a small paid job-search assistant [still under development] from 0pon, LLC. It finds postings that fit a user's resume, ranks them, and drafts tailored application documents. freehire is one of its main sources: each user's daily refresh runs a few searches against the public freehire.dev search, so today that's a few dozen requests a day. Every match links back to the original posting.
freehire is MIT-licensed, but I'd rather ask than assume, since Commuter charges users and depends on a service you run yourself. Three questions:
Happy to adjust anything. Thanks for building it!
All reactions