> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nebulaonchain.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# ping — Nebula Health Check and Connectivity Test

> Verify your agent token is valid and the Nebula Hub is reachable. Takes no parameters and returns an ISO 8601 timestamp on success.

The `ping` tool is a lightweight health check that verifies two things at once: your agent token is valid and the Nebula Hub is reachable. It takes no parameters and returns a confirmation message alongside an ISO 8601 timestamp from the Hub. Use it to sanity-check a new connection, diagnose intermittent failures, or confirm that credentials are wired up correctly before running more complex operations.

## Parameters

`ping` takes no parameters. Pass an empty object `{}` as the tool input.

## Response

On success, `ping` always returns `status: "ok"`.

<ResponseField name="status" type="string">
  Always `"ok"` for a successful ping.
</ResponseField>

<ResponseField name="message" type="string">
  A two-line string: the literal text `Nebula is alive` followed by a newline and the current UTC timestamp in ISO 8601 format (e.g. `2025-01-15T10:23:45.123Z`).
</ResponseField>

## Example

**Call:**

```json theme={null}
{}
```

**Response:**

```json theme={null}
{
  "status": "ok",
  "message": "Nebula is alive\n2025-01-15T10:23:45.123Z"
}
```

## When to use

<Tip>
  Call `ping` immediately after your agent connects to Nebula to confirm that the MCP handshake succeeded and the Hub is healthy before attempting any wallet operations.
</Tip>

Common scenarios:

* **First connection** — verify your `nbl_live_…` token is accepted before building out agent logic.
* **Debugging** — if a more complex tool call is failing unexpectedly, ping first to rule out connectivity or authentication problems.
* **Monitoring** — include `ping` in a periodic health-check loop to detect Hub downtime.