Critique API CLI
The official command-line client for creating, inspecting, modifying, deleting, and invoking private Critique API research endpoints.
The CLI is optional. Critique's agent skill and HTTP API work from projects in any language without Python. Install this package as a standalone tool when a terminal interface is convenient; do not add it to an application's runtime dependencies unless that application directly needs it.
Install
With pipx:
pipx install critique-api-cli
With uv:
uv tool install critique-api-cli
Set the API key in the environment:
export CRITIQUE_API_KEY="your-api-key"
Create a key at Billing & API Keys. Never paste an API key into source code, command arguments, URLs, or commits.
Usage
# Create an endpoint
critique-api create \
--prompt "For a company name, return its latest funding round, investors, date, amount, and primary-source citations."
# List or inspect endpoints
critique-api list
critique-api get 42
# Modify only the intended fields
critique-api update 42 \
--stub latest-company-funding \
--inputs '[{"name":"company","type":"string"}]' \
--output '{"company":"string","amount":"number","investors":[{"name":"string"}]}'
# Invoke the generated endpoint
critique-api run latest-company-funding \
--data '{"company":"OpenAI"}'
# Permanently delete an endpoint
critique-api delete 42 --yes
JSON arguments may be literal JSON or @path/to/file.json.
Use CRITIQUE_BASE_URL only to target a non-production deployment.
Development
python -m venv .venv
source .venv/bin/activate
python -m pip install -e '.[dev]'
pytest
python -m build
python -m twine check dist/*
Releases
Releases use PyPI Trusted Publishing and do not require a stored API token.
- Update the version in
pyproject.tomlandsrc/critique_api_cli/__init__.py. - Merge the release commit to
main. - Create and push the matching tag, such as
v0.1.1. - The publish workflow builds, verifies, and uploads the distribution.
Before the first release, configure a pending GitHub Actions publisher on PyPI with these exact values:
| Field | Value |
|---|---|
| PyPI project name | critique-api-cli |
| GitHub owner | parthh01 |
| GitHub repository | critique-api-cli |
| Workflow filename | publish.yml |
| GitHub environment | pypi |
The pending publisher creates the PyPI project when the first release workflow succeeds; no PyPI API token or repository secret is needed.
License
MIT
Metadata
Release files for critique-api-cli 0.1.1
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 | |
|---|---|---|---|---|
| critique_api_cli-0.1.1.tar.gz | 6.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| critique_api_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.9 kB
Release files / critique_api_cli-0.1.1.tar.gz
| Download URL | critique_api_cli-0.1.1.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42781e641486cc936c6c8e21552a35d620b9cd266e69c3cd50fc4e6b1ee1a4d7
|
|
BLAKE2b-256 checksum How to use checksums |
35a1d79cce70b5b956107b6cbae6145bd05460defa028311670e3355f59f5128
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency logRelease files / critique_api_cli-0.1.1-py3-none-any.whl
| Download URL | critique_api_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bce9baab024e2e61edd5f6789e8673590e6eef6fdcb57443cee902205532f36d
|
|
BLAKE2b-256 checksum How to use checksums |
8bc45aaa5b2d06570e3b21cbf6d8f52c5801e49db603aea85e4f5c2da75b5e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency logSecurity for critique-api-cli 0.1.1
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 critique_api_cli-0.1.1.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 Aug 28, 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.