Testing Sandbox · Invitation Only
Request access for an organization, issue expiring test keys, and run fixed deterministic scenarios. Every result here is a test fixture, not a Council determination.
Platform status
Request Access
Your requests
Your account ID
Share this privately with an organization owner so they can add you as a member. There are no email invitations.
Full policy and steps: Testing Manual (PDF) · Instructions
Stripe test webhook readiness
Read-only delivery diagnostics. Payments, settlement and crediting remain disabled.
Testing Manual
The full manual, covering every workflow below, is available as a downloadable PDF.
Download Testing Manual (PDF)1. Request access
- Sign in to the Console.
- Open Testing Sandbox, Access tab.
- Enter your organization name and submit. One pending request per account.
- Wait for a Console administrator to approve or reject. Status appears under Your requests.
2. Approval and organization
- On approval an organization is created with you as protected owner (test_admin).
- An initial complimentary TEST credit grant is applied (default 100).
- The owner cannot be removed or demoted, and ownership cannot be transferred.
3. Members and roles
- test_admin: manage keys, members (non-owner admins only reviewer/tester), run scenarios.
- tester: run scenarios.
- reviewer: read-only; cannot run.
To add someone, they must sign in and visit the Sandbox once, then give you their account ID privately.
4. API keys
- test_admin creates a key with a label and expiry (1–90 days, default 30).
- The token is shown once only. It is not stored by this page; copy it securely and never log it.
- Revocation is permanent. Removed members' keys stop working immediately.
5. Running scenarios
- Choose a fixed scenario: allow, block or suspended. Each costs 1 TEST credit.
- Each run carries an Idempotency-Key; repeating with the same key replays without charge.
- Results are deterministic fixtures, not Council determinations. The suspended fixture is not the same as organization suspension.
- Key-based runs: POST /console/api/sandbox/orgs/{orgId}/runs with Authorization: Bearer <token> and Idempotency-Key.
6. Limits, usage and suspension
- Daily limit, per-user daily limit (0 disables runs) and max concurrent (1–100) are set by the owner or a Console admin.
- Suspended organizations return 423; exhausted quota or credits return 429.
- Only a Console admin may lift an admin-imposed suspension.
- The ledger shows TEST grant, reserve and settle records.
7. Payments and billing
Payments are not configured. There is no checkout, purchase, conversion, refund or cash value. TEST credits are complimentary and granted only by a Console administrator. Paid and live modes are rejected by the server.
9. Plan & Fund Your Test
- Open the Plan & Fund tab. Owners and test_admin members can save plans; others can view.
- Enter expected tests, evaluations, models, Council rounds and input/output tokens (expected and maximum).
- Add throughput (concurrency, request rate, window) and a contingency money reserve: none or a percentage of the service price, held as a refundable reserve. Everything is saved with the plan.
- Save and request a quote. The server prices the plan under the approved commercial policy: a service price of at least USD 1,500 that keeps EARTHX net earnings at 20% or more after AI, hosting, processing and tax costs, plus any refundable contingency reserve. The quote itemizes each part and the exact USD total. Quotes expire after 24 hours and become stale if the plan changes.
- Review, accept the quote and the finalized Terms, then use Pay exact quote with explicit consent. Only the exact accepted amount, in USD, for the accepted package can be paid.
Current status: prices are live, and payment runs in Stripe test mode (use a Stripe test card; no real money moves). After paying, choose Check payment status: funds count only when Stripe confirms they are fully processed and available. Live charges are not enabled.
10. Funding and refund policy
- Funds must be fully processed and available to cover costs before chargeable testing can begin. A successful checkout, payment authorization, captured payment or pending payout does not unlock testing.
- Each plan records a planned ceiling. It is not enforced today because paid runs are disabled; once enabled, funding must cover it before work starts.
- After a plan is closed or cancelled, eligible unused funds are submitted for refund within 7 working days. Bank processing time is additional.
- Fixed TEST scenarios and complimentary TEST credits remain separate from plans.
This policy describes how funding will work once enabled. It does not mean payments are available today.
8. Administrators
- Review pending requests in Admin Console; approve with an optional credit amount (0–100000) or reject.
- See all organizations, usage counts and integration status.
- Grant complimentary TEST credits with a reason (3–200 characters).
- Suspend or reinstate organizations and adjust limits.