FAQ
Quick answers about what Qwayk is, how the tools work, and how to get access.
If you’re new here, start with: - Docs → Docs - Tools library → Tools - Safety model → Safety model - Pricing → Pricing
Want updates? Create a free account (Subscribe) or start here: Get access.
What is Qwayk?
Qwayk is a small set of command-line tools (CLIs) I built to make AI-assisted API work safer. They help you do real work with real APIs (Ghost, WordPress, Freepik, Plausible, etc.) without risky “guessing edits”.
Is this a hosted service?
No. In v1, these are local tools you run on your own computer or server. Your API keys stay with you.
Does Qwayk store my credentials or tokens?
No. Tools read credentials from your local .env file and (when needed) store tokens in a local .state/ folder that is gitignored.
I don’t want your secrets, and support will never ask you to paste them.
Will this let an AI agent “take over” my accounts?
Only if you let it.
The tools are designed to reduce risk: - dry-run is the default - writes require explicit flags - destructive actions require extra confirmation - after changes, the tool verifies what happened
You are still responsible for API keys, permissions, and any changes made through the APIs.
What does “safe by default” mean?
It means the tool tries very hard to refuse instead of guessing.
The typical loop is: 1) dry-run (plan) 2) review the plan 3) apply (explicit flags) 4) verify (read-back, and when it fits: re-run a dry-run and confirm it shows 0 changes)
The safety model is explained in more detail here: Safety model.
Do I need to be an engineer?
You should be comfortable running commands and editing small config files. Most users will use an assistant (like Codex or Cursor) to speed up the boring parts and review plans carefully.
Will this work with my setup (VS Code / Cursor / CI / servers)?
Yes. These are CLI tools with JSON output, so they can be used from: - any terminal - VS Code / Cursor tasks - CI (like GitHub Actions) - cron jobs - automation tools that can run shell commands
Can I use Qwayk tools inside an “agent runtime”?
Yes, as long as the runtime can call a CLI deterministically.
The important part is the safety loop stays intact: dry-run → review → apply → verify → receipt.
Do I need Codex to use Qwayk?
No. These are normal CLI tools.
I recommend using Codex because it’s great at reviewing a plan against a goal. But you can also review plans yourself or use another assistant.
What happens if an API changes?
Tools are versioned. When something changes, updates should include clear notes (what changed, what breaks, and what you need to do).
When in doubt, the tool should fail safely rather than guess.
Do you offer support?
The product is designed to be docs-first and self-serve. If you get stuck, check Docs and the safety model (Safety model) first.
Support channels and public contact info live here: Contact.
Can I use Qwayk for client work?
Soft launch note: paid memberships are not enabled yet, so there isn’t a “commercial tier” to buy right now.
When paid goes live, I’ll make the license boundaries explicit on: - Pricing - Terms
Where can I read the legal stuff?
Start here: - Terms → Terms - Privacy → Privacy - Disclaimer → Disclaimer
If something legal or policy-related matters to your decision, rely on those pages instead of this FAQ.
Get access
Create a free account, then follow the onboarding steps.
