Enterprise Readiness
This page describes the current technical readiness of Open4X. It is not a service-level agreement, price sheet, or contractual commitment.
Environments
Open4X currently has local development/sandbox, an isolated staging environment, and an internal P2 trial environment. Production has a separate configuration and hostname, but production payment, OAuth, social, email, and TRON providers are enabled only after their release gates pass. The trial environment is isolated and remains side-effect disabled until a separate provider allowlist and observation gate are approved.
The current internal trial endpoints are https://open4x-gateway-trial.29498587.workers.dev and https://openedge-console-trial-sandbox.pages.dev. They are for technical validation only and do not carry production SLA, pricing, or provider-delivery commitments.
API Keys and Controls
Each API key can be scoped by:
- service alias and API scope;
- source IP or CIDR;
- UTC daily quota;
- per-minute request limit;
- in-flight concurrency limit;
- expiry, revocation, rotation, and lifecycle audit.
Plaintext keys are shown only at creation or rotation. The database stores a hash.
API Contract
The machine-readable contract is OpenAPI 3.1, version 2026.08.09. It covers the core REST API, including API keys, asynchronous jobs, TRON lease idempotency, and request trace lookup. WebSocket, inbound webhook, widget, and provider-specific OAuth protocols have separate integration contracts.
Jobs and Request Tracing
The unified job API is:
GET /v1/jobs
GET /v1/jobs/{id}Job states are pending, running, succeeded, failed, canceled, and expired. TRON Lease currently supports HTTPS callbacks with HMAC-SHA256 signatures, exponential retry, and a maximum of eight delivery attempts.
Gateway requests use X-Request-ID. Tenant administrators can query redacted operational metadata with:
GET /console/requests/{request_id}The trace response does not include prompts, full model responses, credentials, or provider secrets.
Service Maturity
| Service | Current status |
|---|---|
| Gateway, API keys, and basic billing | Beta preparation |
| AI Model Gateway | MVP |
| Bot, File, and Webhook Push | Beta preparation |
| SocialOps | MVP |
| Connected Accounts and OAuth | Beta preparation |
| TRON Energy Lease | MVP / sandbox |
Actual production availability is enabled service by service after provider, billing, monitoring, and rollback checks.
Pricing and SLA
Open4X supports prepaid balance, usage billing, and subscription layers. Current pricing documents contain suggested commercial values; free quotas, default limits, overage behavior, SLA targets, maintenance notices, and service credits become effective only through the published price sheet and contract.