> For the complete documentation index, see [llms.txt](https://docs.hypersolutions.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypersolutions.co/ai-plugins/codex-plugin.md).

# Codex plugin

The Hyper Solutions plugin teaches Codex how our API actually works, so your agent can integrate the SDKs, generate sensors, cookies, and tokens for all four vendors, and find the fingerprint mistake behind a blocked request, without you copy-pasting documentation into the chat.

### Installation

With the [Codex CLI](https://github.com/openai/codex) installed:

{% code overflow="wrap" %}

```
codex plugin marketplace add Hyper-Solutions/hypersolutions-codex
codex plugin add hypersolutions@hypersolutions
codex mcp login har-analyzer
```

{% endcode %}

The last command signs the HAR analyzer in against your Hyper Solutions account (also available under **Settings → MCP servers → From plugins → Authenticate**).

### What's included

* **The `hypersolutions` skill**: integration knowledge for Akamai (sensor, sec-cpt, SBSD, pixel), Incapsula (reese84, utmvc), DataDome (interstitial, slider, tags), and Kasada (payload, POW, Vercel BotID), across the Go, Python, and JS/TS SDKs or raw REST. It also knows the non-negotiables: browser-grade TLS clients, exact header order, session consistency, and sticky proxies.
* **The powhttp MCP server**: reads live captures from [powhttp](/request-based-basics/installing-powhttp.md): true header order, TLS fingerprint, and HTTP/2 stream details from the requests your code really sent. Install powhttp and start it under **Settings → MCP Server**. For a full walkthrough of capturing and debugging with powhttp, see the [powhttp guide](https://hypersolutions.co/blog/how-to-use-powhttp-web-scraping).
* **The har-analyzer MCP server**: analyzes an exported HAR against our maintained rule set: header order and casing, `sec-ch-ua` and Chrome version mismatches, duplicate cookies, pseudo-header order, and per-vendor mistakes.

### Authentication

* The **har-analyzer** signs in with your Hyper Solutions account via OAuth (`codex mcp login har-analyzer`).
* Actually calling the Hyper Solutions API requires an [API key](https://hypersolutions.co/keys). See [Authentication](/api-reference/authentication.md).

{% hint style="info" %}
To record a HAR file for analysis, see [Recording HAR files](/request-based-basics/recording-har-files-for-harvey.md).
{% endhint %}

### Example prompts

* "Help me set up the Akamai sensor flow in Python with tls-client."
* "My DataDome slider solve returns 403. Capture my script with powhttp and tell me what's wrong."
* "Analyze this HAR and find why I'm getting blocked."
* "Why is my `_abck` cookie never becoming valid?"

{% embed url="<https://github.com/Hyper-Solutions/hypersolutions-codex>" %}