--- title: "IBM NS1 Connect MCP server for AI agents - actionlake" description: "Give Claude 186 IBM NS1 Connect actions through one MCP server: rum decisions, alerts. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/ibm-ns1-connect updated: 2026-10-23 --- 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](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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` the first call ``` do { action: "ns1_connect.users.list", intent: "check which IBM NS1 Connect account is connected" } # List account users · read · 1 upstream call ``` - 186 actions in one signed file - 104 read look, never change - 59 write create and update - 23 wait for a yes destructive, confirmed first Set up ## Connect IBM NS1 Connect in three steps. 1. 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` 2. 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_key` NS1 Connect API key ``` account { op: "connections.requirements", service: "ns1_connect" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### 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 call check { 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 2026[developer.ibm.com](https://developer.ibm.com/apis/catalog/ns1--ibm-ns1-connect-api/Introduction) **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. - **104** read look, never change - **59** write create and update - **23** destructive wait for a confirmation 1. ### Rum decisions 10 10 read · 0 write · 0 destructive Decisions by Area · Decisions by ASN · Decisions by Records · Get Filter by time 2. ### Alerts 7 2 read · 4 write · 1 destructive List configured alerts · View alert details · Create an alert · Edit alert details 3. ### 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 4. ### 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 5. ### Usage 7 7 read · 0 write · 0 destructive Account-wide usage statistics · Traffic usage by network · Usage for a record · Traffic usage by region 6. ### Zones 7 4 read · 2 write · 1 destructive List zones · View zone details · Create a DNS zone · List of linked zones 7. ### 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 8. ### 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. 1. Read read Which IBM NS1 Connect alerts are open right now? Group them by service. calls `ns1_connect.alerts.list` 2. Write write Create new user in IBM NS1 Connect. Show me exactly what you will send before you save it. calls `ns1_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 user `ns1_connect.users.delete` - Delete a team `ns1_connect.teams.delete` - Delete a monitoring job `ns1_connect.monitoring_jobs.delete` - Delete an API key `ns1_connect.api_keys.delete` - Delete an alert `ns1_connect.alerts.delete` - Delete a notifier list `ns1_connect.notifier_lists.delete` - Delete a record `ns1_connect.records.delete` - Delete a zone `ns1_connect.zones.delete` - Revoke an SSL/TLS certificate `ns1_connect.redirect_certificates.revoke` - Delete a data set `ns1_connect.datasets.delete` - Delete a Pulsar application `ns1_connect.rum_apps.delete` - Delete a URL redirect `ns1_connect.redirects.delete` - Delete a data feed `ns1_connect.data_feeds.delete` - Delete a route map `ns1_connect.route_maps.delete` - Delete data source `ns1_connect.data_sources.delete` - Delete a Pulsar job `ns1_connect.rum_app_jobs.delete` - Delete zone version `ns1_connect.zone_versions.delete` - Delete data sink `ns1_connect.insights_sinks.delete` - Reset two-factor authentication (2FA) `ns1_connect.two_factor.reset_user` - Delete API key secret `ns1_connect.api_key_secrets.delete` - Delete team IP allow list `ns1_connect.team_ip_allow_list.delete` - Delete IP allow list `ns1_connect.account_ip_allow_list.delete` - Delete an external DNSSEC key set `ns1_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. do ns1_connect.users.delete confirm_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: "lead@example.com" }, { match: "ns1_connect.teams.delete", approver: "lead@example.com" }, { match: "ns1_connect.monitoring_jobs.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 186 IBM NS1 Connect actions - 186 actions page each page of a long list is one call - 100 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every IBM NS1 Connect action. 186 actions by area: the id your agent calls, what it does, and its effect. **Rum decisions 10** - `ns1_connect.rum_decisions.by_area` Decisions by Area read - `ns1_connect.rum_decisions.by_asn` Decisions by ASN read - `ns1_connect.rum_decisions.by_record` Decisions by Records read - `ns1_connect.rum_decisions.filters_by_time` Get Filter by time read - `ns1_connect.rum_decisions.get` Decisions read - `ns1_connect.rum_decisions.graph_by_region` Decisions Graph by Region read - `ns1_connect.rum_decisions.graph_by_time` Decisions Graph by Time read - `ns1_connect.rum_decisions.results_by_area` Get Decisions Results data for one or multiple Pulsar Jobs read - `ns1_connect.rum_decisions.results_by_record` Decisions by Results Record read - `ns1_connect.rum_decisions.results_by_time` Get Decisions results data read **Alerts 7** - `ns1_connect.alerts.create` Create an alert write - `ns1_connect.alerts.delete` Delete an alert destructive - `ns1_connect.alerts.get` View alert details read - `ns1_connect.alerts.list` List configured alerts read - `ns1_connect.alerts.replace` Replace an alert write - `ns1_connect.alerts.test` Trigger test of alert write - `ns1_connect.alerts.update` Edit alert details write **Billing usage 7** - `ns1_connect.billing_usage.decisions` View Pulsar decision usage read - `ns1_connect.billing_usage.filter_chains` View number of Filter Chains used read - `ns1_connect.billing_usage.limits` View account usage limits read - `ns1_connect.billing_usage.monitors` View number of monitors used read - `ns1_connect.billing_usage.queries` View incoming query usage details read - `ns1_connect.billing_usage.records` View number of records used read - `ns1_connect.billing_usage.redirects` View number of redirects used read **Rum app jobs 7** - `ns1_connect.rum_app_jobs.create` Create a Pulsar job write - `ns1_connect.rum_app_jobs.delete` Delete a Pulsar job destructive - `ns1_connect.rum_app_jobs.get` View Pulsar job details read - `ns1_connect.rum_app_jobs.get_availability` Get Availability Data read - `ns1_connect.rum_app_jobs.get_data` View aggregated performance data read - `ns1_connect.rum_app_jobs.list` View all jobs within a Pulsar application read - `ns1_connect.rum_app_jobs.update` Edit a Pulsar job write **Usage 7** - `ns1_connect.usage.get` Account-wide usage statistics read - `ns1_connect.usage.get_by_network` Traffic usage by network read - `ns1_connect.usage.get_by_record` Usage for a record read - `ns1_connect.usage.get_by_region` Traffic usage by region read - `ns1_connect.usage.get_by_zone` Usage in a zone read - `ns1_connect.usage.get_redirect` Redirect usage stats for a configuration read - `ns1_connect.usage.get_redirects` Redirect usage stats read **Zones 7** - `ns1_connect.zones.create` Create a DNS zone write - `ns1_connect.zones.delete` Delete a zone destructive - `ns1_connect.zones.get` View zone details read - `ns1_connect.zones.list` List zones read - `ns1_connect.zones.list_linked` List of linked zones read - `ns1_connect.zones.search` Search DNS zones read - `ns1_connect.zones.update` Edit a zone write **API key secrets 6** - `ns1_connect.api_key_secrets.delete` Delete API key secret destructive - `ns1_connect.api_key_secrets.get` View API key secret details read - `ns1_connect.api_key_secrets.get_self` View current API key secret details read - `ns1_connect.api_key_secrets.renew` Generate new API key secret write - `ns1_connect.api_key_secrets.renew_self` Generate new secret for current API key write - `ns1_connect.api_key_secrets.update` Edit API key secret write **Data sources 6** - `ns1_connect.data_sources.create` Create a new data source write - `ns1_connect.data_sources.delete` Delete data source destructive - `ns1_connect.data_sources.get` View data source details read - `ns1_connect.data_sources.list` List data sources read - `ns1_connect.data_sources.publish` Publish data from a data source write - `ns1_connect.data_sources.update` Edit data source write **Redirects 6** - `ns1_connect.redirects.create` Create a new URL redirect write - `ns1_connect.redirects.delete` Delete a URL redirect destructive - `ns1_connect.redirects.get` View URL redirect details read - `ns1_connect.redirects.import_csv` Import URL redirect configurations write - `ns1_connect.redirects.list` List all URL redirects read - `ns1_connect.redirects.update` Edit URL redirect details write **Route maps 6** - `ns1_connect.route_maps.create` Create a route map write - `ns1_connect.route_maps.delete` Delete a route map destructive - `ns1_connect.route_maps.get` View route map details read - `ns1_connect.route_maps.list` View route maps read - `ns1_connect.route_maps.replace` Replace a route map write - `ns1_connect.route_maps.update_meta` Rename a route map write **Users 6** - `ns1_connect.users.create` Create new user write - `ns1_connect.users.create_by_username` Create new user write - `ns1_connect.users.delete` Remove user destructive - `ns1_connect.users.get` View user details read - `ns1_connect.users.list` List account users read - `ns1_connect.users.update` Edit user details write **Account ip allow list 5** - `ns1_connect.account_ip_allow_list.create` Create IP allow list record write - `ns1_connect.account_ip_allow_list.delete` Delete IP allow list destructive - `ns1_connect.account_ip_allow_list.get` View IP allow list details read - `ns1_connect.account_ip_allow_list.list` View global IP allow list records read - `ns1_connect.account_ip_allow_list.update` Edit global IP allow list write **API keys 5** - `ns1_connect.api_keys.create` Create API key write - `ns1_connect.api_keys.delete` Delete an API key destructive - `ns1_connect.api_keys.get` View API key details read - `ns1_connect.api_keys.list` List API keys read - `ns1_connect.api_keys.update` Edit API key write **Data feeds 5** - `ns1_connect.data_feeds.create` Configure a new data feed from a data source write - `ns1_connect.data_feeds.delete` Delete a data feed destructive - `ns1_connect.data_feeds.get` View data feed details read - `ns1_connect.data_feeds.list` View active data feeds from a data source read - `ns1_connect.data_feeds.update` Edit data feed write **Insights sinks 5** - `ns1_connect.insights_sinks.create` Create a data sink write - `ns1_connect.insights_sinks.delete` Delete data sink destructive - `ns1_connect.insights_sinks.get` View data sink configuration read - `ns1_connect.insights_sinks.list` List data sinks read - `ns1_connect.insights_sinks.update` Update data sink configuration write **Monitoring jobs 5** - `ns1_connect.monitoring_jobs.create` Create a monitoring job write - `ns1_connect.monitoring_jobs.delete` Delete a monitoring job destructive - `ns1_connect.monitoring_jobs.get` View monitoring job details read - `ns1_connect.monitoring_jobs.list` List all monitoring jobs read - `ns1_connect.monitoring_jobs.update` Edit a monitoring job write **Notifier lists 5** - `ns1_connect.notifier_lists.create` Create a notifier list write - `ns1_connect.notifier_lists.delete` Delete a notifier list destructive - `ns1_connect.notifier_lists.get` View notifier list details read - `ns1_connect.notifier_lists.list` View all notifier lists read - `ns1_connect.notifier_lists.update` Edit a notifier list write **Records 5** - `ns1_connect.records.create` Create a record write - `ns1_connect.records.delete` Delete a record destructive - `ns1_connect.records.get` View record details read - `ns1_connect.records.search` Search DNS records read - `ns1_connect.records.update` Edit a record write **Redirect certificates 5** - `ns1_connect.redirect_certificates.create` Request an SSL/TLS certificate write - `ns1_connect.redirect_certificates.get` View SSL/TLS certificate details read - `ns1_connect.redirect_certificates.list` View all SSL/TLS certificates read - `ns1_connect.redirect_certificates.renew` Renew an SSL/TLS certificate write - `ns1_connect.redirect_certificates.revoke` Revoke an SSL/TLS certificate destructive **Rum apps 5** - `ns1_connect.rum_apps.create` Create a Pulsar application write - `ns1_connect.rum_apps.delete` Delete a Pulsar application destructive - `ns1_connect.rum_apps.get` View Pulsar application details read - `ns1_connect.rum_apps.list` View all Pulsar applications read - `ns1_connect.rum_apps.update` Edit a Pulsar application by its unique AppID write **Team ip allow list 5** - `ns1_connect.team_ip_allow_list.create` Create team IP allow list write - `ns1_connect.team_ip_allow_list.delete` Delete team IP allow list destructive - `ns1_connect.team_ip_allow_list.get` View team IP allow list details read - `ns1_connect.team_ip_allow_list.list` List team IP allow lists read - `ns1_connect.team_ip_allow_list.update` Edit team IP allow list write **Teams 5** - `ns1_connect.teams.create` Create new team write - `ns1_connect.teams.delete` Delete a team destructive - `ns1_connect.teams.get` View team details read - `ns1_connect.teams.list` List all teams read - `ns1_connect.teams.update` Edit team details write **Zone dnssec external keys 5** - `ns1_connect.zone_dnssec_external_keys.create` Create an external DNSSEC key set write - `ns1_connect.zone_dnssec_external_keys.delete` Delete an external DNSSEC key set destructive - `ns1_connect.zone_dnssec_external_keys.get` View details of an external DNSSEC key set read - `ns1_connect.zone_dnssec_external_keys.list` List all external DNSSEC key sets read - `ns1_connect.zone_dnssec_external_keys.update` Edit an external DNSSEC key set write **Datasets 4** - `ns1_connect.datasets.create` Generate a new data set write - `ns1_connect.datasets.delete` Delete a data set destructive - `ns1_connect.datasets.get` View a generated data set read - `ns1_connect.datasets.list` View all data sets read **Route map stats 4** - `ns1_connect.route_map_stats.hits` View route map hits (account-wide) read - `ns1_connect.route_map_stats.hits_by_record` View route map hits (for a single record) read - `ns1_connect.route_map_stats.misses` View the count of misses for all customer's Route Maps read - `ns1_connect.route_map_stats.misses_by_record` View route map misses (for a single record) read **Two factor 4** - `ns1_connect.two_factor.get` View two-factor authentication (2FA) status read - `ns1_connect.two_factor.reset_user` Reset two-factor authentication (2FA) destructive - `ns1_connect.two_factor.update` Edit two-factor authentication (2FA) status write - `ns1_connect.two_factor.verify` Verify two-factor authentication (2FA) token status write **Zone versions 4** - `ns1_connect.zone_versions.activate` Activate (restore) a zone version write - `ns1_connect.zone_versions.create` Create a new zone version write - `ns1_connect.zone_versions.delete` Delete zone version destructive - `ns1_connect.zone_versions.list` List all zone versions read **DNS networks 3** - `ns1_connect.dns_networks.create` Create a DNS network write - `ns1_connect.dns_networks.list` List available DNS networks read - `ns1_connect.dns_networks.validate` Validate a DNS network write **QPS 3** - `ns1_connect.qps.get` Account-wide DNS queries/second read - `ns1_connect.qps.get_by_record` Queries/sec for a record read - `ns1_connect.qps.get_by_zone` Queries/sec in a zone read **Metadata types 2** - `ns1_connect.metadata_types.list` View metadata fields read - `ns1_connect.metadata_types.list_geo` View geographic-related metadata fields read **Password resets 2** - `ns1_connect.password_resets.complete` Update password write - `ns1_connect.password_resets.request` Create password reset callout write **Rum availability 2** - `ns1_connect.rum_availability.by_area` Get Availability data for one or multiple Pulsar Jobs read - `ns1_connect.rum_availability.by_time` Get availability data for one or multiple Pulsar Jobs read **Rum performance 2** - `ns1_connect.rum_performance.by_area` Get performance data for one or multiple Pulsar Jobs read - `ns1_connect.rum_performance.by_time` Get performance data for one or multiple Pulsar Jobs read **Zone exports 2** - `ns1_connect.zone_exports.create` Initiate a zone file export write - `ns1_connect.zone_exports.get_status` View status of a zone file export read **Account 1** - `ns1_connect.account.get_summary` View account summary read **Activity 1** - `ns1_connect.activity.list` View account activity log read **Alert types 1** - `ns1_connect.alert_types.list` List available alert types read **Data source types 1** - `ns1_connect.data_source_types.list` List data source types read **Dataset reports 1** - `ns1_connect.dataset_reports.send_email` Send data set file to email recipient(s) write **Filter types 1** - `ns1_connect.filter_types.list` View traffic steering filters read **Insights 1** - `ns1_connect.insights.query` View DNS Insights metrics read **Insights sink backends 1** - `ns1_connect.insights_sink_backends.list` List data sink backends read **Monitoring history 1** - `ns1_connect.monitoring_history.list` View monitoring job history read **Monitoring job types 1** - `ns1_connect.monitoring_job_types.list` List monitoring job types read **Monitoring regions 1** - `ns1_connect.monitoring_regions.list` List monitoring regions read **Networks 1** - `ns1_connect.networks.list` List available DNS networks read **Notifier types 1** - `ns1_connect.notifier_types.list` List notifier types read **Redirect logs 1** - `ns1_connect.redirect_logs.list` View URL redirect query log read **Rum jobs 1** - `ns1_connect.rum_jobs.list` Jobs per Customer read **Search 1** - `ns1_connect.search.query` Search zones and records read **Zone backups 1** - `ns1_connect.zone_backups.restore` Restore a zone or record from back-up write **Zone dnssec 1** - `ns1_connect.zone_dnssec.get` Get DNSSEC information read **Zone imports 1** - `ns1_connect.zone_imports.get` Retrieve zone file import job status read 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. ## More connectors like IBM NS1 Connect Shares the most action names with - [Axiom 23](https://actionlake.com/connectors/axiom) - [Sentry 19](https://actionlake.com/connectors/sentry) - [Uptrends 18](https://actionlake.com/connectors/uptrends) - [Cribl 15](https://actionlake.com/connectors/cribl) - [Honeybadger 14](https://actionlake.com/connectors/honeybadger) - [Databricks 10](https://actionlake.com/connectors/databricks) Joins with, on shared entities - [ilert 4](https://actionlake.com/connectors/ilert) - [Commvault Cloud 3](https://actionlake.com/connectors/commvault-cloud) - [Rootly 3](https://actionlake.com/connectors/rootly) - [MongoDB Atlas 3](https://actionlake.com/connectors/mongodb-atlas) - [Site24x7 3](https://actionlake.com/connectors/site24x7) - [FireHydrant 3](https://actionlake.com/connectors/firehydrant) Browse - [All Observability & analytics connectors](https://actionlake.com/connectors/category/observability-and-analytics) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by IBM NS1 Connect; the name is the vendor's own. Counts are from the IBM NS1 Connect service file, version 1.0.0. ## Give your agent IBM NS1 Connect today. [Connect IBM NS1 Connect free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/ibm-ns1-connect More: https://actionlake.com/llms.txt