# Access, keys and AI costs

Choose the right keys, understand model billing and keep team subscriptions and payment history.

Team members and owners using several products or agent connections.

You understand connection access, model billing and the team’s cost records.

## Use the right key

A passkey signs you in through your device. It is not an API secret to paste into a client configuration.

- A personal Hub agent key lets your agent work through MCP or the API with your permissions in one team. It does not pay for a model.

- Product data keys let your app send events or payments to Hub. The SDK event key and the separate server-side money key are not interchangeable. Keep the money key out of browser code; neither key gives an agent access to tasks.

- Keys from external services connect those services to Hub. The model key links the built-in Analyst’s requests to your provider account for billing; Sentry and other source tokens give access to those services’ data.

## Check access and payment

1. Check the current account and team. Owners manage invitations, members’ product access and shared connections. Each member connects their own agent under their own identity.

2. If an agent needs another product, ask the owner to check your account’s access. Every key you create has the same product access as your account. You cannot currently set a separate product list for each key.

3. For the built-in Analyst, open Model connections and use a personal key or a team key enabled by the owner. Check Payment before sending a question.

4. To change which key pays for a conversation, start a new one. Hub does not silently switch to another key when a request fails.

## Track team costs

In Team costs, an owner records agent subscriptions, infrastructure and one-off expenses. Members with access to all team products can read financial figures. Records and reminders work without another connection.

The board shows current monthly recurring costs. Recorded payments and accepted agent tasks use the chosen period. Amounts stay in their own currencies. A task’s agent budget is a manual estimate; client tokens and cost estimates stay separate from recorded payments.

1. Choose Add expense, then enter the service, amount, currency, frequency and next date. Expand payment and reminder settings when needed.

2. After paying, choose Record payment. Hub saves the mark and advances the next date for a recurring expense. The service handles the charge and invoice.

3. Open Payment history beneath upcoming payments. It shows five records at a time across all dates, independently of the board period: service, saved amount, date and author. Choose Show more for older marks.

4. An owner can reverse an incorrect mark through its row menu when that action is available. The reversed record remains visible. An archived recurring expense stays archived; reversing a mark does not request a provider refund.

## Keep these boundaries in mind

Analyst conversations are private within Hub. Paying with the team key does not let teammates read them. Requests and data still go to the chosen provider; its account administrators may have access under that provider’s rules.

Connecting an external agent and paying for the built-in Analyst are separate settings. Agent cost data in Hub may be incomplete, so compare it with your provider’s bill.

If you exposed a key, revoke it in the relevant service or in Hub and update the connection. Ask the team owner to resolve access problems.

Team and access: /app/team

Personal agents: /app/agents

Model connections: /app/connections?s=assistant

Agent costs: /app/agent-costs

URL: https://hub.n1.team/help/access-and-payment