Free plan
Know your limits.
One place for device slots, connection allowances, and the way your history syncs.
- 5
- device slots per account
- 30
- days after disconnect
- 10
- connections per 24 hours
- 90
- days of history import
Devices & connections
A slot is a place for a device. A connection is a successful authorization. They have separate limits.
| Limit | Allowance | How it works |
|---|---|---|
| Device slotsPer GitHub account | 5 | Active devices and reserved slots share the same five-slot allowance. |
| Manual disconnect | 30 days | Access stops immediately. The slot is reserved until the cooldown ends or the credential expires, whichever comes first. |
| Short connection window | 5 / 10 min | A rolling window shared by all devices on the account. |
| Daily connections | 10 / 24 h | New connections, reconnections, and credential rotations all count. Disconnecting does not refund them. |
| Credential lifetime | 180 days | Expiry releases the slot immediately. Reconnecting needs an available slot and consumes a connection allowance. |
What happens when a device leaves?
I disconnect a device
The device stops uploading immediately. Its slot cools down for up to 30 days. The same device can reconnect in its reserved slot, but that reconnection still counts toward the connection limits. Disconnecting again restarts the cooldown.
The credential expires
The slot is available immediately, with no extra cooldown. If another device takes it, the expired device must wait for a free slot. Reconnecting the expired device also counts toward the 10-minute and 24-hour connection limits.
I delete my account
Usage, credentials, and the public card are deleted. Existing connection counts and unexpired slot reservations remain. Recreating the same GitHub account connection does not give you a fresh allowance.
A device means a TokensBurned installation identity. Keep its local identity to reconnect as the same device. Deleting local files does not free a server slot.
History & sync
TokensBurned stores aggregate usage. Import range, upload frequency, and display refresh are separate rules.
- History import
- Up to 90 days
Import an explicitly selected harness and date range. Older stored totals are retained as summaries; this is not a 90-day deletion policy.
- Automatic client sync
- Triggered by your tool
Connected plugins can upload usage automatically. Use tokensburned run to start background collection and tokensburned run --stop to stop it. Automatic uploads and manual imports follow the same account update limits.
- Changes to a daily snapshot
- Hourly / daily
Today’s snapshot can change once per UTC hour. Older days can change once per UTC day. Sending more often does not force a new stored revision.
- Public card refresh
- About 1 hour
Cards and summaries use an hourly cache. A visit can refresh a stale card; publication must be explicitly enabled.
Request protection
Short request limits protect the service. They apply in addition to account allowances and can be shared by devices using the same public IP.
View request and upload limits
| Limit | Allowance | Scope |
|---|---|---|
| Start authorization | 5 / minute | Per IP address |
| Authorization requests | 60 / minute | Per IP, per route |
| Authenticated requests | 10 / minute | Per device, per route; also 60 / minute per IP, per route |
| Public card requests | 120 / minute | Per IP address |
| Upload request | 20 UTC days / 512 KiB | Per request; the client splits larger imports automatically. |
| Client daily envelope | 256 KiB | Maximum serialized daily envelope sent by the client. |
| Daily breakdowns | 32 entries / kind | Per day, for harness, provider, and model breakdowns. |
If you reach a limit
Wait until the release or retry time shown by the client. Repeated attempts, switching devices, or deleting the account do not reset the account allowance.
After account deletion
Deleting your data does not reset your free allowance.
Account deletion removes usage, device credentials, profile information, and the public card. Existing connection counts and device slot reservations remain in effect until they expire.
Connections stop counting after 24 hours. Device slot reservations end no later than 30 days after deletion, or earlier if the credential expires.
Read the privacy details