yeet.cx valid

yeet

yeet is a network operations platform for agents on Linux, built on eBPF. Teams use yeet to quickly identify and fix network-wide incidents, investigate network behavior at runtime, and build an endless array of products for their bespoke use cases. Instead of buying specialized tools or hiring platform experts, yeet gives every engineer the ability to understand what's happening across their entire network.

For agents: Network operations platform for Linux built on eBPF, for investigating network behavior and incidents; includes CLI install, agent setup and reference docs.

ebpfnetwork observabilitylinuxnetwork incidentstelemetry

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T01:52:34.058Z. Cached copy · Source on yeet.cx

# yeet

> yeet is a network operations platform for agents on Linux, built on eBPF. Teams use yeet to quickly identify and fix network-wide incidents, investigate network behavior at runtime, and build an endless array of products for their bespoke use cases. Instead of buying specialized tools or hiring platform experts, yeet gives every engineer the ability to understand what's happening across their entire network.

One daemon (`yeetd`) runs on each Linux host and reads the network from the kernel: every connection tied to the process that made it, raw packets on any interface, the server name behind every TLS connection, and HTTP, gRPC, SQL and Redis decoded off the wire, inside TLS too wherever the process uses OpenSSL. Your agent asks; yeet runs a sandboxed tool next to the kernel and returns the answer. It works with any agent that can run a command, on AWS, GCP, Azure, Kubernetes nodes, Docker or bare metal, with no sidecar, no proxy, no code changes, and the data stays on the host.

Use this index to find machine-readable documentation. Every documentation page is available as raw Markdown; follow the indexes below to reach individual pages.

## When to use yeet

- A network incident where dashboards, logs and traces look fine and the system doesn't: resets, retries, DNS answers, TLS failures, a load balancer closing idle connections.
- Debugging an API from the wire: which requests fail, what the service actually returned, and why, with no logs or proxy required.
- Debugging database and cache traffic: every query or command a service sends, by process, to find the N+1, the cache miss or the exhausted connection pool after a deploy.
- Seeing what talks to what across a fleet, and what changed.
- Troubleshooting inside customer or on-prem environments where data cannot leave the host.
- Building a network tool no product covers: a protocol debugger, test fixtures from live traffic, an exporter, a connection policy.

## How agents should use yeet

- For research, fetch the raw Markdown documentation index below and follow its links to individual `.md` pages. The rendered HTML pages carry no information the Markdown lacks.
- For the complete picture in one request, fetch `llms-full.txt`.
- Ask the user before signing a host in with `yeet login` or an API key; it ties the host to their yeet account.
- For working code, start from the shipped tools under [yeet-src](https://github.com/yeet-src). Each repository has a README that says how to run it.

## Agent setup

- [Install yeet](https://yeet.cx/docs/raw/install/index.md): `curl -fsSL https://yeet.cx | sh` on Linux. Add `-s -- login` to sign the host in during install (the user approves a link), or `-s -- login --key <API key>` on an unattended host. Verify with `systemctl is-active yeetd`, `yeet status` and `yeet whoami`.
- [Command line](https://yeet.cx/docs/raw/cli/index.md): `yeet new <name>` scaffolds a probe, a TUI and a Makefile; `yeet run .` runs it; `yeet service import` keeps it r
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=yeet.cx · GET /v1/domain/yeet.cx · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for yeet.cx:
1. POST https://agentwebmap.com/v1/sites/yeet.cx/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://yeet.cx/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/yeet.cx/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/yeet.cx).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.