GitHub Billing (BYOK) — connector documentation
- MCP endpoint:
https://byok-github-billing.connectorbay.com/mcp - REST API:
POST https://byok-github-billing.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-github-billing.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own GitHub Billing GitHub personal access token (classic, with admin:org or manage_billing:enterprise style billing access for organizations), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-github-billing.connectorbay.com/health· Tool schemas:https://byok-github-billing.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-github-billing · agent@connectorbay.com
What GitHub Billing (BYOK) is for
GitHub Billing (BYOK) lets an AI assistant read your own GitHub Billing data through the GitHub Billing API with a key you supply (GitHub personal access token (classic, with admin:org or manage_billing:enterprise style billing access for organizations)). Read-only: 9 tools (get_org_usage_summary, get_org_usage_report, get_org_premium_request_usage, get_org_ai_credit_usage, list_org_budgets, get_user_usage_summary, get_user_usage_report, get_user_premium_request_usage, get_user_ai_credit_usage). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.github.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Billing. GitHub Billing and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "How much did octo-org spend on GitHub Actions this month?"
- "Show octo-org's daily billing usage rows for October 2026."
- "How many Copilot premium requests did octo-org use this month?"
- "How many AI credits did octo-org consume this month?"
- "What spending budgets does octo-org have and how much is used?"
- "How much GitHub usage has my personal account billed this month?"
What it does
get_org_usage_summary: Get an organization's billing usage summary for a period, with quantities and amounts per product and SKU. Filter by repository, product or SKU.get_org_usage_report: Get an organization's detailed billing usage report: one row per day, product, SKU and repository with quantity and amounts.get_org_premium_request_usage: Get an organization's Copilot premium request usage for a period, by product, model and SKU, optionally for one user.get_org_ai_credit_usage: Get an organization's AI credit usage for a period, by product, model and SKU, optionally for one user.list_org_budgets: List an organization's spending budgets with amount, consumed amount, scope, product and alert settings.get_user_usage_summary: Get a user account's billing usage summary for a period, with quantities and amounts per product and SKU.get_user_usage_report: Get a user account's detailed billing usage report: one row per day, product, SKU and repository.get_user_premium_request_usage: Get a user's Copilot premium request usage for a period, by product, model and SKU.get_user_ai_credit_usage: Get a user's AI credit usage for a period, by product, model and SKU.
BYOK key
You bring your own GitHub Billing GitHub personal access token (classic, with admin:org or manage_billing:enterprise style billing access for organizations) (https://github.com/settings/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.github.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.github.com/en/rest/billing (the API this connector calls, with a BYOK key)
Live from the GitHub Billing API (api.github.com) with a BYOK key; documentation: https://docs.github.com/en/rest/billing. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitHub Billing. GitHub Billing and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your GitHub Billing account.
Built for: Worldwide. Languages: English.