AffixIOAFFIXIO
Contact

Developer tool

AffixIO CLI

Prove, verify, and generate Merkle-backed codes from the terminal. One-line install, hub browser login, local vault at ~/.affix/codes/.

Verify login Merkle codes PNG export Local vault
1.2.3Release
Node 18+Runtime
VerifyDevice login
MerkleEvery code
Install 
curl -fsSL https://www.affix-io.com/cli/install.sh | bash

  1. Run affix login. The CLI shows a device code and opens your browser.

  2. Sign in at affix-io.com/cli/verify and approve the code for this machine.

  3. Run affix for interactive mode, or call commands directly from your shell.

Capabilities

Built for operators who live in the terminal

Prove, verify, and generate codes without leaving your shell. Every output is Merkle-audited through the hub proxy.

API
Prove and verify

Call Noir circuits on api.affix-io.com. Health checks, auth validation, and proof verification without leaving the shell.

Codes
Merkle QR and barcodes

Generate through the hub proxy with Merkle audit on every create. SVG by default, --png for raster output. Any https URL.

Vault
Local code storage

Files saved to ~/.affix/codes/ with configurable output locations. List, open, scan, and remove from the vault.

Auth
Verify device login

No manual API key copy. Approve a device code at /cli/verify and receive an aio_ key on this machine.

AffixIO Engineering · Wales, UK. CLI v1.2.3 ships from this page. Commands tested against the live verify endpoint and service status. Updated 13 July 2026.

Reference

Command reference

All commands available after affix login. Run affix alone for interactive mode.

Auth

affix login

Browser activation via /cli/verify. Credentials in ~/.affix/credentials.json.

affix logout

Remove local credentials from this machine.

affix whoami

Show the signed-in account.

API

affix health

Check api.affix-io.com health.

affix circuits

List available Noir circuits.

affix prove [--circuit <id>]

Demo prove. Default circuit: ticket_local_resident.

affix verify <proof>

Verify a proof string against the API.

Codes

affix qr <url|text> [--png]

Merkle-backed QR. Pass --png for SVG and PNG output.

affix qr ticket --event <slug> [--scans N]

Ticket QR with scan limits.

affix barcode <data> [--type code128]

Barcode generation with Merkle audit.

affix scan <id|token>

Merkle-audited scan against a stored or raw code.

affix codes

List the local vault.

affix open <id>

Open SVG or PNG in your default app.

Config

affix location add <name> <path>

Register a custom output directory for generated files.

affix location list

Show saved output locations.

affix

Interactive REPL after sign-in.

Questions

Where are credentials stored?

Locally at ~/.affix/credentials.json with restrictive file permissions. The verify page issues a dedicated API key labelled for your CLI session.

Do I need a separate API key?

No manual key copy. After approval at /cli/verify the CLI receives an aio_ key automatically. Manage keys from the account hub.

Where are QR and barcodes stored?

Generated files live in ~/.affix/codes/ with an index at index.json. SVG by default. Pass --png for a PNG copy.

Can I point output to another folder?

Use affix location add desktop ~/Desktop/codes then --location desktop, or --out /path for a one-off path.

What if the device code expires?

Codes last ten minutes. Run affix login again to generate a fresh code.

Building an application integration? Start with the quickstart or the Node.js SDK.

Activate CLI Quickstart