Globalping is a global network of probes that allows users to run network tests like ping, traceroute, and DNS resolve from various locations worldwide.
Globalping is a global network of probes that allows users to run network tests like ping, traceroute, and DNS resolve from various locations worldwide. On Nagent, Globalping is exposed as a fully-configurable server monitoring integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Globalping into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Globalping to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Globalping into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Globalping, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GLOBALPING_CREATE_MEASUREMENTTool to create and trigger a network measurement. Use when you need connectivity checks from specific geographic or network locations.
Input parameters
Measurement type to run
Global max probes; mutually exclusive with per-location limit
Publicly reachable target hostname or IP
List of location filters specifying where to run probes. Each filter can use continent, country, city, asn, network, or a 'magic' fuzzy string. Combine filters with '+' in magic (e.g., 'US+AWS'). Defaults to 1 random probe worldwide if omitted.
Stream partial results if true
Options specific to the chosen measurement type
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GLOBALPING_GET_LIMITSTool to retrieve current rate limits and credits. Use this to check remaining API quota before making measurements. Returns rate limits based on IP address for unauthenticated requests or user account for authenticated requests.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GLOBALPING_GET_MEASUREMENTRetrieve measurement results by ID. Use this after creating a measurement to get the status and detailed results from all participating probes. Poll this endpoint until status is 'finished'.
Input parameters
Measurement identifier returned from a create measurement request
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GLOBALPING_HEALTH_CHECKTool to check API health status. Use when verifying API availability.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GLOBALPING_LIST_PROBESRetrieve all currently online Globalping probes worldwide. Returns probe metadata including location (continent, country, city), network information (ASN, ISP name), and tags (datacenter-network, eyeball-network, cloud provider tags). Use max_results parameter to limit response size since the API typically returns ~3500 active probes.
Input parameters
Maximum number of probes to return. The API returns ~3500 active probes by default, so set this to limit the response size (e.g., 10 or 50) for faster processing. Applied as client-side trimming.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 57 agents privately built on Nagent that already use Globalping.
Build on Nagent
Connect Globalping to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Globalping, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Globalping is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Globalping is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Globalping steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Globalping event fires, the agent kicks off automatically.
Every Globalping action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Globalping ships with 5 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Globalping together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Globalping-based workflows tailored to your business.