---
title: "Connect Cartes to VeriRoute Intel - APIANT.ai"
description: "When \"New marker\" fires in Cartes, your agent runs \"Check number trust\" in VeriRoute Intel."
canonical: "https://apiant.ai/connect/cartes-to-veriroute-intel"
---

# Connect Cartes to VeriRoute Intel

When **New marker** fires in [Cartes](https://apiant.ai/connections/cartes), your agent runs **Check number trust** in [VeriRoute Intel](https://apiant.ai/connections/veriroute-intel). Describe the whole flow and it is built, tested on every scenario and kept running.

Cartes **1** trigger Cartes **11** actions VeriRoute Intel **5** actions

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

## What do you want Cartes and VeriRoute Intel to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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 Cartes can start in VeriRoute Intel

- When **New marker** in Cartes then **Check number trust** in VeriRoute Intel
- When **New marker** in Cartes then **Look up LRN** in VeriRoute Intel

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 Cartes and VeriRoute Intel

## Triggers and actions 1 trigger · 16 actions

- Trigger

**New marker**

Triggers when a new marker is added to a Cartes map.

- Action

**Add map**

Creates a new map on Cartes.io and returns it, including the one-time map token needed to edit or delete it.

- Action

**Add marker**

Adds a marker at a latitude and longitude on a Cartes.io map, in an existing or new category.

- Action

**Delete map**

Deletes a map from Cartes.io.

- Action

**Delete marker**

Deletes a marker from a Cartes.io map.

- Action

**Find maps by keyword**

Returns public Cartes.io maps that match a keyword.

- Action

**Get map**

Returns a single Cartes.io map, including its title, description, privacy setting and categories.

- Action

**List categories**

Returns all marker categories available on Cartes.io.

- Action

**List maps**

Returns the public maps on Cartes.io, optionally filtered by ID, category or query.

- Action

**List markers**

Returns all markers on a Cartes.io map, optionally including expired ones.

- Action

**Update map**

Updates the title, description, privacy or marker-creation setting of an existing Cartes.io map.

- Action

**Update marker**

Updates a marker on a Cartes.io map: change its description, or (as the map owner) flag it as spam.

- Action

**Check number trust**

Checks a phone number's trust, spam, robocall and scam risk, returning complaint counts and report dates.

- Action

**Get usage statistics**

Returns lookup counts and costs for your API key over a date range, broken down by product.

- Action

**Look up LRN**

Returns the Local Routing Number, carrier and line type for a phone number, optionally with location, messaging provider, caller name and trust data.

- Action

**Look up messaging provider**

Returns the messaging (SMS) provider for a phone number and whether messaging is enabled.

- Action

**Look up spam**

Checks whether a phone number has been reported as spam, a robocall or a scam.

## Each app on its own

- [ **Cartes** Open-source platform for creating live, community-driven, anonymous maps with custom markers via API.](https://apiant.ai/connections/cartes)
- [ **VeriRoute Intel** CNAM caller ID, carrier/LRN lookup and spam scoring for North American phone numbers](https://apiant.ai/connections/veriroute-intel)

Reviews

## What our customers say

## More from Cartes

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

## More into VeriRoute Intel

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

Questions

## Cartes and VeriRoute Intel, answered

###

### What can start an automation from Cartes?

Any of Cartes's 1 trigger in the catalog, including New marker. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in VeriRoute Intel when something happens in Cartes?

Any of VeriRoute Intel's 5 actions, including Check number trust, Get usage statistics, Look up LRN and Look up messaging provider. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from VeriRoute Intel to Cartes?

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

###

### Do I have to build a connector for Cartes or VeriRoute Intel?

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.

###

### Can my AI client use Cartes and VeriRoute Intel without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### 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.
