# Pynt CLI Modes

Pynt offers two powerful modes within its CLI for conducting API security tests: [**Pynt Command**](#pynt-command) and [**Pynt Listen**](#pynt-listen). Each mode is designed to integrate with various tools and workflows, ensuring flexibility in how API security tests are performed.

***

### Pynt Command

{% hint style="info" %}
💡 **Pynt Command Mode**: Pynt Command allows users to wrap their existing CLI-based functional tests with Pynt’s security testing capabilities. It seamlessly integrates into your current workflow, enabling automatic API security testing alongside functional tests.
{% endhint %}

Pynt Command supports a wide range of configurations and optional arguments to tailor the tests to specific needs, making it adaptable for various testing environments.

***

### Pynt Listen

{% hint style="info" %}
💡 **Pynt Listen Mode**: Pynt Listen operates as an interactive proxy, listening on a specified port and capturing network traffic for security analysis. It is designed for tools that can direct their traffic through a proxy, providing flexibility for API security testing in various scenarios.
{% endhint %}

With Pynt Listen, users can capture traffic from a variety of sources and initiate security tests by triggering the scan, making it ideal for capturing real-time data from browsers, testing suites, and more.

***

{% hint style="info" %}
For additional support, visit [Pynt Community Support](https://www.pynt.io/community).
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.pynt.io/documentation/api-security-testing/pynt-cli-modes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.