Instrument
Add project and workflow labels around one supported provider path, plus input, cached-input where exposed, output, attempts, and accepted-result status.
FIXED-SCOPE IMPLEMENTATION · £75
Ship cost attribution into one AI workflow.
I instrument one authorized Node.js/TypeScript or Python codebase so each model call can be attributed to a project and workflow, reconciled to token usage, and exported into the free TokenGauge ledger.
No account required · no payment before scope · no credentials in the enquiry
DELIVERABLEA working ledger path,
A working ledger path,
not a slide deck.
The goal is a reviewable implementation that records the fields needed to answer which feature moved the bill. Prompts and model outputs are excluded from the new cost log by default.
Export
Produce the documented TokenGauge CSV schema so aggregates can be opened in the free browser-local ledger without a proprietary ingestion service.
Verify
Add focused tests, run the repository's existing quality gate, and show one sanitized sample that imports and totals correctly.
INCLUDED
Clear acceptance checks.
- One Node.js/TypeScript or Python repository you are authorized to modify
- One existing OpenAI, Anthropic, Gemini, xAI, DeepSeek, Kimi, Qwen, Mistral, or Cohere request path
- Project/workflow attribution and retry-aware attempts
- Canonical CSV export plus one validated import
- Focused automated tests, handoff notes, and one revision
BOUNDARIES
Deliberately small.
- No data-warehouse migration, billing system, or new analytics dashboard
- No provider account, API credits, hosting spend, or secret collection
- No promise that a cost reduction exists
- No production deployment unless it is explicitly included in the written scope
- No work begins until repository access, acceptance checks, and payment timing are agreed
PROCESS
Public context first. Private access later.
Send the public URL
Use the prefilled email, Telegram, or the public GitHub form. Share only a public repository or product URL and the outcome you need. Do not send credentials, private source, prompts, outputs, customer data, or payment details.
Receive written scope
I confirm fit, exact files or integration boundary, acceptance checks, delivery target, and payment timing before implementation.
Review the change
You receive a focused branch or pull request, test evidence, the ledger import fixture, and one revision inside the agreed boundary.
START WITH NO SECRETS
Describe the workflow and desired attribution.
Replies are asynchronous. Suitable enquiries receive a written scope before any payment request. Need enforcement rather than reporting? See the budget guard →