HubSpot Agent Hub: Agents, Credits, Tier Availability and Data Preparation

HubSpot Agent Hub is described on HubSpot's product page as included for every Starter, Professional and Enterprise customer, and two costly misreadings start from that sentence. In the first, a support team switches the customer agent on for website chat, and mid-month the agent stops receiving new conversations because the included credits are spent. In the second, an administrator raises the credit limit so that one data agent prompt can run across six thousand company records. The run uses 60,000 credits, twenty months of a Professional allowance, part of them on duplicates a merge would have removed. On an account that bought its credits before 16 September 2026, the default billing setting then keeps the monthly charge at that level until the contract term ends.

This article describes Agent Hub as HubSpot documents it in September 2026. It starts with what Agent Hub is, then lists the agents with the subscription and credit rate for each. It then sets out the billing settings, prices a sample account's month under each of them, and follows how an agent reaches CRM data. It closes with the documented limits, a preparation procedure, costs and returns, symptoms, common questions and the limits of the evidence.

Agent Hub is the workspace at Agents > Agent Hub where agents and agentic workflows are activated, configured and monitored (Understand Agent Hub). An agent is an AI process that reads account data and returns an output or takes an action; HubSpot builds some, and users build custom agents in the agent builder. A HubSpot Credit is the unit in which usage-based features are billed, reset monthly (Manage HubSpot Credits).

Agent Hub in the HubSpot Product Lineup

HubSpot's navigation lists Agent Hub beside the six hubs and Smart CRM, but it is not sold in editions. The Agent Hub product page states that it is included for all Starter, Professional and Enterprise customers and that custom agents consume credits, and the Agent Hub section of HubSpot's catalog lists agents without a price. Its Intro, Agents, Workflows and Context tabs sit at Agents > Agent Hub, and runs are read in Agents > Agent Inbox.

The name runs four questions together, and the product page answers only whether the workspace is available. Whether a given agent is available depends on hub and tier; what it costs is a credit rate per unit of work; and what it can read is set by AI settings, its configuration and the permissions of whoever runs it.

HubSpot Agent Hub Agents by Subscription and Status

The catalog lists eleven agents, and its rate sheet gives a billing unit for eight of them.

Eight of the eleven are labelled Beta. The credits documentation warns that beta features may begin consuming credits and that rates may change as features evolve. HubSpot aims to give thirty days' notice before a beta feature starts consuming credits, but does not promise it. Three agents have no listed rate, which under that warning is not the same as free. The catalog also does not say how many action units a custom agent run uses, so a test run is the only estimate for those four.

The HubSpot sources disagree in three places. Understand Agent Hub lists Agent Hub for Smart CRM and Revenue Hub at Professional and Enterprise only, where the product page includes every Starter customer. The customer agent documentation adds Revenue Hub where the catalog omits it. Deal progression appears as a card on the Intro tab, while the catalog lists it as a beta Sales Hub and Service Hub feature outside its Agent Hub table.

Agent Hub Pricing and HubSpot Credits

The finding has two parts. The catalog supplies the inputs to both and performs neither calculation. First, no agent is priced by seat or by account. For five of the eight agents with a rate, the billing unit is a CRM item: a record, a lead, a resolved conversation, a contact's personalised email or an invoice. A Professional account's 3,000 included credits therefore pay for a data agent prompt on 300 records, or 60 resolved conversations, or 30 prospecting leads. The size and duplication of the population an agent works on set the month's credit use; the number of users does not enter the calculation.

Second, the billing setting decides whether a one-time run is paid for once or every month. Under overage billing, the setting HubSpot labels Pay-as-you-go, a backfill across a large population is billed once. Under auto-upgrade, usage above the monthly limit raises the account's credit capacity for the rest of its commitment term, and that capacity can only be lowered when the term ends. A one-off run then becomes the monthly price.

Included credits follow the highest tier held, not the number of hubs. The catalog grants 500, 3,000 or 5,000 a month at Starter, Professional or Enterprise, and 500, 5,000 or 10,000 with Data Hub or the Customer Platform bundle. Two Professional hubs receive 3,000, not 6,000, and unused credits do not roll over. The same balance pays for features outside Agent Hub: the rate sheet charges 10 credits for each AI action executed in a workflow, and buyer intent and Data Studio draw on it too.

