> For the complete documentation index, see [llms.txt](https://docs.pynt.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pynt.io/documentation/security-testing-integrations/live-traffic-connectors/ebpf.md).

# eBPF

## Introduction

This document provides a technical overview of how Pynt leverages **eBPF** to **capture real-time HTTP traffic, generate HAR files**, and seamlessly integrate with Pynt’s SaaS platform for **deep API security insights**.

By implementing **eBPF-based live traffic**, Pynt enables **comprehensive API visibility**—identifying both **known and shadow APIs** while ensuring minimal system overhead.

## Architecture Diagram

<figure><img src="/files/4YxPnVlSXYRwD60H2yBN" alt=""><figcaption></figcaption></figure>

## Installation & Deployment

### **Access to Deployment Manifests**

To deploy Pynt’s **eBPF Live Traffic integration**, please **contact our team**. We will provide:

* **Kubernetes manifests** for seamless installation.
* A **detailed README** with setup instructions.

### **Guided Deployment Support**

Our security experts are available to assist you with:

* Customizing filters, storage limits, and network configurations.
* Ensuring smooth integration into your Kubernetes environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pynt.io/documentation/security-testing-integrations/live-traffic-connectors/ebpf.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.