Start here

Data freshness and accuracy

When Lamdy syncs, what billed and estimated mean, and why a total can differ from a provider's console.

Lamdy's figures come straight from each provider's billing and usage reports. This page explains when those reports are read, how fresh they can be, and why a number in Lamdy can differ from one in a provider's console.

When Lamdy syncs

Every 30 minutes, in the background, for every connected provider, whether or not anyone has Lamdy open.
While you have Lamdy open: when a page loads, every few minutes while the tab is visible, and when you come back to the tab. A provider is re-read when its data is more than five minutes old.
On demand: Refresh at the top of every page re-reads every provider; Fetch latest on Integrations or a provider's page re-reads one.

The newest sync time is shown next to Refresh, for example “Synced 3 min ago”. Each sync re-reads the recent window in full and replaces it, so late corrections from the provider are picked up too.

How fresh the provider's own data is

Lamdy can only be as current as the provider's report. Typical delays:

Provider	Usage (tokens)	Billed cost
OpenAI, Anthropic	A few minutes	Usually within a day
OpenRouter, Deepgram, ElevenLabs, Cursor	Minutes	Minutes to hours
Azure OpenAI, Vercel AI Gateway	Several hours	Up to 24–48 hours, so Lamdy re-reads them at most every 12 hours on its own

Billed and estimated

When a provider has reported usage but not billed it yet, Lamdy estimates the cost from the rates you were actually billed for that model recently. Estimated amounts are labelled, and they are replaced by the billed figure as soon as the provider publishes it. Provider invoices remain the source of truth.

Why a total can differ from the provider's console

Days are UTC. Providers report billing days in UTC, and so does Lamdy. Times such as “last synced” are shown in your workspace's timezone (Settings).
Credits and taxes. Lamdy shows usage cost. Promotional credits, prepaid balances and tax on an invoice are not subtracted or added.
The key's scope. A key limited to one project only sees that project.
Not billed yet. Today's cost can be partly estimated until the provider bills it.

Still seeing something unexpected? See Troubleshooting.

Data freshness and accuracy

When Lamdy syncs, what billed and estimated mean, and why a total can differ from a provider's console.

When Lamdy syncs

Every 30 minutes, in the background, for every connected provider, whether or not anyone has Lamdy open.
While you have Lamdy open: when a page loads, every few minutes while the tab is visible, and when you come back to the tab. A provider is re-read when its data is more than five minutes old.
On demand: Refresh at the top of every page re-reads every provider; Fetch latest on Integrations or a provider's page re-reads one.

How fresh the provider's own data is

Lamdy can only be as current as the provider's report. Typical delays:

Provider	Usage (tokens)	Billed cost
OpenAI, Anthropic	A few minutes	Usually within a day
OpenRouter, Deepgram, ElevenLabs, Cursor	Minutes	Minutes to hours
Azure OpenAI, Vercel AI Gateway	Several hours	Up to 24–48 hours, so Lamdy re-reads them at most every 12 hours on its own

Billed and estimated

Why a total can differ from the provider's console

Days are UTC. Providers report billing days in UTC, and so does Lamdy. Times such as “last synced” are shown in your workspace's timezone (Settings).
Credits and taxes. Lamdy shows usage cost. Promotional credits, prepaid balances and tax on an invoice are not subtracted or added.
The key's scope. A key limited to one project only sees that project.
Not billed yet. Today's cost can be partly estimated until the provider bills it.

Still seeing something unexpected? See Troubleshooting.