FAQ

Each idle gap that exceeds the earned context window closes the billing cycle. A new cycle means a new first hour — and the first hour absorbs the full context reload: your topology, current state, constraints. Sprinting amortizes that cost across more hours.

No. The formula is deterministic — same inputs always produce the same price. This protects both sides: you know exactly what you'll pay before we start, and I don't have to guess what the market will bear. The only discount is -15% for USDT payment.

Productive time only, at 0.5h granularity. Waiting for your response, reading documentation, or troubleshooting my own tools — not billed. The first 30 minutes of any engagement are free.

USDT payments receive a 15% discount on the total. This reflects lower transaction costs and faster settlement. Applied after all other calculations (tier multiplier, formula).

Yes — with grounding infrastructure. AI generates RouterOS configurations from verified facts (your topology, firmware version, hardware model), not from hallucinated documentation. I authored routeros-7-llm-safe-reference specifically to prevent AI errors in network config.

Yes. This happens more often than you'd think. Ungrounded AI generates plausible-looking but conflicting rules. I audit the full configuration, identify contradictions, rebuild from scratch, and teach you how to use AI tools safely going forward.

A curated, version-specific dataset of valid RouterOS commands, syntax, and constraints. When an LLM generates configuration using this grounding data, it produces commands that actually exist in your firmware version. Without grounding, AI will confidently generate commands that don't exist.