For the complete documentation index, see llms.txt. This page is also available as Markdown.

Credits Item Display Order

Describes the display order contract for Credits items and transaction details in API responses.

Credits pricing, transaction details, and agent execution records use the same display order. When presenting details, integrations should preserve the order returned by the API rather than re-sorting by name, code, or the display_order field alone.

Ordering Rules

The system sorts items by category first, then by display order within each category. The category order is:

  1. Language models

  2. Knowledge bases

  3. Voice

  4. Tools

  5. Content safety

  6. AgentOps

  7. Crawlers

  8. Avatars

  9. Meetings

  10. Platform fees

Items that do not belong to an existing category are placed after the categories above. Transactions in the same position are further ordered by time and identifier to maintain a stable order.

display_order only indicates the position within the same category. Different categories may use identical or interleaved values, so this field alone cannot reconstruct the complete order.

Affected Responses

This order applies to Credits pricing items, expanded transaction records, and Credits details in agent execution records. CSV pricing exports use the same order.

If an integration needs custom categories or visual grouping, it can add group headings while preserving the API order. Reordering items may cause the admin console and external reports to show different results.

Upgrade Checklist

  1. Remove frontend sorting by name or code.

  2. Check whether display_order is treated as a global rank across categories.

  3. Compare the pricing page, transaction details, and exported files to confirm that the relative order of the same items is consistent.

Last updated

Was this helpful?