Connectors · Observability & analytics

IBM NS1 Connect MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to IBM NS1 Connect and the rest of your systems. It gives your agent 186 IBM NS1 Connect actions (104 reads, 59 writes and 23 that wait for a confirmation) and holds the IBM NS1 Connect credential itself, so the agent never does. It paces IBM NS1 Connect's limits and records every call.

Connect IBM NS1 Connect free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

186actionsin one signed file
104readlook, never change
59writecreate and update
23wait for a yesdestructive, confirmed first

Set up

Connect IBM NS1 Connect in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect IBM NS1 Connect.
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
- api_keyNS1 Connect API key
```
account { op: "connections.requirements", service: "ns1_connect" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "ns1_connect.users.list" }# list account users · read · 1 upstream callcheck { action: "ns1_connect.users.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

IBM NS1 Connect at a glance

Sign-in: API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide: api_key
Limits we pace to: 10 calls a second, per connection
API covered: IBM NS1 Connect API 1.1.15 (OpenAPI 3.0.3)api.nsone.net
Built from: IBM NS1 Connect's documentation, read 23 October 2026developer.ibm.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 100 of 104 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 4, so ask can line IBM NS1 Connect up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in IBM NS1 Connect.

186 actions in 53 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

104readlook, never change
59writecreate and update
23destructivewait for a confirmation

Rum decisions
10
10 read · 0 write · 0 destructive
Decisions by Area · Decisions by ASN · Decisions by Records · Get Filter by time
Alerts
7
2 read · 4 write · 1 destructive
List configured alerts · View alert details · Create an alert · Edit alert details
Billing usage
7
7 read · 0 write · 0 destructive
View Pulsar decision usage · View number of Filter Chains used · View account usage limits · View number of monitors used
Rum app jobs
7
4 read · 2 write · 1 destructive
View all jobs within a Pulsar application · View Pulsar job details · Get Availability Data · View aggregated performance data
Usage
7
7 read · 0 write · 0 destructive
Account-wide usage statistics · Traffic usage by network · Usage for a record · Traffic usage by region
Zones
7
4 read · 2 write · 1 destructive
List zones · View zone details · Create a DNS zone · List of linked zones
API key secrets
6
2 read · 3 write · 1 destructive
View API key secret details · View current API key secret details · Generate new API key secret · Generate new secret for current API key
Data sources
6
2 read · 3 write · 1 destructive
List data sources · View data source details · Create a new data source · Publish data from a data source

45 more areas · 129 actions

Redirects 6
Route maps 6
Users 6
Account ip allow list 5
API keys 5
Data feeds 5
Insights sinks 5
Monitoring jobs 5
Notifier lists 5
Records 5
Redirect certificates 5
Rum apps 5
Team ip allow list 5
Teams 5
Zone dnssec external keys 5
Datasets 4
Route map stats 4
Two factor 4
Zone versions 4
DNS networks 3
QPS 3
Metadata types 2
Password resets 2
Rum availability 2
Rum performance 2
Zone exports 2
Account 1
Activity 1
Alert types 1
Data source types 1
Dataset reports 1
Filter types 1
Insights 1
Insights sink backends 1
Monitoring history 1
Monitoring job types 1
Monitoring regions 1
Networks 1
Notifier types 1
Redirect logs 1
Rum jobs 1
Search 1
Zone backups 1
Zone dnssec 1
Zone imports 1

Top actions

The IBM NS1 Connect API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 46 of IBM NS1 Connect's 48 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`ns1_connect.users.list`List account users	List account users.	read	`identity.user.list`474 connectors
`ns1_connect.teams.list`List all teams	List all teams.	read	`identity.group.list`262 connectors
`ns1_connect.users.get`View user details	View user details.	read	`identity.user.get`399 connectors
`ns1_connect.teams.get`View team details	View team details.	read	`identity.group.get`212 connectors
`ns1_connect.alerts.list`List configured alerts	List configured alerts.	read	`monitoring.alert.list`51 connectors
`ns1_connect.monitoring_jobs.list`List all monitoring jobs	List all monitoring jobs.	read	`monitoring.monitor.list`32 connectors
`ns1_connect.users.create`Create new user	Create new user.	write	`identity.user.create`262 connectors
`ns1_connect.teams.create`Create new team	Create new team.	write	`identity.group.create`205 connectors
`ns1_connect.users.update`Edit user details	Edit user details.	write	`identity.user.update`280 connectors
`ns1_connect.users.delete`Remove user	Remove user.	destructive	`identity.user.delete`253 connectors
`ns1_connect.api_keys.list`List API keys	List API keys.	read	`identity.api_key.list`96 connectors
`ns1_connect.activity.list`View account activity log	View account activity log.	read	`identity.audit_event.list`51 connectors

Try it

Prompts to paste into Claude.

Each one names the IBM NS1 Connect actions it will call, so you know what it reads and what it changes before you send it.

Readread
Which IBM NS1 Connect alerts are open right now? Group them by service.
callsns1_connect.alerts.list
Writewrite
Create new user in IBM NS1 Connect. Show me exactly what you will send before you save it.
callsns1_connect.users.create

Governance for IBM NS1 Connect

Destructive actions wait for a yes.

23 IBM NS1 Connect actions are destructive. These are all of them:

Remove userns1_connect.users.delete
Delete a teamns1_connect.teams.delete
Delete a monitoring jobns1_connect.monitoring_jobs.delete
Delete an API keyns1_connect.api_keys.delete
Delete an alertns1_connect.alerts.delete
Delete a notifier listns1_connect.notifier_lists.delete
Delete a recordns1_connect.records.delete
Delete a zonens1_connect.zones.delete
Revoke an SSL/TLS certificatens1_connect.redirect_certificates.revoke
Delete a data setns1_connect.datasets.delete
Delete a Pulsar applicationns1_connect.rum_apps.delete
Delete a URL redirectns1_connect.redirects.delete
Delete a data feedns1_connect.data_feeds.delete
Delete a route mapns1_connect.route_maps.delete
Delete data sourcens1_connect.data_sources.delete
Delete a Pulsar jobns1_connect.rum_app_jobs.delete
Delete zone versionns1_connect.zone_versions.delete
Delete data sinkns1_connect.insights_sinks.delete
Reset two-factor authentication (2FA)ns1_connect.two_factor.reset_user
Delete API key secretns1_connect.api_key_secrets.delete
Delete team IP allow listns1_connect.team_ip_allow_list.delete
Delete IP allow listns1_connect.account_ip_allow_list.delete
Delete an external DNSSEC key setns1_connect.zone_dnssec_external_keys.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dons1_connect.users.deleteconfirm_policy: human

Remove user?

intent: the user asked me to remove user

run suspended · waiting for a named person · key ns1-connect-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "ns1-connect-agent",  allowed_actions: ["ns1_connect.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "ns1_connect.users.delete", approver: "[email protected]" },    { match: "ns1_connect.teams.delete", approver: "[email protected]" },    { match: "ns1_connect.monitoring_jobs.delete", approver: "[email protected]" }  ]}

Illustrative. Scoped to IBM NS1 Connect only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What IBM NS1 Connect costs on actionlake.

Every IBM NS1 Connect action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call IBM NS1 Connect refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 186 IBM NS1 Connect actions
186actions pageeach page of a long list is one call
100reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every IBM NS1 Connect action.

186 actions by area: the id your agent calls, what it does, and its effect.

Rum decisions10

ns1_connect.rum_decisions.by_areaDecisions by Arearead
ns1_connect.rum_decisions.by_asnDecisions by ASNread
ns1_connect.rum_decisions.by_recordDecisions by Recordsread
ns1_connect.rum_decisions.filters_by_timeGet Filter by timeread
ns1_connect.rum_decisions.getDecisionsread
ns1_connect.rum_decisions.graph_by_regionDecisions Graph by Regionread
ns1_connect.rum_decisions.graph_by_timeDecisions Graph by Timeread
ns1_connect.rum_decisions.results_by_areaGet Decisions Results data for one or multiple Pulsar Jobsread
ns1_connect.rum_decisions.results_by_recordDecisions by Results Recordread
ns1_connect.rum_decisions.results_by_timeGet Decisions results dataread

Alerts7

ns1_connect.alerts.createCreate an alertwrite
ns1_connect.alerts.deleteDelete an alertdestructive
ns1_connect.alerts.getView alert detailsread
ns1_connect.alerts.listList configured alertsread
ns1_connect.alerts.replaceReplace an alertwrite
ns1_connect.alerts.testTrigger test of alertwrite
ns1_connect.alerts.updateEdit alert detailswrite

Billing usage7

ns1_connect.billing_usage.decisionsView Pulsar decision usageread
ns1_connect.billing_usage.filter_chainsView number of Filter Chains usedread
ns1_connect.billing_usage.limitsView account usage limitsread
ns1_connect.billing_usage.monitorsView number of monitors usedread
ns1_connect.billing_usage.queriesView incoming query usage detailsread
ns1_connect.billing_usage.recordsView number of records usedread
ns1_connect.billing_usage.redirectsView number of redirects usedread

Rum app jobs7

ns1_connect.rum_app_jobs.createCreate a Pulsar jobwrite
ns1_connect.rum_app_jobs.deleteDelete a Pulsar jobdestructive
ns1_connect.rum_app_jobs.getView Pulsar job detailsread
ns1_connect.rum_app_jobs.get_availabilityGet Availability Dataread
ns1_connect.rum_app_jobs.get_dataView aggregated performance dataread
ns1_connect.rum_app_jobs.listView all jobs within a Pulsar applicationread
ns1_connect.rum_app_jobs.updateEdit a Pulsar jobwrite

Usage7

ns1_connect.usage.getAccount-wide usage statisticsread
ns1_connect.usage.get_by_networkTraffic usage by networkread
ns1_connect.usage.get_by_recordUsage for a recordread
ns1_connect.usage.get_by_regionTraffic usage by regionread
ns1_connect.usage.get_by_zoneUsage in a zoneread
ns1_connect.usage.get_redirectRedirect usage stats for a configurationread
ns1_connect.usage.get_redirectsRedirect usage statsread

Zones7

ns1_connect.zones.createCreate a DNS zonewrite
ns1_connect.zones.deleteDelete a zonedestructive
ns1_connect.zones.getView zone detailsread
ns1_connect.zones.listList zonesread
ns1_connect.zones.list_linkedList of linked zonesread
ns1_connect.zones.searchSearch DNS zonesread
ns1_connect.zones.updateEdit a zonewrite

API key secrets6

ns1_connect.api_key_secrets.deleteDelete API key secretdestructive
ns1_connect.api_key_secrets.getView API key secret detailsread
ns1_connect.api_key_secrets.get_selfView current API key secret detailsread
ns1_connect.api_key_secrets.renewGenerate new API key secretwrite
ns1_connect.api_key_secrets.renew_selfGenerate new secret for current API keywrite
ns1_connect.api_key_secrets.updateEdit API key secretwrite

Data sources6

ns1_connect.data_sources.createCreate a new data sourcewrite
ns1_connect.data_sources.deleteDelete data sourcedestructive
ns1_connect.data_sources.getView data source detailsread
ns1_connect.data_sources.listList data sourcesread
ns1_connect.data_sources.publishPublish data from a data sourcewrite
ns1_connect.data_sources.updateEdit data sourcewrite

Redirects6

ns1_connect.redirects.createCreate a new URL redirectwrite
ns1_connect.redirects.deleteDelete a URL redirectdestructive
ns1_connect.redirects.getView URL redirect detailsread
ns1_connect.redirects.import_csvImport URL redirect configurationswrite
ns1_connect.redirects.listList all URL redirectsread
ns1_connect.redirects.updateEdit URL redirect detailswrite

Route maps6

ns1_connect.route_maps.createCreate a route mapwrite
ns1_connect.route_maps.deleteDelete a route mapdestructive
ns1_connect.route_maps.getView route map detailsread
ns1_connect.route_maps.listView route mapsread
ns1_connect.route_maps.replaceReplace a route mapwrite
ns1_connect.route_maps.update_metaRename a route mapwrite

Users6

ns1_connect.users.createCreate new userwrite
ns1_connect.users.create_by_usernameCreate new userwrite
ns1_connect.users.deleteRemove userdestructive
ns1_connect.users.getView user detailsread
ns1_connect.users.listList account usersread
ns1_connect.users.updateEdit user detailswrite

Account ip allow list5

ns1_connect.account_ip_allow_list.createCreate IP allow list recordwrite
ns1_connect.account_ip_allow_list.deleteDelete IP allow listdestructive
ns1_connect.account_ip_allow_list.getView IP allow list detailsread
ns1_connect.account_ip_allow_list.listView global IP allow list recordsread
ns1_connect.account_ip_allow_list.updateEdit global IP allow listwrite

API keys5

ns1_connect.api_keys.createCreate API keywrite
ns1_connect.api_keys.deleteDelete an API keydestructive
ns1_connect.api_keys.getView API key detailsread
ns1_connect.api_keys.listList API keysread
ns1_connect.api_keys.updateEdit API keywrite

Data feeds5

ns1_connect.data_feeds.createConfigure a new data feed from a data sourcewrite
ns1_connect.data_feeds.deleteDelete a data feeddestructive
ns1_connect.data_feeds.getView data feed detailsread
ns1_connect.data_feeds.listView active data feeds from a data sourceread
ns1_connect.data_feeds.updateEdit data feedwrite

Insights sinks5

ns1_connect.insights_sinks.createCreate a data sinkwrite
ns1_connect.insights_sinks.deleteDelete data sinkdestructive
ns1_connect.insights_sinks.getView data sink configurationread
ns1_connect.insights_sinks.listList data sinksread
ns1_connect.insights_sinks.updateUpdate data sink configurationwrite

Monitoring jobs5

ns1_connect.monitoring_jobs.createCreate a monitoring jobwrite
ns1_connect.monitoring_jobs.deleteDelete a monitoring jobdestructive
ns1_connect.monitoring_jobs.getView monitoring job detailsread
ns1_connect.monitoring_jobs.listList all monitoring jobsread
ns1_connect.monitoring_jobs.updateEdit a monitoring jobwrite

Notifier lists5

ns1_connect.notifier_lists.createCreate a notifier listwrite
ns1_connect.notifier_lists.deleteDelete a notifier listdestructive
ns1_connect.notifier_lists.getView notifier list detailsread
ns1_connect.notifier_lists.listView all notifier listsread
ns1_connect.notifier_lists.updateEdit a notifier listwrite

Records5

ns1_connect.records.createCreate a recordwrite
ns1_connect.records.deleteDelete a recorddestructive
ns1_connect.records.getView record detailsread
ns1_connect.records.searchSearch DNS recordsread
ns1_connect.records.updateEdit a recordwrite

Redirect certificates5

ns1_connect.redirect_certificates.createRequest an SSL/TLS certificatewrite
ns1_connect.redirect_certificates.getView SSL/TLS certificate detailsread
ns1_connect.redirect_certificates.listView all SSL/TLS certificatesread
ns1_connect.redirect_certificates.renewRenew an SSL/TLS certificatewrite
ns1_connect.redirect_certificates.revokeRevoke an SSL/TLS certificatedestructive

Rum apps5

ns1_connect.rum_apps.createCreate a Pulsar applicationwrite
ns1_connect.rum_apps.deleteDelete a Pulsar applicationdestructive
ns1_connect.rum_apps.getView Pulsar application detailsread
ns1_connect.rum_apps.listView all Pulsar applicationsread
ns1_connect.rum_apps.updateEdit a Pulsar application by its unique AppIDwrite

Team ip allow list5

ns1_connect.team_ip_allow_list.createCreate team IP allow listwrite
ns1_connect.team_ip_allow_list.deleteDelete team IP allow listdestructive
ns1_connect.team_ip_allow_list.getView team IP allow list detailsread
ns1_connect.team_ip_allow_list.listList team IP allow listsread
ns1_connect.team_ip_allow_list.updateEdit team IP allow listwrite

Teams5

ns1_connect.teams.createCreate new teamwrite
ns1_connect.teams.deleteDelete a teamdestructive
ns1_connect.teams.getView team detailsread
ns1_connect.teams.listList all teamsread
ns1_connect.teams.updateEdit team detailswrite

Zone dnssec external keys5

ns1_connect.zone_dnssec_external_keys.createCreate an external DNSSEC key setwrite
ns1_connect.zone_dnssec_external_keys.deleteDelete an external DNSSEC key setdestructive
ns1_connect.zone_dnssec_external_keys.getView details of an external DNSSEC key setread
ns1_connect.zone_dnssec_external_keys.listList all external DNSSEC key setsread
ns1_connect.zone_dnssec_external_keys.updateEdit an external DNSSEC key setwrite

Datasets4

ns1_connect.datasets.createGenerate a new data setwrite
ns1_connect.datasets.deleteDelete a data setdestructive
ns1_connect.datasets.getView a generated data setread
ns1_connect.datasets.listView all data setsread

Route map stats4

ns1_connect.route_map_stats.hitsView route map hits (account-wide)read
ns1_connect.route_map_stats.hits_by_recordView route map hits (for a single record)read
ns1_connect.route_map_stats.missesView the count of misses for all customer's Route Mapsread
ns1_connect.route_map_stats.misses_by_recordView route map misses (for a single record)read

Two factor4

ns1_connect.two_factor.getView two-factor authentication (2FA) statusread
ns1_connect.two_factor.reset_userReset two-factor authentication (2FA)destructive
ns1_connect.two_factor.updateEdit two-factor authentication (2FA) statuswrite
ns1_connect.two_factor.verifyVerify two-factor authentication (2FA) token statuswrite

Zone versions4

ns1_connect.zone_versions.activateActivate (restore) a zone versionwrite
ns1_connect.zone_versions.createCreate a new zone versionwrite
ns1_connect.zone_versions.deleteDelete zone versiondestructive
ns1_connect.zone_versions.listList all zone versionsread

DNS networks3

ns1_connect.dns_networks.createCreate a DNS networkwrite
ns1_connect.dns_networks.listList available DNS networksread
ns1_connect.dns_networks.validateValidate a DNS networkwrite

QPS3

ns1_connect.qps.getAccount-wide DNS queries/secondread
ns1_connect.qps.get_by_recordQueries/sec for a recordread
ns1_connect.qps.get_by_zoneQueries/sec in a zoneread

Metadata types2

ns1_connect.metadata_types.listView metadata fieldsread
ns1_connect.metadata_types.list_geoView geographic-related metadata fieldsread

Password resets2

ns1_connect.password_resets.completeUpdate passwordwrite
ns1_connect.password_resets.requestCreate password reset calloutwrite

Rum availability2

ns1_connect.rum_availability.by_areaGet Availability data for one or multiple Pulsar Jobsread
ns1_connect.rum_availability.by_timeGet availability data for one or multiple Pulsar Jobsread

Rum performance2

ns1_connect.rum_performance.by_areaGet performance data for one or multiple Pulsar Jobsread
ns1_connect.rum_performance.by_timeGet performance data for one or multiple Pulsar Jobsread

Zone exports2

ns1_connect.zone_exports.createInitiate a zone file exportwrite
ns1_connect.zone_exports.get_statusView status of a zone file exportread

Account1

ns1_connect.account.get_summaryView account summaryread

Activity1

ns1_connect.activity.listView account activity logread

Alert types1

ns1_connect.alert_types.listList available alert typesread

Data source types1

ns1_connect.data_source_types.listList data source typesread

Dataset reports1

ns1_connect.dataset_reports.send_emailSend data set file to email recipient(s)write

Filter types1

ns1_connect.filter_types.listView traffic steering filtersread

Insights1

ns1_connect.insights.queryView DNS Insights metricsread

Insights sink backends1

ns1_connect.insights_sink_backends.listList data sink backendsread

Monitoring history1

ns1_connect.monitoring_history.listView monitoring job historyread

Monitoring job types1

ns1_connect.monitoring_job_types.listList monitoring job typesread

Monitoring regions1

ns1_connect.monitoring_regions.listList monitoring regionsread

Networks1

ns1_connect.networks.listList available DNS networksread

Notifier types1

ns1_connect.notifier_types.listList notifier typesread

Redirect logs1

ns1_connect.redirect_logs.listView URL redirect query logread

Rum jobs1

ns1_connect.rum_jobs.listJobs per Customerread

Search1

ns1_connect.search.querySearch zones and recordsread

Zone backups1

ns1_connect.zone_backups.restoreRestore a zone or record from back-upwrite

Zone dnssec1

ns1_connect.zone_dnssec.getGet DNSSEC informationread

Zone imports1

ns1_connect.zone_imports.getRetrieve zone file import job statusread

Questions

The IBM NS1 Connect MCP server, answered.

Is there an IBM NS1 Connect MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 186 IBM NS1 Connect actions across rum decisions, alerts, billing usage and rum app jobs, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by IBM NS1 Connect.

What do I need to connect IBM NS1 Connect?

NS1 Connect API key. The free call account { op: "connections.requirements", service: "ns1_connect" } lists exactly what to paste.

Can an AI agent delete or change things in IBM NS1 Connect?

Only if its key allows it, and only with an explicit confirmation. 23 IBM NS1 Connect actions are destructive, including remove user, delete a team and delete a monitoring job. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my IBM NS1 Connect API limit?

actionlake paces every call to the limits in the IBM NS1 Connect service file: 10 calls a second per connection. Repeated reads are answered from cache (100 IBM NS1 Connect actions can be), which never reaches IBM NS1 Connect.

What does an IBM NS1 Connect action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (186 IBM NS1 Connect actions page). Cache hits, searches, dry runs and calls IBM NS1 Connect refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which IBM NS1 Connect API does it cover?

The IBM NS1 Connect API 1.1.15 (OpenAPI 3.0.3) at api.nsone.net. It is built from IBM NS1 Connect's documentation as read on 23 October 2026. 186 actions in 53 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my IBM NS1 Connect data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your IBM NS1 Connect credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent IBM NS1 Connect today.

Connect IBM NS1 Connect free See pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

IBM NS1 Connect MCP server for AI agents.

Connect IBM NS1 Connect in three steps.

Add actionlake to Claude.

Connect IBM NS1 Connect.

Make the first call. Check before a write.

What an AI agent can do in IBM NS1 Connect.

Rum decisions

Alerts

Billing usage

Rum app jobs

Usage

Zones

API key secrets

Data sources