Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

May 14, 2026 Documentation update No migration required

​
Affects

Customers and teams reading the public Tracer documentation to configure spending limits or understand validation responses. This update applies to the public documentation portal. It does not change the runtime API behavior.
The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.

​
What changed

​
Spending limit periods

The public documentation now shows the full set of supported spending limit periods:
ValueDescription
PER_TRANSACTIONApplies to each individual transaction
DAILYApplies over a daily period
WEEKLYApplies over a weekly period
MONTHLYApplies over a monthly period
CUSTOMApplies over a custom date range

​
Scheduling fields

The documentation now explains the optional scheduling fields used to control when a limit applies:
FieldDescription
activeTimeStartTime of day when the limit starts applying, in HH:mm format
activeTimeEndTime of day when the limit stops applying, in HH:mm format
customStartDateStart date for a custom-period limit
customEndDateEnd date for a custom-period limit
For CUSTOM limits, provide both customStartDate and customEndDate.

​
Limit amount

The documentation now makes the amount format explicit. For spending limits, send maxAmount as a decimal string: Before 
{
  "limitType": "DAILY",
  "maxAmount": 100000
}
After 
{
  "limitType": "DAILY",
  "maxAmount": "1000.00"
}
For a custom-period limit: 
{
  "limitType": "CUSTOM",
  "maxAmount": "5000.00",
  "customStartDate": "2026-06-01T00:00:00Z",
  "customEndDate": "2026-06-30T23:59:59Z"
}

​
Validation response timing

Validation response timing fields now allow decimal values because processing time may include fractions of a millisecond.

​
Impact

This is a documentation update. It clarifies the public documentation portal for Tracer limits. No migration is required if your current Tracer integration is already working. Use the updated documentation when configuring new limits or reviewing existing ones.

​
What you need to do

1
Use one of the documented limit periods: PER_TRANSACTION, DAILY, WEEKLY, MONTHLY, or CUSTOM.
2
Send maxAmount as a decimal string, such as "1000.00".
3
Use activeTimeStart and activeTimeEnd in HH:mm format when a limit applies only during part of the day.
4
Include both customStartDate and customEndDate for CUSTOM limits.
5
Keep transaction amounts and usage counters in the smallest currency unit where the documentation says those fields are integer values.
6
Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.

​
Deadline

None.

​
Why

The previous documentation did not show the full Tracer limit model. This update prevents readers from implementing limits from incomplete examples.

​
Resources