Developer Preview availability
What is public today, what needs approval, and how Torq keeps public documentation separate from production access.
Torq Developer documentation is publicly readable. The current integration program is Developer Preview: approved organizations can receive test credentials and controlled sandbox access while the public-GA release gate remains closed.
| Surface | Availability | Notes |
|---|---|---|
| Documentation, OpenAPI, SDK reference, and ABI provenance | Public | Read the contract before requesting access. |
| Canonical API and authenticated GraphQL | Approved Developer Preview applications | A key, scopes, quotas, and origin policy are required. |
| Sepolia sandbox admission, fixtures, and faucet claims | Approved Developer Preview applications | Ownership, wallet session, and application quota are enforced. |
| Production credentials and approved-role scopes | Approval required | Torq evaluates the organization, application, scope, and current authority. |
| Public GA | Not open | The governed launch gate remains fail-closed until its independent release evidence is complete. |
What access never grants
- A Developer key does not grant protocol-manager, guardian, council, deployment, reset, or shared-secret authority.
- 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 active V2 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 preview 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 Developer Preview 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.