---
title: "Connect Felt to NameAPI - APIANT.ai"
description: "When \"New or updated map\" fires in Felt, your agent runs \"Detect contact risk\" in NameAPI."
canonical: "https://apiant.ai/connect/felt-to-nameapi"
---

# Connect Felt to NameAPI

When **New or updated map** fires in [Felt](https://apiant.ai/connections/felt), your agent runs **Detect contact risk** in [NameAPI](https://apiant.ai/connections/nameapi). Describe the whole flow and it is built, tested on every scenario and kept running.

Felt **1** trigger NameAPI **7** actions

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

## What do you want Felt and NameAPI 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 Felt can start in NameAPI

- When **New or updated map** in Felt then **Detect contact risk** in NameAPI
- When **New or updated map** in Felt then **Detect disposable email address** in NameAPI

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 Felt and NameAPI

## Triggers and actions 1 trigger · 7 actions

- Trigger

**New or updated map**

Fires when a map is created or edited (annotations drawn/edited, layers updated, comments added/resolved). Delivered via Felt's map:update webhook, attached per-map and created in Felt workspace settings UI (no REST endpoint to register it); verify the felt-signature HMAC header. See /rest-api/listening-to-updates-using-webhooks.

- Action

**Detect contact risk**

Risk Detector: scores a person/email/address record for fake or risky data.

- Action

**Detect disposable email address**

Disposable Email Address Detector: checks whether an email is disposable.

- Action

**Format person name**

Name Formatter: formats a person name (e.g. salutation/full name) per locale.

- Action

**Genderize person name**

Name Genderizer: infers gender from a person name.

- Action

**Match person names**

Name Matcher: compares two person names and returns a match type/confidence.

- Action

**Parse email name**

Email Name Parser: extracts a person name from an email address.

- Action

**Parse person name**

Name Parser: splits a full name into components (given/family names, title, gender).

## Each app on its own

- [ **Felt** Cloud-based GIS platform for creating interactive maps and dashboards from geospatial and database data.](https://apiant.ai/connections/felt)
- [ **NameAPI** API for parsing, genderizing, matching, and formatting personal names.](https://apiant.ai/connections/nameapi)

Reviews

## What our customers say

## More from Felt

- [ **Felt to capture** capture is a service that is your AI's long-term memory.](https://apiant.ai/connect/felt-to-capture)
- [ **Felt to Mapbox** Mapping and geolocation platform offering interactive maps, geocoding, routing, and navigation APIs.](https://apiant.ai/connect/felt-to-mapbox)
- [ **Felt to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/felt-to-hubspot)
- [ **Felt to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/felt-to-salesforce)
- [ **Felt to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/felt-to-slack)
- [ **Felt to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/felt-to-google-sheets)

## More into NameAPI

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

Questions

## Felt and NameAPI, answered

###

### What can start an automation from Felt?

Any of Felt's 1 trigger in the catalog, including New or updated map. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in NameAPI when something happens in Felt?

Any of NameAPI's 7 actions, including Detect contact risk, Detect disposable email address, Format person name and Genderize person name. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from NameAPI to Felt?

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

###

### Do I have to build a connector for Felt or NameAPI?

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 Felt and NameAPI without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in NameAPI 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.
