---
name: answer-billing-question
description: Answer a Hyperline billing question using documentation and read-only data checks. Use when an agent needs to explain subscriptions, invoices, payments, quotes, usage, credits, wallets, analytics, custom properties, or API behavior.
---
# Answer Billing Question
Start with documentation. Use account data only when the answer depends on the customer's current state.
## Inputs
Collect:
- The user's question.
- Environment: production or sandbox if account data is needed.
- Relevant entity IDs, names, or URLs if the question is about a specific customer, subscription, invoice, quote, or product.
## Workflow
1. Classify the domain: subscriptions, invoices, payments, quotes, usage, credits, wallets, analytics, custom properties, integrations, or API.
2. Read the most relevant Hyperline documentation or API reference.
3. If the question depends on live data, run read-only MCP, CLI, or API calls to inspect the relevant records.
4. Answer directly.
5. Include links to the most relevant docs when they help the user act.
6. Separate confirmed facts from assumptions.
## Output
Return:
- Short answer first.
- Then the explanation or steps.
- Then docs links or checked records.
- Then any caveats.
## Safety
- Do not change account data while answering a question unless the user explicitly asks and confirms the exact action.
- Do not expose internal implementation details.
- Do not invent IDs, statuses, or product names.
- If data is ambiguous, say what is ambiguous and ask for the missing identifier.