Every purchase route prices a credit at one cent: overage at $0.010, a capacity pack at $10 for 1,000 credits a month, and Agent Packs at $25 for 2,500, $400 for 40,000 and $1,500 for 150,000. The route decides behaviour at the limit rather than price, since a pack commits to credits that expire unused.

The credits documentation sets out what happens at the limit. An account that has bought no credits pauses every credit-consuming feature at its included limit until the reset date or a purchase. Once credits are bought, usage past the limit triggers auto-upgrade, the default for purchases before 16 September 2026, or overage billing, the default for purchases since, which charges each credit over the limit once at the per-credit rate. A spend limit, set by default 50 per cent above total monthly credits, pauses credit features when it is reached. Only users on paid seats or Partner Seats can use credits.

A test run simulates an agent, reading CRM context, without consuming credits or changing records, and a monthly run limit caps its runs (Test and control agent credit usage). The same article records that all agents started consuming credits on 23 July 2026. The customer agent is billed per resolution: a conversation in which it shared a source or performed an action with no visitor-initiated handoff within 72 hours, or in which it set a lead's qualification. A first customer agent set-up can opt into 14 days of free access, during which it uses no credits.

Credit Consumption on a Sample Professional Account

The figures below are sample data built from catalog rates read on 27 September 2026; they describe no client and are not a quote. The sample account holds Sales Hub and Service Hub Professional, so it receives 3,000 credits a month.

With nothing purchased, the plan stops at 3,000 credits, and the customer agent stops taking new chats at that point. With credits bought on overage billing and the maximum monthly credits raised to cover the plan, the recurring month bills 32,000 credits after the included 3,000, or $320. The first month bills 92,000, or $920. The prospecting line is a floor, because the prospecting agent documentation adds credit-consuming steps according to each play's settings.

The backfill equals twenty months of included credits, and 720 of the 6,000 companies are duplicates in this sample, so 7,200 credits answer the same question twice. Merging first cuts the backfill to 52,800 credits and the first month's bill under overage billing to $848.

Under auto-upgrade, the backfill month lifts the account to 95,000 credits a month, 92 capacity packs above the included 3,000, for the rest of the term. The recurring plan uses 35,000 of them. The other 60,000 expire unused each month, and the $6,600 difference is their price. Merging first lowers that monthly price from $920 to $850, since capacity is sold in packs of 1,000 credits. The table treats the backfill month itself as billed at the upgraded capacity, because HubSpot does not document how the month of an upgrade is prorated.

Shared Data Layer Access for Agents

An agent reads the same records, conversations and files as other HubSpot tools, through four gates.

The first gate is account-wide. In Settings > Account management > AI, the Access tab holds a master switch, Give users access to generative AI tools and features, with three data switches beneath it: CRM data, Customer conversation data and Files data (AI settings). Files data is off by default, yet the agent builder and the data, prospecting and customer agents all require it on. The agent builder, the Agent Marketplace and the Agent Inbox also require the separate Give users access to Breeze Assistant switch. AI settings also hold the AI model training switch, on by default.

The second gate is the agent's configuration. In the agent builder, an agent reaches data only through the actions granted to it (HubSpot actions such as getting data, reading or writing CRM records, browsing the web, and MCP connections), the knowledge attached to it, and inputs supplied at run time. Knowledge means the Context tab's defaults, such as the brand kit and ideal customer profiles, connected integrations, and up to 50 knowledge vaults built from files, content or segments.

The third gate is the person running the agent. By default Super Admins edit an agent and every user can run it, and an agent run from a workflow or automation acts with its owner's permissions, so its actions may fail wherever the owner lacks access (Run agents and review output).

The fourth gate is built into each HubSpot agent. The customer agent reads or updates contact properties only, up to ten, each behind a Match email or Verify email check (customer agent CRM access). The prospecting agent considers the past year's engagements associated with contact records and sends from the contact owner's connected inbox or a fallback sender. The data agent answers one prompt per record from web research, the company website, property data or call transcripts.

HubSpot's set-up guidance states the consequence generally: incomplete property values can produce inaccurate or generic output, and duplicates can lead the AI to outdated or conflicting information. Which records a feature can reach is the question HubSpot Smart CRM treats for the data model as a whole; for agents it acquires a price, since a duplicate is billed as well as misread.

Agentic Workflows, Agent Builder and Documented Limits

