Add organization-scoped API-key usage analytics and last-used tracking to src/services/apiKeys.ts

[1nonlypiece]

📌 Description

API keys support hashing, scopes, and rotation, but there is no per-key usage
visibility: when a key was last used, from where, and how often. Operators cannot
identify dormant keys to revoke or spot anomalous usage spikes. This is a common
prerequisite for least-privilege key hygiene.

This issue adds last-used tracking and lightweight usage counters per API key
plus an org-scoped analytics endpoint.

🎯 Requirements and Context

• Track last_used_at, request count, and last-seen IP per key, updated on the
  auth path without adding a synchronous write on every request (batch/throttle
  the update).
• Add GET /api/orgs/:id/api-keys/usage returning per-key usage.
• Must be org-scoped; never expose key material or hashes.
• Updates must not measurably increase auth latency (async/coalesced writes).

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b feature/api-key-usage-analytics

2. Implement changes

• Add throttled usage updates to src/services/apiKeys.ts and
  src/middleware/apiKeyAuth.ts.
• Add a Knex migration for the usage columns/counters.
• Add the route to src/routes/apiKeys.ts.
• Add src/tests/apiKeys.usageAnalytics.test.ts.
• Document in docs/api-keys.md.

3. Test and commit

• Run: npm test -- src/tests/apiKeys.usageAnalytics.test.ts
• Cover edge cases: last-used update coalescing, dormant key detection, cross-org
  isolation, no key material leaked, counter accuracy under concurrency.

Example commit message

feat: API-key usage analytics with throttled last-used tracking

✅ Guidelines

• Minimum 95% test coverage on new/changed lines.
• No measurable auth-path latency regression; never expose key material.
• Timeframe: 96 hours.

🏷️ Labels

type-feature · type-enhancement · area-backend · MAYBE REWARDED · GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the contributor Discord to coordinate, ask questions, and get unblocked fast: https://discord.gg/xvNAvMJf
• Please introduce yourself in the channel before you start so we can avoid duplicate work, pair you with a reviewer, and get your PR merged quickly.
• Maintainers actively triage this channel and aim for fast, clear, respectful reviews — reach out any time you're blocked.

[JudeDaniel6]

@JudeDaniel6 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, Please can i work on this issues and give you a better result

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JudeDaniel6 to this issue.

[midexol]

@midexol has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hi maintainer, I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @midexol to this issue.

[drips-wave]

Congratulations, @midexol! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @midexol: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@midexol's PR #939 was approved and merged by @1nonlypiece.

🏆 @midexol: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (506 total points). Track your full progress on GrantFox.

👏 Great work, @midexol! Keep contributing to Disciplr-Org.