Skip to content

Network tools your agent already has

The web is where most answers are. These are what your agent uses to reach it and check what came back.

17 tools

Fetching a page, calling an API, resolving a name, checking whether something is actually up. Agents spend a lot of their time on the other end of a request, and having proper tools for it is the difference between reporting a failure and diagnosing one.

The tools

Preinstalled on every plan, with nothing to set up. A few depend on the engine you pick.

  • curl

    Make HTTP requests, post payloads and follow redirects.

  • wget

    Download files and mirror pages over HTTP and FTP.

  • nc

    Netcat. Open, listen on and test raw TCP connections.

  • socat

    Bridge sockets, files and ports between two endpoints.

  • dig

    Query DNS records and trace how a name resolves.

  • nslookup

    Look up a hostname or an address against a resolver.

  • host

    Quick DNS lookups for a name or an IP address.

  • ip

    Inspect the addresses, routes and links on the machine.

  • ss

    List the sockets, ports and connections open on the machine.

  • naabu

    Fast port discovery on hosts you are authorised to scan.

  • websocat

    Connect to a WebSocket endpoint and send or read frames.

  • ddgs

    Search the web from the shell and get results back as text or JSON.

  • xh

    Send HTTP requests with HTTPie syntax and readable output.

  • grpcurl

    Call gRPC services and list their methods from the shell.

  • oha

    Load-test an HTTP endpoint and report latency percentiles.

  • hurl

    Run HTTP requests and assertions written as a plain text file.

  • doggo

    Look up DNS records and get the answer back as JSON.

Get started

A real command line, already set up

Every agent runs on a sandboxed machine with the whole toolbox preinstalled. No setup step, on any plan.