harrecon
Turn a HAR capture into a private API's inventory, response schemas and a typed Python client — offline, stdlib only.
$ harrecon inventory capture.har
captured 6 entries, 2 JSON endpoints
auth mechanisms:
authorization: Bearer: Bearer e…(32 chars)
GET /v1/health [api.example.com] 200
GET /v1/lots/{id} [api.example.com] 200/200
$ harrecon schema capture.har "GET /v1/lots/{id}"
object
id: int
title: string
price: number
$ harrecon diff worked.har broken.har
+ GET /v1/search [api.example.com]
~ GET /v1/lots/{id} [api.example.com] schema changed:
after: {"fields": {..., "currency": {"type": "string"}}}
$ harrecon gen capture.har "GET /v1/lots/{id}" --out client.py
Commands
harrecon inventory <har> [--host H] [--json] # endpoints + auth mechanisms (redacted)
harrecon schema <har> "<METHOD> /path" [--json] # merged schema across samples, optional-fields aware
harrecon diff <har_a> <har_b> [--json] # added / removed / schema-changed — "did they change the API"
harrecon gen <har> "<METHOD> /path" [--out f.py] # typed dataclass client skeleton (urllib, review before use)
Numeric path segments collapse to {id} so repeated calls count as one endpoint. Static assets, HTML and tracking noise are excluded. Auth samples are redacted in all output. Python 3.11+, stdlib only.
Install: pip install harrecon — or from this repo:
pip install "git+https://github.com/juzorei/harrecon#subdirectory=tools/harrecon"
The companion agent skill lives in skills/har-to-api-client: capture hygiene, auth identification, schema caveats (inference from samples ≠ documentation), diff-based scraper debugging, and the ToS boundaries. Skills: npx skills add juzorei/harrecon.
Metadata
Release files for harrecon 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| harrecon-0.1.0.tar.gz | 10.1 kB | With provenance | Details for harrecon-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| harrecon-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for harrecon-0.1.0-py3-none-any.whl |
Total release size: 19.7 kB
Release files / harrecon-0.1.0.tar.gz
| Download URL | harrecon-0.1.0.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
855e3afa13e7feef2bff643eb569549fd442e4906107f2e04514d81dd6496156
|
|
BLAKE2b-256 checksum How to use checksums |
e29ca131a0ce09761798e3d498345cb4ffe016168ed8a6a5519d461f61ff2b8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / harrecon-0.1.0-py3-none-any.whl
| Download URL | harrecon-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ac87c24f53eee97b1bc4532bec662ad4c1b6b21ebab9476c3f14ce1f7ee4503
|
|
BLAKE2b-256 checksum How to use checksums |
3cf6c57a2057b0e38a4e0d4c1bd7f172747a51559f20978d636fadfc3593e834
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for harrecon 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for harrecon-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.