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 toolsFetching 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.
curlMake HTTP requests, post payloads and follow redirects.
wgetDownload files and mirror pages over HTTP and FTP.
ncNetcat. Open, listen on and test raw TCP connections.
socatBridge sockets, files and ports between two endpoints.
digQuery DNS records and trace how a name resolves.
nslookupLook up a hostname or an address against a resolver.
hostQuick DNS lookups for a name or an IP address.
ipInspect the addresses, routes and links on the machine.
ssList the sockets, ports and connections open on the machine.
naabuFast port discovery on hosts you are authorised to scan.
websocatConnect to a WebSocket endpoint and send or read frames.
ddgsSearch the web from the shell and get results back as text or JSON.
xhSend HTTP requests with HTTPie syntax and readable output.
grpcurlCall gRPC services and list their methods from the shell.
ohaLoad-test an HTTP endpoint and report latency percentiles.
hurlRun HTTP requests and assertions written as a plain text file.
doggoLook up DNS records and get the answer back as JSON.
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.