Agentic workflows require Professional or Enterprise, the tier step set out in HubSpot Starter vs Professional, and Starter runs agents from automations in a side panel instead. The Agent Hub workflow builder accepts one trigger per workflow, offers only some workflow actions, and cannot enroll records manually. The older tool's Run agent action is limited to 500 executions a day, and migrating a workflow into the new builder requires two betas, restarts its version history and cannot be reversed.

The Agent Marketplace lists only HubSpot's pre-built agents, so a custom agent cannot be published there, and five agents were withdrawn on 23 July 2026: Social Post, ABM Landing Page, RFP, Cross-sell/Upsell and Sales to Marketing Feedback. Deleting an agent is permanent, credit-consuming prospecting actions cannot run in a sandbox, and every credit estimate is, in HubSpot's words, for informational purposes only.

Data Preparation Procedure Before Enabling Agents

1. List each intended agent against the subscription table, with the unit it bills on and the expected monthly count of that unit. List separately any one-time run, such as a backfill, with its count.
2. In Settings > Account management > AI, confirm the master switch, CRM data, Customer conversation data and Breeze Assistant access are on, turn Files data on, and record the decision on AI model training.
3. In Agents > Agent Hub, complete the Context tab with the brand identity, products and services, ideal customer profiles and buyer profiles that the set-up guidance lists.
4. Build a segment for each agent's target population, run duplicate management over it, and merge before any agent reads it.
5. Fill the properties each prompt references, measuring property completeness per segment, associate calls, meetings and notes with their contacts, and confirm every contact owner in a prospecting segment has a connected inbox.
6. Restrict the Agent builder, Customer agent editor, Prospecting agent admin and assignment, and Data Agent access permissions to named users.
7. In Account & Billing > Usage & Limits > HubSpot Credits, set maximum monthly credits and feature limits. Where credits have been bought, read the Overage setting, and switch auto-upgrade to Pay-as-you-go before any one-time run from step 1. The switch needs a Super Admin or Billing Admin, and it takes effect only from the next usage period once credits have been used in the current one.
8. Test each agent on sample input, since a simulation can still call MCP tools, and set a monthly run limit from its estimate. For a first customer agent, use the 14 days of free access to measure how many conversations resolve before credits are spent.
9. Verify after one week. For custom agents, expand the sources of three runs in Agents > Agent Inbox and confirm each read the intended records. For the customer agent, open three conversations counted as resolved and confirm each shared a source or completed an action. Then compare usage by feature on the HubSpot Credits tab with the step 1 estimate, and investigate any agent more than a fifth above it.

Costs and Returns of Agent Hub

What Agent Hub buys is work priced per unit rather than per person: at one cent a credit, a resolved conversation costs $0.50, a prospecting lead $1.00 and a data agent answer on one record $0.10, figures a business can set against the same unit done by staff. The largest avoidable cost in the sample is a billing setting, not a rate: $6,600 over one term for running a backfill under auto-upgrade. The costs beyond credits are preparation and governance: context kept current, segments deduplicated and associated before the first run, credit-consuming permissions limited to named users, and write access granted only where an unreviewed change to a record is acceptable.

HubSpot's product page reports averages for agent users, such as 39 per cent faster ticket resolution than teams not using the customer agent, without saying how users were selected or compared. A comparison between adopters and others cannot separate the agent's effect from the kind of business that adopts one, so the figures are a vendor claim rather than an expected return.

The case is strongest for high-volume, repeatable work on a deduplicated, associated population: support questions answered from maintained content, or a property whose answer is worth more than ten cents a record. It is weakest where volumes are small and irregular, where records are duplicated or unassociated, and where a Starter account needs agentic workflows.

Two alternatives win on specific axes. Where the rule can be written down, a workflow without AI actions or a calculated property returns the same output for the same input and has no line on the rate sheet. Where the task is one question about one record, the set-up guidance states that Breeze Assistant works without using credits, and the customer agent's reply recommendations consume none. The firm is a HubSpot Solutions Partner and is paid for the preparation this article describes, which is the interest to weigh against this section.

Agent Hub Symptoms and Their Causes

Agents cannot be created, installed or run, although other AI features work. AI settings document the master switch as the requirement for generative features and the data switches as additional access. Agents list further prerequisites: Files data on, which is off by default, Breeze Assistant access on, and a user holding Super Admin or the Agent builder permission.

