Skip to main content

Status: not available yet

There is no public Developer API today. The API client is not distributed, its HTTP endpoints are not live, and API plans are not on sale. The API prices on the pricing page are planned prices. There is no release date.

Automate QNSQY today: the command line

The qnsqy command line runs unattended in scripts, scheduled jobs and CI. Your files are encrypted on your machine; when you are signed in, only the operation type, data size, algorithm and program version go to our billing server for the licence check.

  • API key: create one in your dashboard or with qnsqy account new-key, then set QNSQY_API_KEY in the job's environment. The program uses it instead of a stored sign-in.
  • Passwords: pass them on standard input with --password-stdin, never on the command line.
  • Many files: qnsqy batch encrypts or decrypts many files in one run (Pro and up).
  • Your plan applies: the same algorithms and limits as in the desktop app. Plans are flat-fee, with no credits.
Encrypt to a partner's public key, then decrypt with your private key
# The key comes from the environment, never from the command line
export QNSQY_API_KEY="<your API key>"

qnsqy encrypt -i report.pdf --recipient partner.pub
qnsqy decrypt -i incoming.pdf.qs --key my-key --password-stdin < key-passphrase.txt

On Windows, add --acknowledge-no-sandbox to each command. Every command and option: command reference and user guide.

Automate QNSQY today: the MCP server

qnsqy --mcp runs an MCP server over standard input and output with up to 108 tools (52 on Free, 83 on Pro, 108 on Business), for AI agents and for any program that speaks JSON-RPC 2.0. It runs locally, under the same plan and the same checks as the command line. Details: For AI Agents.

What the planned API is meant to be

The plan keeps the command line's model: the work runs on your machine with the same engine and the same .qs format, and only the operation type, data size, algorithm and program version go to our billing server. Use would be counted in credits, at the planned prices on the pricing page. These details can change before release.

Honest scope

QNSQY implements the NIST-standardized post-quantum algorithms (FIPS 203, 204 and 205). It is not FIPS 140-3 validated, holds no CMVP certificate, and is not SOC 2, PCI DSS or HIPAA certified. Your auditor owns the compliance call. See Security and Certifications.

Automate post-quantum encryption today

Download QNSQY, set an API key in your job's environment, and script the command line. Or connect an AI agent through the MCP server.