Update API limits docs to unify trace + score deletion under trace data deletion

[Copilot]

This updates the API limits page to match the deletion-rate-limit model introduced in langfuse/langfuse#12886. Trace deletion and score deletion limits are now documented together under a single “trace data deletion via public API” concept to reduce ambiguity.

• Documentation structure

  • Consolidated deletion-related wording in the rate-limiting doc so trace and score deletion are represented as one public-API deletion category.
  • Replaced separate trace-deletion framing with a unified “trace data deletion via public API” headline/entry.

• Rate-limit table updates

  • Updated the relevant row in content/faq/all/api-limits.mdx to describe both trace and score deletion under the same resource class.
  • Kept plan-tier formatting and table layout consistent with existing conventions.

• Request constraints alignment

  • Adjusted deletion constraint wording to reflect the merged deletion concept (trace data deletion via public API) instead of only trace deletion.

| **Trace Data Deletion via Public API**. DELETE APIs used to delete trace data (traces and scores). | ... |

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-docs	Ready	Preview, Comment	Mar 31, 2026 8:13am