# Connect Particle to Auto.dev

When **New device event (instant)** fires in [Particle](https://apiant.ai/connections/particle), your agent runs **Decode VIN** in [Auto.dev](https://apiant.ai/connections/auto-dev). Describe the whole flow and it is built, tested on every scenario and kept running.

Particle **1** trigger Particle **5** actions Auto.dev **3** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Particle and Auto.dev to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Particle can start in Auto.dev

- When **New device event (instant)** in Particle then **Decode VIN** in Auto.dev
- When **New device event (instant)** in Particle then **List vehicle listings** in Auto.dev

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Particle and Auto.dev

## Triggers and actions 1 trigger · 8 actions

- Trigger

**New device event (instant)**

Fires when a matching device event is published, delivered via a Particle webhook integration.

- Action

**Execute a logic function**

Run a configured Particle Logic function and return its result.

- Action

**Get ledger instance**

Retrieve the current data for a ledger instance (shared cloud/device key-value state).

- Action

**List devices**

List all devices in your account or product fleet.

- Action

**Publish an event**

Publish a custom event to the device cloud so other devices or integrations can subscribe to it.

- Action

**Set ledger instance data**

Update the data stored in a ledger instance.

- Action

**Decode VIN**

Decodes a vehicle identification number (VIN) and returns the vehicle's make, model, trim, year, engine, drivetrain and other details.

- Action

**List vehicle listings**

Returns active marketplace listings for a vehicle, identified by its VIN, with real-time pricing and availability.

- Action

**List vehicle photos**

Returns the photo gallery image URLs available for a vehicle, identified by its VIN.

## Each app on its own

- [ **Particle** Particle is an Internet of Things (IoT) device platform that enables businesses to easily add the power of...](https://apiant.ai/connections/particle)
- [ **Auto.dev** VIN decode, vehicle listings, payments, recalls, specs via REST API, CLI, SDK, or MCP](https://apiant.ai/connections/auto-dev)

Reviews

## What our customers say

## More from Particle

- [ **Particle to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/particle-to-salesforce)
- [ **Particle to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/particle-to-slack)
- [ **Particle to Google Sheets** Google Sheets](https://apiant.ai/connect/particle-to-google-sheets)
- [ **Particle to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/particle-to-stripe)
- [ **Particle to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/particle-to-shopify)
- [ **Particle to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/particle-to-quickbooks-online)

## More into Auto.dev

- [ **HubSpot to Auto.dev** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-auto-dev)
- [ **Salesforce to Auto.dev** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-auto-dev)
- [ **Slack to Auto.dev** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-auto-dev)
- [ **Google Sheets to Auto.dev** Google Sheets](https://apiant.ai/connect/google-sheets-to-auto-dev)
- [ **Gmail to Auto.dev** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-auto-dev)
- [ **Google Calendar to Auto.dev** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-auto-dev)

Questions

## Particle and Auto.dev, answered

###

### What can start an automation from Particle?

Any of Particle's 1 trigger in the catalog, including New device event (instant). Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Auto.dev when something happens in Particle?

Any of Auto.dev's 3 actions, including Decode VIN, List vehicle listings and List vehicle photos. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Auto.dev to Particle?

Auto.dev has no triggers in the catalog today, so automations start in Particle. If you need the other direction, ask: your agent reads Auto.dev's API documentation and adds it.

###

### Do I have to build a connector for Particle or Auto.dev?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