The monthly credit charge stays high after a one-time run has finished. The account is on auto-upgrade, and the run raised its capacity for the rest of the commitment term. The tier can only be lowered at the end of the term, so the fix is to switch to overage billing before the next one-time run.

The customer agent stops taking chats before the month ends. The included credits are spent with nothing purchased, or the spend limit is reached, and new conversations route through the configured handoff instead.

An agent works when run by hand and fails inside a workflow. Workflow runs use the agent owner's permissions, and the owner lacks access to a tool one of its actions needs.

The customer agent cannot answer an order question although the CRM holds the answer. The value sits on a deal, company or custom object, and the customer agent reads contact properties only.

Credit use runs above the test estimate. Duplicates are billed as separate units, a play adds steps beyond the per-lead rate, or email threads reopened after 72 hours count as new resolutions; a custom agent's Run history tab in the agent builder shows the estimated credits per run.

Frequently Asked Questions

Is HubSpot Agent Hub pricing separate from the hub subscriptions?

HubSpot Agent Hub has no price of its own, and the product page includes it with every Starter, Professional and Enterprise subscription. Its pricing is each agent's credit rate at one cent a credit, drawn first from the credits included with the highest tier held. Beyond those, the billing setting decides whether extra usage is charged once or raises the monthly capacity for the rest of the term.

Is agent hub HubSpot's replacement for the workflows tool?

Not in September 2026: eligible workflows can be migrated into its builder through two betas, and the workflows tool remains, with a Run agent action.

Which subscription does the HubSpot Service Hub AI customer service agent need?

Professional or Enterprise of Marketing, Sales, Service, Content or Data Hub or Smart CRM, so Service Hub is one route rather than a requirement.

Is there a HubSpot Service Hub AI knowledge base agent?

Yes: the knowledge base agent, in beta, finds gaps in knowledge base articles, needs Service Hub Professional or Enterprise, and costs 200 credits per new article.

Does the HubSpot Sales Hub prospecting agent require Sales Hub?

No. Any Starter, Professional or Enterprise product qualifies, at 100 credits per lead, so a Starter account's included credits cover five leads a month.

Is the HubSpot Marketing Hub social media AI agent still available?

The Social Post Agent was withdrawn on 23 July 2026 and remains only where installed; the beta content agent, for Marketing Hub Professional and Enterprise, creates social content instead.

Which agent builder changes took effect on 23 July 2026?

Every agent began consuming HubSpot Credits, and five pre-built agents could no longer be installed, so HubSpot recommends free simulated runs and a monthly run limit per agent.

Scope and Limits of the Evidence

Every product fact here is as documented in September 2026, read from HubSpot's knowledge base, product page and catalog on 27 September 2026, which are authoritative over this text. Eight of eleven agents are in beta and their rates may change. Breeze Assistant, AEO, HubSpot Work and external AI clients are outside this article's scope, as are the other credit-consuming features that share the balance, such as workflow AI actions, buyer intent and Data Studio.

The sample account shows how per-unit rates, allowances and billing settings combine, not how many conversations resolve or records duplicate in any real account. HubSpot does not document how an auto-upgrade month is prorated, so the term comparison follows the documented rules for the eleven months after the backfill and assumes the backfill month. No independent evidence of what agents return was found, only vendor averages published without a method.

In Summary

HubSpot Agent Hub is the workspace where pre-built and custom agents are activated, built, run and monitored. The product page includes it with every Starter, Professional and Enterprise subscription, and the catalog lists it without a price. Of eleven catalogued agents, the data, prospecting and customer agents carry no beta label, and eight are in beta.

Agents are billed per unit of work at one cent a credit however credits are bought. Where the unit is a CRM item, a Professional account's 3,000 included credits cover 300 data agent record prompts, 60 resolved conversations or 30 prospecting leads. Agents read CRM data through AI settings in which Files data starts switched off, through their own actions and knowledge, and with their owner's permissions inside workflows.

Before the first agent is switched on, the segment it will read should be merged, associated and counted. That count multiplied by the agent's rate is the month's credit use, and deduplication lowers the count without reducing the work done. Before any one-time run over a large segment, the billing setting needs the same attention: overage billing charges for the run once, while auto-upgrade makes it the monthly price until the term ends.