chore(docs): fix costs route typo

[avivhalfon]

Important

Fixes URL in property_costs.mdx for the costs route to correct endpoint.

• API Reference:
  • Fixes URL in property_costs.mdx from https://api.traceloop.com/api/v2/costs/by-association-property to https://api.traceloop.com/v2/costs/by-association-property.

^{This description was created by for 884657d. You can customize this summary. It will automatically update as commits are pushed.}

Summary by CodeRabbit

• Documentation
  • Updated the API reference for the Costs by Association Property endpoint to use the new URL: GET https://api.traceloop.com/v2/costs/by-association-property (previously https://api.traceloop.com/api/v2/costs/by-association-property).
  • No changes to parameters, response schema, examples, or error handling.
  • Action: Update any integrations or bookmarks to the new endpoint URL.

[coderabbitai]

Walkthrough

Updated the documented API endpoint path in the costs by-association-property reference, removing the extra /api segment. No other content was changed.

Changes

Cohort / File(s)	Summary
Docs: Endpoint path update api-reference/costs/property_costs.mdx	Changed documented API from GET https://api.traceloop.com/api/v2/costs/by-association-property to GET https://api.traceloop.com/v2/costs/by-association-property; no parameter, schema, or example updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nudge my whiskers at the URL line,
A tiny hop—one path now aligns.
No payloads moved, no schemas rearranged,
Just tidied tracks where calls are ranged.
Thump-thump! Docs gleam, concise and bright—
A rabbit’s joy in getting paths just right. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "chore(docs): fix costs route typo" accurately and concisely summarizes the primary change in the changeset — a documentation correction to the costs endpoint URL — and uses a conventional commit-style prefix indicating it's a docs chore. It is specific and clear enough for a teammate scanning history to understand the main change without extraneous detail. The title directly reflects the file-level edit shown in the PR summary.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ah/fix-costs-route

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7d6086c and 884657d.

📒 Files selected for processing (1)

• api-reference/costs/property_costs.mdx (1 hunks)

🔇 Additional comments (1)

api-reference/costs/property_costs.mdx (1)

3-3: Approve: endpoint path corrected — repo scan clean.

Search found only api-reference/costs/property_costs.mdx (line 3) containing the corrected URL "GET https://api.traceloop.com/v2/costs/by-association-property"; no matches for "https://api.traceloop.com/api/v2" remain.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 884657d in 41 seconds. Click for details.

• Reviewed 12 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. api-reference/costs/property_costs.mdx:3

• Draft comment:
  Confirm that the removal of the '/api' prefix in the endpoint URL is intentional and consistent with backend routing.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This violates several rules: 1) Don't ask authors to confirm their intentions 2) Don't make speculative comments 3) Don't comment unless there's clearly a code change required. The URL change was likely intentional as part of an API version update. If it was incorrect, it would be caught during testing/deployment. Maybe this is a critical API endpoint and confirming the URL change could prevent production issues? No - if this was an incorrect URL change, it would be immediately apparent in testing and CI/CD. Asking for confirmation adds no value. Delete this comment as it only asks for confirmation without providing any actionable feedback and would be caught by testing if incorrect.

Workflow ID: wflow_7ZiEBSXCi3G4BKni

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}