Developer access and availability
Torq Developer documentation is publicly readable. The current integration program is controlled developer access: approved organizations can receive test credentials and controlled sandbox access while the public-GA release gate remains closed.
What access never grants
- A Developer key is limited to its application grants and approved workflow scopes.
- A wallet session does not authorize a transaction by itself.
- A prepared workflow does not let Torq sign, custody, or relay a production transaction.
- A sandbox admission never grants authority over the current Sepolia release.
What to prepare before requesting access
Use one organization owner wallet, a named application, the intended browser origins, the requested test scopes, and an integration contact. Keep secret keys in your server-side secret manager. Do not include seed phrases, private keys, reusable signatures, or customer signer credentials in an access request.
The current availability boundary is deliberate. It lets developers study the public contract and build against the same typed surfaces without representing restricted access as general production availability.
Remaining public launch boundaries
Two release proofs remain open and are separate from live API uptime:
- SDK registry publication. The checked-in TypeScript, React, contracts, Python, JVM, Kotlin, and Swift clients remain controlled developer access source packages. Public registry publication and a clean independent installation are not yet proven.
- Protected public-CI. The governed
release.public_ci_wiringstatus remainspartial_proven; a protected public-GA candidate has not yet produced a genuinely passing run.
Public GA remains disabled until both proofs are current and complete. The API status page reports current service health only; a healthy check does not satisfy either release boundary.