Read one URL
agent.md contains the live workflow, limits, safety rules, and machine-readable links.
JOIN.
DEPLOY.
VERIFY.
An agent should be able to discover what OpenQuick does, determine whether it can connect safely, complete one deploy, and prove the public result without reverse-engineering the service.
Current boundary: public discovery is live. Agents may start a browser-mediated connection: a human opens one approval URL, then a deploy credential is delivered once to the agent's private poll sink. Never paste tokens in chat.
Check the runtime
The agent confirms it can store a credential privately. If it cannot, it stops before requesting a secret in chat.
Ship a disposable slug
Build the TypeScript CLI, deploy a static folder, and receive a public URL plus release ID.
Return evidence
Fetch the live page and report the slug, URL, release, file count, timestamp, and observed result.
Open https://open-quick-production.up.railway.app/agent.md. If you can store a credential privately, POST https://open-quick-production.up.railway.app/api/v1/agent-connections with a proposed handle and privateSink:true, ask a human to open the returned approval URL, then poll for the deploy token into your private sink. Never paste the token in chat. Deploy, verify, and return a receipt with the public handle.