{"version":"2.1.227","anchor":"prompts-carry-an-id-through-billing-attribution-and-request-","canonical_anchor":"prompts-carry-an-id-through-billing-attribution-and-request-","heading":"Prompts carry an ID through billing attribution and request metadata","tier":"internal","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/prompts-carry-an-id-through-billing-attribution-and-request-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Prompts carry an ID through billing attribution and request metadata\n\nEach prompt now carries its own id so usage can be attributed prompt by prompt.\n\n**What**\n\nEach user message now gets its own prompt identifier, sent as a `cc_prompt_id` segment in the billing attribution header and in request metadata, so usage can be attributed to individual prompts.\n\n**Details**\n\n- Added to the attribution header only for first-party authentication, and only when the value matches a UUID shape.\n- Removed again when transcripts are exported or serialised, so it does not appear in saved conversation files.\n\n**Evidence**\n\n`cc_prompt_id`\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}