New · Official AI plugins

Your coding agent,
fluent in antibot.

Official plugins for Claude Code and Codex that teach your agent the Hyper Solutions API: how to generate sensors, cookies, and tokens for Akamai, DataDome, Incapsula, and Kasada, and how to find out why a request got blocked, from a live capture or an exported HAR.

See the plugin in action →
Claude Code · Anthropic's agentic coding CLI
/plugin marketplace add Hyper-Solutions/hypersolutions-claude-code
/plugin install hypersolutions@hypersolutions
Sign in to the HAR analyzer once via /mcp. It authenticates against your Hyper Solutions account.View on GitHub →
Codex · OpenAI's coding agent CLI
$codex plugin marketplace add Hyper-Solutions/hypersolutions-codex
$codex plugin add hypersolutions@hypersolutions
$codex mcp login har-analyzer
The last command signs the HAR analyzer in against your Hyper Solutions account.View on GitHub →
Any MCP client

Bring it to the agent you already use.

The two MCP servers and the skill are the whole product. Point any MCP-capable agent at them and it gets the same capabilities, no packaged plugin required. Paste the config, drop the skill into your rules, done.

Works anywhere MCP does: Cursor · Cline · Continue · Windsurf · VS Code · Zed · Goose · Gemini CLI, and more.

View the skill on GitHub →
mcp config · any client
{
  "mcpServers": {
    "powhttp": {
      "type": "http",
      "url": "http://localhost:8383/mcp"
    },
    "har-analyzer": {
      "type": "http",
      "url": "https://har-mcp.hypersolutions.co/mcp"
    }
  }
}
powhttp exposes its tools once powhttp is running with its MCP server enabled. The HAR analyzer signs in with your Hyper Solutions account via OAuth on first connect.
What's inside

One skill, two debugging tools, zero copy-pasting docs.

Both plugins ship the same brain. The difference between a request that solves and a request that gets blocked is usually a fingerprint detail your HTTP client hides from you. The plugins give your agent the knowledge and the instruments to find it.

debugging tool02

Live wire capture with powhttp

A bundled MCP server reads your traffic straight from powhttp: the requests your code really sent, not what your HTTP library claims it sent.

header orderTLS fingerprintHTTP/2 stream
debugging tool03

HAR analysis with a maintained rule set

Export a HAR and the agent runs it against our hosted analyzer, the same checks our support engineers use.

  • header order and casing
  • sec-ch-ua and Chrome version
  • duplicate cookies, pseudo-header order
In practice

Things you can just ask.

No docs open, no dashboard tab. Your agent already knows the API. Describe the problem and let it work.

Agent session
>My DataDome solve returns 403. Analyze this HAR and tell me why I am getting blocked.
har-analyzer scanned 41 requests · 1.2s
detected productDataDome
confirmedheader order mismatch on 3 requests
confirmedsec-ch-ua says Chrome 143, sensor payload says 140
warningmissing datadome cookie on the retry request
Fix applied to session.py
Proof

One prompt. One working scraper.

We pointed the plugin at a recorded Etihad session and asked for a working Go scraper in a single prompt. 16 minutes and 31 seconds later it pulled live award pricing. We never touched the code, and it runs with zero AI in the pipeline.

Read the full demo →
Run log · etihad-scraper
>Implement the requests to scrape Etihad's air-bounds pricing API in Go and figure out the antibot bootstrap.
00:41read the powhttp capture: 282 requests before the pricing API responds
03:12detected AkamaiIncapsula only reese84 gates the API, Akamai skipped
07:48rebuilt the reese84 dynamic bootstrap: script fetch, proof of work, sensor via the API
12:05matched the browser's JA4 and header order with tls-client
16:31 live award pricing, 22 KB per search
1
prompt
16:31
build time
875×
less bandwidth
0
AI calls at runtime
FAQ

Questions engineers actually ask.

Yes. Both the Claude Code and Codex plugins are free to install and use. You pay for Hyper Solutions API usage, the sensors, cookies, and tokens you generate, on the same pricing as the rest of the platform. The plugin itself never adds a fee.
The HAR analyzer processes your capture to produce the report and nothing else. HAR files can contain cookies and tokens, so send only the flow you are debugging. If you want a capture sanitized first, ask us on Discord and we will walk you through it.
You need an account to sign in to the HAR analyzer, and an API key to actually generate sensors, cookies, and tokens. The integration skill and the powhttp capture tools work as soon as the plugin is installed.
The whole thing is editor-agnostic. Claude Code and Codex get one-command installs; everywhere else, paste the MCP config and drop the skill into your rules, as shown in "Bring it to the agent you already use" above. It works with Cursor, Cline, Continue, Windsurf, and any MCP client.
A bare model guesses at our API from stale training data. The plugin ships maintained integration references plus two instruments a model cannot improvise: live wire capture through powhttp and our HAR analyzer rule set. Your agent works from ground truth instead of guesses.