costhawk 1.5.13 → 1.5.15

package/README.md

@@ -168,9 +168,13 @@ COSTHAWK_GIT_SHA=$(git rev-parse --short HEAD) npm run build
 | Tool | Description |
 |------|-------------|
 | `costhawk_get_usage_summary` | Get usage and costs over a time period (by provider/model) |
-| `costhawk_get_usage_by_tag` | Get usage grouped by custom tags (user_id, feature, etc.) |
+| `costhawk_get_usage_by_tag` | Get usage grouped by attribution fields and custom metadata (`project`, `feature`, `team`, `environment`, `user_id`, etc.) |
 | `costhawk_detect_anomalies` | Check for cost anomalies and unusual usage patterns |
 
+`costhawk_get_usage_by_tag` has two data sources:
+- Standard attribution fields like `feature`, `project`, `team`, and `environment` can come from wrapped-key or scoped API key attribution.
+- Arbitrary custom tag keys only appear when you send request metadata through the proxy, such as `costhawk_metadata.feature` or `costhawk_metadata.user_id`.
+
 ### Claude Code Local Tracking (Optional Auto-Sync)
 
 These tools parse your local Claude Code transcripts from `~/.claude/projects/` to track token usage - including the 4 token types Claude Code uses.

package/dist/build-info.d.ts

@@ -1,2 +1,2 @@
-export declare const BUILD_COMMIT_SHA = "1ed40d7";
+export declare const BUILD_COMMIT_SHA = "7a15693";
 //# sourceMappingURL=build-info.d.ts.map

package/dist/build-info.js

@@ -1,3 +1,3 @@
 // Auto-generated during release builds. Values may be empty in dev.
-export const BUILD_COMMIT_SHA = "1ed40d7";
+export const BUILD_COMMIT_SHA = "7a15693";
 //# sourceMappingURL=build-info.js.map