Skip to content
quoxcli

Find out what a credential needs

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

What does this credential need?

Ask whether Quox knows a service and which fields it wants, before you store a key.

What you get: the exact fields a service needs before you go and fetch a key, so you store it right the first time.

Ask Quox

Section titled “Ask Quox”

Name the service in your own words:

quox · talking to Quox

Does my vault's integration type catalogue have a type for PyPI? If so, what is it called and which fields does it ask for?

▤ AOCL │ L1 identity complete · allowed · 0ms

▤ AOCL │ L3 policy gate complete · proceed · 3ms

◐ VAULT │ types ✔ VAULT │ types │ 1 count, 1 types · 4.1s

⛓ AEE │ envelope opened · stream_success

Yes, the catalogue has a PyPI type.

• Name: PyPI (id  pypi , category devops)
• What it's for: a PyPI upload token.
• Fields: one required field, API Token (stored as a password). The placeholder shows
  the expected prefix,  pypi-... .
• Testing: there is no live connection test. PyPI API tokens authorize uploads and have
  no read endpoint to test against, so saving only checks the token's format.

19.7s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.0, 15 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Oct 2026 · test report mv8ymr

Quox read the vault’s catalogue of integration types and found the match. It never touched a stored secret: the catalogue only describes what a credential of that type looks like.

Do it yourself

Section titled “Do it yourself”

1. Find the type

Section titled “1. Find the type”
integration types 
quox vault typesID                        Name                           Descriptionnpm                       npm                            npm registry: package metadata, dist-tags, search, and to...pypi                      PyPI                           PyPI upload token (format check only: PyPI API tokens aut...ward_webhook              WARD Evidence Webhook          Endpoint that receives each witnessed WARD evidence tip a...
From a real run on our own install. Trimmed to three of over 400 types.

The ID is what you pass as --type. Add --output json to see each type’s fields, which ones are required, and whether Quox can live-test it.

2. Store the credential

Section titled “2. Store the credential”
Terminal window
quox vault create --type pypi --label "PyPI upload"

Quox asks for each field and hides what you type. For scripts, --credentials-stdin reads the fields as JSON from standard input, so the secret never lands in your shell history or on disk.

3. Check it

Section titled “3. Check it”

quox vault test <id> tests a stored credential. For a type that only checks the format, like PyPI, the test confirms the token looks right.

What just happened

Section titled “What just happened”

Asking about a type reads the catalogue, not your vault, so no secret was read and no approval was needed. When you store a credential, Quox encrypts it on your own install. Agents later borrow it for one tool call at a time and never see the value.

Check it yourself

Section titled “Check it yourself”

quox vault list shows your credentials with every secret masked. quox vault activity shows who used which credential, and when.

Undo

Section titled “Undo”

Asking needs no undo. quox vault delete <id> removes a stored credential.

Next

Section titled “Next”