Apihustle // toolworks
Small tools for the part of your stack nobody thinks about until it breaks: scheduled calls, uptime checks, and the job that quietly never ran. Set up in a minute. No sales calls.
Position
Tools for developers and agile teams who would rather ship than set things up. This is how we build them, and what that means for you.
Sensible defaults get you a working schedule or monitor in about a minute. When you need more, the controls are there: intervals, headers, payloads, retries, grace periods. A simple first screen does not mean a shallow tool.
Describe what you want in plain language and get a working workflow back. Plug the tools into Claude Code, Codex or any other MCP client and run them from where you already work.
Sign in once. Every tool that needs an account uses the same one, with the same billing and the same team. The ones that do not need an account stay that way.
Slack, Discord, Telegram, email, or a webhook to anything else. You choose where a failure shows up. Nobody should have to remember to open a dashboard.
Our own jobs, checks and deploys go through these tools. When something breaks we are usually the first to know, and the fix is our problem before it is yours.
Built in Copenhagen. Used every day by the people who make it.
Read the full manifestoThe flagship
Most of what we build comes back to one question: did the thing that was supposed to happen actually happen? Crontap answers it from three directions.
Crontap calls your endpoint on a schedule, written as cron or plain English. It catches the call that fails.
CrontapCrontap checks a public URL on an interval. It catches the service that stops responding.
Uptime MonitoringYour job pings Crontap when it finishes. It catches the job that never ran, ran late, or failed.
Heartbeats
Crontap, in three parts
All three live in one Crontap account, with one notification list and one dashboard. Each catches a kind of failure the other two miss.
Schedule recurring API calls with cron syntax.
Crontap calls your endpoints on a schedule you write in cron or plain English. Pick a frequency and a timezone, test the call once, and forget about it.
Uptime monitoring built into Crontap.
Point Crontap at a public URL and it checks it on an interval, from every minute to once a day. You get 90 days of history, daily uptime bars, and an email when it stops responding.
The alert for the cron job that never ran.
Heartbeats turn monitoring around: your job pings Crontap after it runs. If the ping does not arrive in time, you get an alert.
The full suite
8 products. Each does one job and works on its own.
See your API's real performance at a glance.
Clobbr hits an endpoint in sequence or in parallel and shows what happens to response times under load. It runs on your machine, on macOS, Windows or the CLI. One lifetime licence, no account.
Describe your website. Get real code back.
Page AI plans, designs and writes your website, then hands you clean code instead of locking you into an editor. It does the first draft. You finish it.
Your boilerplate, set up and deployed.
Shipixen builds a codebase for your landing page, blog or product site, deploys it, and hands you the repository. Skip the first day of every project.
Landing page components for React and Next.js.
Templates, components and examples for landing pages that convert. Open source, styled with Tailwind CSS, and free to copy into your project.
Read, debug and compare cron expressions on a calendar.
Paste a cron expression and see exactly when it fires. CronTool puts several schedules side by side on one calendar, understands extended syntax, and needs no account.
Index
Start somewhere
Crontap is free to start and takes about a minute to set up. It catches the call that failed, the URL that stopped answering, and the job that never ran.
