All tools / AI cost & reliability
lifeskiff
Fail your AI over to the next vendor when billing breaks, and know about it.
Buy lifeskiff for $99One payment of $99, plus sales tax where it applies, and every future update. Delivered as a private GitHub repository you're invited to.
See it work
lifeskiff demo
10:55 first request, vendor credits gone -> answered by openai
ALERT Gemini is refusing requests (HTTP 402, billing)
10:57 next request (no new alert) -> answered by openai
11:06 ten minutes on: probe the first vendor -> answered by openai
14:21 credits topped up, probe succeeds -> answered by gemini
ALERT Gemini is answering again
14:22 back to normal -> answered by gemini
state: {"active": false, "serving": "gemini"}
What it does
lifeskiff is an ordered list of AI providers with a retry hook for any loop. It tells a broken account (billing, key or quota) from a passing glitch, moves the same request to the next vendor, probes the first one back, and alerts you once an hour.
- Billing-aware classifier
- 402, auth and day or month quota errors switch vendors; per-minute 429s, 5xx, timeouts and ordinary 400s do not. It reads the vendor's error wording, which a vendor may change.
- Ordered list of providers
- A request only moves down the list. A retry hook (begin, failed, succeeded, or run and arun) fits any loop.
- Probe-back
- While a vendor is down, one request per ten minutes tries it again, claimed under a lock so only one worker does it. The first success clears the incident.
- Alerts once an hour
- Per vendor and kind, through a function you supply, with a recovered alert. Webhook, background-thread and logger helpers are included; a webhook posts to the URL you give it.
- Payload scrub helpers
- scrub_messages and portable_tools make a history built for one vendor valid for another, so the switch does not fail on vendor-private tool-call signatures. You call them around your own model call.
- Streamed tool-call reassembly
- ToolCallAccumulator handles several calls that all report index 0 and keeps the vendor's signature.
- Shared state
- In memory, or in one JSON file shared by all workers on a machine. Any object with read() and update(fn) works as a store.
- Offline demo and command line
- lifeskiff demo replays an outage with fake vendors. classify, scrub, status, mark-down and clear are there for scripts.
What you get
lifeskiff 1.0.2: the Python package and the lifeskiff command, with an offline demo, a runnable tool-loop example and the full test suite, with 172 automated tests.
A commercial license. Use it and change it in your own projects and your clients' projects. Don't share or resell the source. Read the license.
Every update. New versions land in the same repository; git pull to get them.
Requirements
Python 3.10 or newer. Python 3.10 or newer; no third-party runtime dependencies. lifeskiff calls no vendor itself, so you bring your own model client.
How buying works
- Enter your GitHub username. You'll see the account before you pay, so you can check it's yours.
- Pay $99, plus any sales tax shown at checkout, on Stripe's checkout page.
- Accept the invitation GitHub emails you. Signed in as that account, you'll also find it at
github.com/dominares-tools/lifeskiff/invitations. Invitations expire after 7 days; you can get a new one any time. - Clone and install:
git clone https://github.com/dominares-tools/lifeskiff.gitPrivate repo: sign in to GitHub on this computer first. Run
gh auth loginand choose HTTPS, or give git a personal access token when it asks for a password. To use an SSH key instead, clonegit@github.com:dominares-tools/lifeskiff.git.python3 -m venv .venv && . .venv/bin/activate pip install ./lifeskiff
Questions
Do I need GitHub?
Yes. Access is a read-only invitation to a private repository, sent to the GitHub account you choose.
Can I get a refund?
Yes, within 14 days, no questions asked. Access ends when the refund goes through. Refund policy.
Who takes the payment?
Payments are handled by Stripe, which works out sales tax. Your receipt and card statement show Link (LINK.COM*), Stripe's checkout service.
Something wrong?
Email support@dominares.org. Every buyer of a tool shares its repository, so support happens by email rather than in GitHub issues.