llms.txt
A concise map of the current documentation, platform setup, API reference, and machine-use rules.
Use machine-readable documentation, the OpenAPI description, and focused API guides to help coding agents inspect, explain, and automate Smart Link workflows.
Start with the smallest source that answers the task, then follow the canonical documentation links for implementation details.
A concise map of the current documentation, platform setup, API reference, and machine-use rules.
A structured API description agents can inspect when generating requests, clients, or integration examples.
Human-readable authentication, request, response, error, parameter, and rate-limit guidance.
Fetch https://zq.tn/llms.txt and identify the most relevant canonical page for the task.
Use the OpenAPI description for endpoint structure, then confirm authentication and constraints in the API reference.
Keep credentials server-side, show the proposed request, and let a human approve production-changing actions.
Read https://zq.tn/llms.txt first. Use only the canonical ZipQuantum documentation it links to. Explain the request before executing it. Never expose an API key in browser or mobile-app code. Ask for approval before creating, changing, or deleting production links.
These rules apply whether the agent writes code, prepares a request, or assists an operator.
Never place a ZipQuantum API key in public JavaScript, URLs, logs, or a distributed mobile binary.
Do not put passwords, tokens, private user data, or other secrets in destinations or parameters.
Only configure custom domains owned and verified by the authenticated ZipQuantum account.
Require explicit confirmation before an agent performs an action that changes production data.
Point your coding agent to zq.tn/llms.txt, then use the API reference for the exact implementation details.