{"version":"2.1.314","anchor":"new-api-call-and-signer-telemetry-names","canonical_anchor":"new-api-call-and-signer-telemetry-names","heading":"Two new labels for API calls about effort caps and peer sending","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/new-api-call-and-signer-telemetry-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Two new labels for API calls about effort caps and peer sending\n\nClaude Code's list of API call labels gains entries for retrying under an organisation effort cap and for a signed peer send\n\n**What**\n\nClaude Code labels each kind of request it sends to the API. The list of labels gains two entries:\n\n- `api_org_effort_cap_retry`, for retrying a request when an organisation caps effort\n\n- `peer_send_signer`, for a signed request sent to a peer\n\n**Why**\n\nThe names point to a retry path for organisation-level effort limits and to signed messages between sessions. Only the labels themselves are present.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}