Usage & Costs

Once Syntic Code is in the hands of a team, two questions follow quickly: what is it doing, and what is it costing us? This section answers both. It brings together the operational signals you watch to keep the tool healthy, the mechanics of how the Syntic model consumes API credits, and the analytics that show how adoption is spreading across your organization.

The three views

Think of usage as three overlapping lenses. Monitoring is the operational lens: is the CLI reaching the model, are requests succeeding, and are there errors or latency problems to chase. Costs is the financial lens: how credit consumption works, what drives it up, and how to keep spend predictable. Analytics is the adoption lens: which teams and individuals are getting value, and where usage is thin. Together they let you run Syntic Code as a supported service rather than a black box.

Using them together

These views reinforce each other. A spike in cost usually shows up first as a change in monitoring data, and analytics tells you whether that spike came from broad healthy adoption or a single runaway job. Establish a baseline early, while usage is small, so that later changes are easy to interpret. Decide who owns each lens, such as a platform team for monitoring and a finance or engineering-leadership partner for costs, and agree on the thresholds that should trigger a closer look.

Read Monitoring first to set up the signals, then Costs to connect those signals to spend, and finally Analytics to understand and grow adoption.