Integration

Connect Stripe to IP2Location

When New Charge fires in Stripe, your agent runs Lookup domain WHOIS in IP2Location. Describe the whole flow and it is built, tested on every scenario and kept running.

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

Build solutions, not workarounds.

What do you want Stripe and IP2Location to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

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)
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)
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)
Zed

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

Setup guide (opens in a new tab)
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)
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)

Stripe tells you a payment happened; IP2Location tells you where it came from. Joining them lets a team look up the geolocation, network and proxy details behind a charge, customer or subscription, and write what comes back onto the Stripe customer record so billing and support see the same context. Domain WHOIS lookups work the same way for business email addresses.

Example flows

What Stripe can start in IP2Location

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 Stripe and IP2Location

Triggers and actions 11 triggers · 24 actions

Each app on its own

Reviews

What our customers say

More from Stripe

More into IP2Location

Questions

Stripe and IP2Location, answered

Can IP2Location start one of these scenarios?

No, IP2Location only offers lookups, so every scenario here begins with a Stripe trigger such as a new charge, customer, invoice, subscription or refund. IP2Location is then asked for geolocation, proxy or WHOIS details.

Where does the IP address for the lookup come from?

It comes from the Stripe record itself, for example the IP stored with a charge or kept in customer metadata, and that value is passed to the IP2Location geolocation lookup. If no IP is present, the agent can fall back to a WHOIS lookup on the billing email's domain instead.

What can start an automation from Stripe?

Any of Stripe's 11 triggers in the catalog, including New Charge, New Charge (instant), New Customer and New Invoice. Describe the moment in plain language and your agent picks the right one.

What can your agent do in IP2Location when something happens in Stripe?

Any of IP2Location's 3 actions, including Lookup domain WHOIS, Lookup IP geolocation and Get my IP details. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from IP2Location to Stripe?

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

Do I have to build a connector for Stripe or IP2Location?

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 Stripe and IP2Location 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.