---
title: "What’s New at Explorium: October 2026"
description: "New at Explorium: a skill that migrates AgentSource v1 to v2 for you, a HubSpot Agent Builder connector, DROP compliance, and fresher prospect data."
canonical: "https://www.explorium.ai/blog/product-updates/explorium-product-updates-october-2026/"
last-updated: "2026-10-05"
---

# What’s New at Explorium: October 2026

> New at Explorium: a skill that migrates AgentSource v1 to v2 for you, a HubSpot Agent Builder connector, DROP compliance, and fresher prospect data.

- Canonical URL: https://www.explorium.ai/blog/product-updates/explorium-product-updates-october-2026/
- Last updated: 2026-10-05

September brought four updates for teams building on Explorium: a skill that migrates your AgentSource v1 integration to v2 for you, an Explorium connector for HubSpot's Agent Builder, compliance with California's DROP, and a significant refresh of our prospect data. Here is what changed and what, if anything, you need to do.

## Move from AgentSource v1 to v2 in minutes

[AgentSource v2](https://www.explorium.ai/blog/product-updates/agentsource-v2-launch/) has been generally available since early September, and v1 keeps running in parallel so nobody is forced to cut over. But "migrate at your own pace" is only useful if the migration itself is not a slog, and moving endpoints, renamed fields, filters, and webhooks by hand is exactly that.

So we packaged the migration as an [Agent Skill](https://developers.explorium.ai/v2/upgrade-skill). Drop it into Claude Code or any Agent Skills-compatible tool, point it at your project, and it does the work:

- **Audits** your code, tests, fixtures, and docs for v1 patterns with a bundled scanner.

- **Migrates** the full contract: path moves, renamed and removed fields, filter changes, async-job semantics, events, and webhooks.

- **Preserves behavior**, keeping synchronous `/enrich` calls synchronous unless you already orchestrate async work, and adding polling and input-limit handling where a job needs it.

- **Validates** the result by updating tests and rescanning for any v1 references left behind, with file locations.

Installation is a single unzip into your skills directory. In Claude Code, the whole migration is one command:

```
`/agentsource-v1-v2-upgrade Migrate this project's AgentSource integration from v1 to v2.`
```

Review the diff, run your tests, and commit once both your own suite and the skill's residual-v1 scanner pass. The [upgrade skill page](https://developers.explorium.ai/v2/upgrade-skill) has the download and setup steps for each agent, and the [migration guide](https://developers.explorium.ai/v2/migration-from-v1) remains the reference if you prefer to do it by hand.

## AgentSource in HubSpot's Agent Builder

HubSpot's Agent Hub lets teams build their own agents on top of their CRM, and those agents are only as good as the data they can reach. Explorium now ships as an MCP connector for HubSpot, so agents you build in Agent Builder can match, enrich, and research companies and contacts with Explorium data without leaving HubSpot.

Once connected, it appears as **AgentSource by Explorium** under Settings → Integrations → Connected Apps. In Agent Builder, open Configure, choose Add tool, and pick the Explorium connector under MCP Servers. Typical uses: enriching a newly created contact before routing it, checking firmographics before an agent drafts outreach, or pulling a short list of lookalike accounts into a workflow.

You need a HubSpot Super Admin seat and Agent Hub enabled in your portal (Settings → AI). The connector is in early access ahead of a HubSpot Marketplace listing, so if you want it in your portal, [get in touch](https://www.explorium.ai/about/#contact) and we will get you connected.

## Explorium is compliant with DROP

Explorium is now compliant with California's Delete Request and Opt-out Platform (DROP). Established under the state's Delete Act, DROP gives Californians a single, streamlined mechanism to request deletion of their personal information or opt out of certain data uses, and requires registered data brokers to honor those requests through the platform.

We have the processes in place to meet these requirements efficiently and responsibly, with privacy protections embedded in how we collect, manage, and refresh data. For customers, nothing changes in how you use AgentSource. What it does mean is that the data your agents rely on is maintained under a framework built for accountability, which matters more as agents start acting on data automatically. Quality data and responsible data practices go hand in hand, and we will keep sharing updates as regulation evolves.

## Fresher prospect data

Data quality is never a one-time project, and this month it showed. We completed a significant refresh of our prospect contact data, which now reflects the most current professional profile information we have had in a long time: current titles, current employers, and updated locations as people change roles and move companies.

Alongside it, the business entity graph grew and was refreshed:

- Total business entities up from 117.6M to 118.2M, a net gain of roughly 513K companies.

- LinkedIn profile metrics refreshed for about 23M companies.

- Locality coverage improved for roughly 2M businesses and region coverage for 1.75M, and country coverage now stands at 97.9%.

In practice this means fewer bounced emails to people who have left, fewer stale job titles in your sequences, and better matching when your agent looks someone up by name and company. No action is needed on your side. The refreshed data is already available through every AgentSource endpoint.

## Get started

Read the [AgentSource v2 documentation](https://developers.explorium.ai/v2/overview), install the [upgrade skill](https://developers.explorium.ai/v2/upgrade-skill), or [talk to us](https://www.explorium.ai/about/#contact) about the HubSpot connector.