Archestra Apps HackathonSee what people are building

Thread

J
jce2:04 PMOpen in Slack
hi guys. Can I track costs per user in archestra (without making a team or proxy per user πŸ™‚ ) ?

8 replies
A
Archestra2:04 PMOpen in Slack
Yes! You can use *tags* on API calls to track costs per user. Add a tags array to your requests: ``json { "tags": ["user:alice", "project:demo"], ... } `` Then filter by tags in your usage dashboard or via the API. Docs: https://archestra.ai/docs/platform-quickstart (see the tags section) πŸ€– Slack Agent
πŸ™Œ1
J
jce2:04 PMOpen in Slack
lol the bot is awesome πŸ˜„
😁2
A
Archestra2:04 PMOpen in Slack
Thanks! πŸ˜„ Let me know if you need anything else! πŸ€– Slack Agent
J
jce2:08 PMOpen in Slack
but to make it more precise: where do I these tags? When Claude is making the requests to the llm proxy I cannot enrich the request with custom tags can i ?
A
Archestra2:08 PMOpen in Slack
Good point! If Claude (or another model) is making requests through the proxy, you can't inject tags at call time. *Options: 1. Proxy-level default tags β€” set tags on the proxy config itself (e.g., "defaultTags": ["user:alice"]). You'd still need one proxy per user though. 2. API key tags β€” create per-user API keys with tags baked in. Usage gets attributed via the key. 3. Custom header* β€” some setups let you pass X-Archestra-Tags header if the client allows custom headers. What's your setup β€” are you using MCP, or direct API calls from your app? πŸ€– Slack Agent
MK
Matvey Kukuy (archestra team)2:10 PMOpen in Slack
If you're using claude, Connect page should generate per-user keys so your logs should be attributed
J
jce2:27 PMOpen in Slack
ok
A
Archestra2:27 PMOpen in Slack
Got it! So with Claude via the Connect page, your logs are already attributed per user. Let me know if you need help with anything else! πŸ€– Slack Agent