How do you process asynchronous tasks today?

Meerkat, an open-source API, launches to help developers process asynchronous tasks like link monitoring and delivery tracking without building schedulers or webhook plumbing. The platform allows self-hosting or cloud use, charges only for scheduling and execution, and integrates with LLMs via user-provided API keys.

Open source API for developers who need agents to monitor links, track deliveries, and report findings — without building schedulers, webhook plumbing, or LLM tool loops. Results POST to your endpoint. Self-host anywhere · Run on the stack you already ship 01 · The primitive Every product that watches the world rebuilds the same stack: schedulers, LLM tool loops, page diffing, webhook retries. Meerkat collapses that into a single open source resource. 02 · Lifecycle POST /api/v1/tasks description: "watch URL" input params: {...} output webhook: "/hook" providers: anthropic | openai openrouter | grok key: encrypted at rest agent.execute → on schedule → on demand → change detection POST your-app.com/hook signed: hmac-sha256 retries: exponential status: 200 ✓ 06 · Architecture A task moves through three actors. You register it, Meerkat schedules and orchestrates, an LLM your key executes, and a signed webhook lands back at your endpoint. 03 · Self-host Self-host Meerkat with the same REST API as Cloud. You run Postgres and workers; users connect their own LLM keys. MIT licensed, no vendor lock-in. 04 · Run it your way Same open source codebase. Same API. Pick the operating model that fits your team. 05 · BYOK Meerkat never resells AI tokens. Each account connects an encrypted API key. Model costs go to your provider; Meerkat charges only for scheduling, execution, and webhooks. claude-sonnet-4-20250514 gpt-4o-mini meta-llama/llama-3.3-70b-instruct:free grok-3-mini 07 · In production Drop in DHL, FedEx, or UPS URLs. Meerkat polls, diffs, and webhooks only when the state actually moves. Price drops, restocks, availability shifts — converted into compact JSON your app can react to in one route. Per-run snapshots are diffed against history. You get a summary of what changed, not an HTML payload to parse. Fire a single task for research, scraping, or extraction. Marked complete after the webhook lands. 08 · API surface JSON in, JSON out. Bearer auth. Idempotent retries. Signed webhooks. The whole surface fits on one screen — identical between self-host and Cloud. /api/v1/signup Create account + API key /api/v1/tasks Register a task — recurring or one off /api/v1/tasks/:id/run Trigger an on-demand run /api/v1/tasks/:id/runs Stream execution history /api/v1/tasks/:id/events Audit log + webhook deliveries /api/v1/tasks/:id/pause Pause a recurring schedule $ meerkat init Sign up free, connect your LLM key, and ship your first webhook in under five minutes. Or deploy the open source version yourself — same API, your infrastructure.