Skip to main content
Your subscription includes allowances for the ways your team and your agents use Tempo. The allowances themselves are in your Order Form. This page explains how usage is counted, how to keep an eye on it, and the limits Tempo applies to keep the platform stable for everyone.

​
What is counted

​
What is not counted

  • Re-synced content that has not changed since Tempo last received it.
  • Anything Tempo generates, including observations, deal state, summaries, and Themes.
  • Context Tempo received before your Effective Date, if you used Tempo before signing.

​
Allowances

Each allowance applies to the period your Order Form states, resets at the start of the next period, and does not roll over. The historical backfill allowance is the exception: it is a one-time amount for onboarding and does not reset. Authorized Users are unlimited. Adding a member does not consume an allowance.

​
Review recorded activity

Organization admins can review recorded activity in Settings → Usage. The report shows the last 30 days when that history is available.
1

Open the report

In the Tempo app, open Settings → Usage.
2

See daily numbers

Click Show daily numbers as a table below the charts for exact counts by date.
The report has four summary cards: Daily charts and the member table show when activity occurred and who took part. A person counts as active after opening Tempo, calling an MCP tool, or approving or rejecting an update. Background processing, history imports, and support impersonation do not count as human activity. Approval counts describe approvals, not confirmed CRM writes. Dates follow the time zone set under Timezone in Settings → Profile, and the report names that time zone. Tempo fills in your browser’s time zone when you have not chosen one. If no valid time zone is set, dates use UTC. Each admin sees days in their own time zone, so two admins can see different daily totals. Today is incomplete, and weekly comparisons use complete days. If reporting starts partway through the 30-day window, the report names the first available date. Earlier days are unavailable, and totals cover only the recorded period. For some earlier days, activity counts only people who are still members. When this applies, the report names the date. Activity before that date does not include people who have since left. The report shows activity, not your remaining subscription allowance. For an allowance balance, ask for a report through support.

​
When the report is unavailable

If you see Usage could not be loaded, refresh the page. If you see Usage is currently unavailable, read the message below it. If Tempo could not retrieve activity, click Refresh or try again shortly. If reporting is not available for your organization yet, contact support.

​
Usage beyond an allowance

Usage above an included allowance is billed at the additional usage rates in your Order Form, on the schedule it states. Tempo does not cut off access when you pass an allowance.

​
Rate limits

Independently of allowances, Tempo applies limits that protect the stability and security of the platform. Hitting a rate limit is not an outage and does not count against your allowance.

​
Agentic search concurrency

Agentic search, which backs the search_deal_context MCP tool and the POST /api/v1/agentic-search/deal-context endpoint, is the most expensive request Tempo serves. Each user, or each API key when no acting user is set, can run a small number of agentic searches at the same time. A request above that limit is rejected immediately with HTTP 429 Too Many Requests rather than queued. To stay under the limit:
  • Wait for an in-flight search to finish before starting another for the same user.
  • Use the faster read and query endpoints where a synthesized answer is not needed. See which surface to use.
  • On a 429, back off and retry after a few seconds. Do not retry in a tight loop.

​
Connected source limits

Salesforce, HubSpot, Google, Slack, and other connected sources apply their own API limits. Tempo paces its sync to stay within them, which can delay how quickly new context appears after a large change. These limits affect sync timing only. They do not affect your allowances or Tempo’s availability commitment.

​
General guidance

  • Treat any 429 response as a signal to slow down, and honor a Retry-After header when one is present.
  • Keep one API key per integration so you can tell which client is responsible for a spike. See Create a key.
  • If a legitimate workload needs more headroom, get in touch. Limits can be reviewed for your organization.