BIl-116 Add ListPrepaidCredits RPC to BillingService

[nzerouali]

Ticket: BIl-116
Adds a new RPC to the BillingService to list prepaid credit contracts for an organization.

• New ListCreditContracts RPC, scoped by account_id
• New CreditContract message with fields: id, account_id, total_amount_usd, billing_frequency, active_from, active_to, notes
• REST endpoint: GET /api/billing/v1/accounts/{account_id}/credit-contracts

[github-actions]

PR Packages Published

Python Package:

• Version: 0.116.0.dev343+4444461
• Package: qdrant-cloud-public-api
• Registry: https://us-python.pkg.dev/qdrant-cloud/python/
• To update run: uv add qdrant-cloud-public-api==0.116.0.dev343+4444461

NPM Package:

• Version: 0.116.0-dev343.4444461
• Package: @qdrant/qdrant-cloud-public-api
• Registry: https://us-npm.pkg.dev/qdrant-cloud/npm/
• To update run: npm install @qdrant/qdrant-cloud-public-api@0.116.0-dev343.4444461

[github-actions]

The latest Buf updates on your PR. Results from workflow Pull Request / linting (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Apr 16, 2026, 12:42 PM

[lomidzemikheili]

organization_id confuses me, why we use it and in the end we treat it like an account_id.

If there is not intention behind it, I would stick with account_id.

[nzerouali]

organization_id confuses me, why we use it and in the end we treat it like an account_id.

If there is not intention behind it, I would stick with account_id.

@lomidzemikheili organization_id here is intentional. It refers to the parent account, not any other individual account. In our hierarchy, an organization can have multiple accounts under it, and prepaid credits are signed at the organization level, covering all its child accounts. Using account_id would be misleading and imply the contract is scoped to a single account.

[lomidzemikheili]

LGTM! Thanks for addressing my feedback.

Resolved