API Documentation
Choose your card type, then submit and track tasks.
Save the task ID. Poll every 5 seconds.
Authentication
Send HTTP POST requests with Content-Type: application/json. Use your business card directly; no separate API key is required.
Content-Type: application/json
Authorization: Bearer YOUR_CARD_KEYCredentials can also be provided in X-CDKey or the cdkey body field. Priority: Authorization → X-CDKey → cdkey. An invalid higher-priority credential is rejected; lower-priority values are not tried.
Use HTTPS from your server. Browser cross-origin access is not enabled. Keep credentials out of public frontend code and logs.
Web API
Use a cdkd-… card. Mobile cards cannot submit web plans.
| Plan | task_type / plan_code | Cost |
|---|---|---|
| Loading available services… | ||
Call get_balance before submission. Its plans array lists enabled services with plan_code, plan_label, cost_points and configured. Display only available plans and read their current prices; do not hard-code costs. Closed plans reject new submissions through both the customer page and API. Existing orders retain the price captured when submitted for settlement, refunds and requeueing.
A closed plan rejects new orders and customer restarts of failed orders with plan_disabled (409). Original request replays and credential updates to active or successful orders remain allowed. plan_price_not_configured means pricing is missing; plan_not_configured means no execution template is configured. Contact the service provider.
The table lists services currently enabled on configured Workers; closed services are hidden. Your card must first be assigned to a dedicated Worker by the administrator. Call get_balance to obtain the plans and prices for that card. Use the returned plan_code; do not infer a service from its month count.
Points are reserved on submission, captured on success, and released on failure or cancellation. A disconnect is settled after the server heartbeat timeout.
The initial result is stored by normalized email. An existing subscription blocks this attempt and refunds the reservation. An explicit customer resubmission of that failed order performs a fresh check. Completed subscription and renewal stages managed by this system are preserved and never repeated.
| action | Fields | Behavior |
|---|---|---|
get_balance / stats | Authentication | Returns available_points, reserved_points, spent_points. |
submit_task / submit | request_id, task_type or plan_code, email, password; twofa or recovery_email | One account per request_id. twofa accepts a Base32 secret or an 8-digit backup code string, not a 6-digit rotating OTP. |
get_status / list / detail | Optional task_id or email, not both; limit / offset for lists | Queries only this card. data is an object for task_id/email queries and an array for lists; an unmatched email gives null. Poll every 5 seconds. |
cancel_task / cancel | task_id | Only queued tasks can be cancelled. Releases reserved points once. |
Request IDs, repeated emails and limits
Generate and save a stable request_id for each order. Reuse the same ID and original payload after an unconfirmed network result. A changed payload with the same ID returns idempotency_conflict.
For a failed, refunded order under the same card, email and plan, resubmit with a new request_id to requeue its original task ID, even if credentials are unchanged. The Worker deletes the old browser profile and creates a fresh one before execution. The original plan, price, completed PSC and subscription stages are retained; only unfinished work is reserved and executed. Cancelled orders still require changed credentials to requeue. Queued, running and successful orders only update credentials. Reuse the original request_id and payload after an uncertain network result; a replay never reserves points or starts work twice. Check status for the current state.
Web submissions are limited to 10 per normalized email across cards, including deleted history. Web and mobile counters are separate. An active task under another card blocks a new task.
Verification and import formats
Provide at least one valid twofa or recovery_email. Empty twofa is allowed with a valid recovery email; a nonempty value must still be valid. Always pass backup codes as strings to preserve leading zeros. "00123456", "0012 3456" and "bym-00123456" normalize to "bym-00123456". Existing prefixes are not duplicated.
Imports accept email----password----2FA, email----password----recovery-email, or email----password----recovery-email----2FA. Keep delimiters for empty columns. Use tasks/account_data only to represent one web account per request_id.
{
"action": "submit_task",
"request_id": "9e6ca48c-37b2-4c51-b948-4a41ac0b626a",
"task_type": "YOUR_ENABLED_PLAN_CODE",
"email": "[email protected]",
"password": "YOUR_ACCOUNT_PASSWORD",
"recovery_email": "[email protected]",
"twofa": "00123456"
}| status | Meaning |
|---|---|
queued | Queued; can be cancelled. |
dispatched / running | Assigned or running; continue polling. |
succeeded | Complete; points captured. |
failed | Failed; inspect status and settlement_status. Task diagnostics are not returned. |
cancelled | Cancelled; reservation released. |
{
"action": "get_status",
"task_id": "550e8400-e29b-41d4-a716-446655440000"
}{
"success": true,
"data": {
"task_id": "550e8400-e29b-41d4-a716-446655440000",
"email": "[email protected]",
"status": "failed",
"settlement_status": "refunded",
"initial_subscription_status": "preexisting",
"message": ""
}
}List limit: 1–1000, default 100. Offset defaults to 0. Status values are lowercase. Web tasks do not require a result link.
Antigravity activation and subscription bundles
Customer page: Antigravity activation ↗. Use a web cdkd- point card for activation only, or subscribe first and then activate. Existing mobile and ordinary web subscription services remain available.
| task_type | Service | Points reserved | Google AI Pro subscription already exists at first login |
|---|---|---|---|
| Loading available services… | |||
Bundle charges are separate. Once the full subscription succeeds, its points are captured and the same browser profile is retained for activation. Activation captures 1 point on success; activation failure returns only that point. A preexisting subscription skips the subscription stage, returns its points and continues activation without closing or deleting the profile. Ordinary subscription orders still reject subscriptions present at first login.
| Operation | Request | Notes |
|---|---|---|
| Balance | action=get_balance with web card authentication | ag_activation.configured indicates whether the activation template is enabled. |
| Submit | action=submit_task, a task_type above, request_id, email, password, and twofa/totp or recovery_email | One account per request. Omit plan_months. Use separate request IDs for batches. |
| Query | action=get_status with task_id; for lists include task_type=ag_verify and limit/offset | The list includes all activation-only and bundled orders owned by the card. Filter a specific bundle with sub6_ag/sub12_ag/sub24_ag. |
{
"action": "submit_task",
"cdkey": "cdkd-YOUR_CARD_KEY",
"task_type": "YOUR_ENABLED_SERVICE_CODE",
"request_id": "ag-order-001",
"email": "[email protected]",
"password": "YOUR_ACCOUNT_PASSWORD",
"twofa": "00123456",
"recovery_email": ""
}{
"task_type": "YOUR_ENABLED_SERVICE_CODE",
"ag_requested": true,
"status": "failed",
"cost_points": 3,
"subscription_cost_points": 2,
"activation_cost_points": 1,
"subscription_outcome": "completed",
"activation_status": "failed",
"charged_points": 2,
"refunded_points": 1,
"credential_available": true,
"ag_verified": false,
"credential": "YOUR_REFRESH_TOKEN",
"export_line": "[email protected]_ACCOUNT_PASSWORD----无辅助邮箱----bym-00123456----YOUR_REFRESH_TOKEN"
}subscription_outcome: pending/completed/skipped_existing. activation_status: not_started/pending/running/succeeded/failed/cancelled. charged_points and refunded_points describe the current settlement of the order components. Retrying activation retains the completed subscription charge and does not accumulate past failed-attempt refunds. An overall failed status does not mean a full refund; show subscription and activation outcomes separately.
Credentials are returned as soon as acquired and retained on later failure. credential_available:true means a credential was saved; ag_verified:true means activation succeeded. The export format is email----password----recovery email----2FA/backup code----credential, using literal fallbacks 无辅助邮箱 and 无2fa. Copy export_line unchanged or join multiple lines to export TXT. Ordinary mobile and web subscriptions do not expose credential exports.
For a failed, refunded order under the same card and email, resubmit with a new request_id to requeue its original task ID, even if credentials are unchanged. The Worker deletes the old browser profile and creates a fresh one before execution. The original plan, price, completed PSC and subscription stages are retained; only unfinished work is reserved and executed. Cancelled orders still require changed credentials to requeue. Queued, running and successful orders only update credentials. Reuse the original request_id and payload after an uncertain network result; a replay never reserves points or starts work twice. Check status for the current state.
AI integration prompt: activation and subscription bundles
Integrate https://pixel.geminixs.us/api-doc?lang=en#ag-activation as a dedicated page. Preserve existing subscription pages.
POST /openapi.php with cdkey; submit_task submits and get_status queries.
Check ag_activation.configured first. Activation-only uses ag_activation.cost_points. Bundles require a currently listed bundle whose subscription is available in the card’s plans; add subscription cost_points and activation cost_points. Omit plan_months.
If a subscription already exists, return subscription points and continue activation. If subscription succeeds but activation fails, return only the activation point.
Persist task_id/request_id per request. Reuse original identifiers and data after uncertain responses.
List task_type=ag_verify includes all activation and bundled orders. Paginate with limit/offset and poll about every 5 seconds.
Display subscription_outcome, activation_status, charged_points and refunded_points separately.
Keep credential_available distinct from ag_verified. Allow export as soon as the credential is saved, including failed tasks with a credential.
Copy export_line unchanged; join lines for TXT, keeping literal fallbacks 无辅助邮箱 and 无2fa.
Resubmission updates authentication only; retain the original ID, plan and price. Requeue only unfinished stages.
Show credential exports only for activation services and enforce the original card's ownership.Web · Error reference
HTTP 200 and success:true mean the query succeeded, not that the task succeeded.
success:false → inspect error/message. Validation rejection creates no new task or charge. Confirm the original order after a network error or 5xx.
data.status:"failed" → inspect status and settlement_status; diagnostic fields are not returned.
When settlement_status is refunded, the reservation has already been released. Do not issue another client-side refund.
The following categories are for administrator diagnostics; customer task responses do not include reason fields.
| error_code | Customer message | Next action |
|---|---|---|
password_error | Incorrect password | Check credentials. No automatic retry. |
twofa_error | 2FA / backup code error or no available verification method | Provide a valid secret, backup code or recovery email. No automatic retry. |
captcha_no_sms | Phone verification is required | Resolve account verification manually. |
no_offer | No offer available | The account does not qualify for the offer. Automatic retries stop. Check settlement_status for accounting. |
payment_error | Payment error / Payment currency mismatch | Check payment information or contact support. Explicit setup errors stop retries. |
initial_already_subscribed | Subscription already existed at the first login | Further work is blocked. Use an eligible account; changing cards does not clear the record. |
initial_subscription_unconfirmed | Initial subscription status could not be confirmed | Contact support. An unknown result is not treated as unsubscribed. |
disconnected | Connection lost | Refresh final status and accounting before another submission. |
failed / unknown | Task failed | Keep the task ID and contact support. |
Customer API progress messages
During processing, message (and msg for web tasks) contains only 处理环境, 登录中 or 订阅中. Terminal tasks return an empty message; use status for success, failure or cancellation. Web tasks omit error_code, login_error and payment_error; mobile tasks retain raw_status. Result links, credentials and settlement fields retain their existing contracts. Request validation and authentication errors still return success:false and error/message.
| initial_subscription_status | Meaning |
|---|---|
pending | No confirmed initial result yet. |
clear | No subscription at first login; subsequent stages skip this check. |
preexisting | Already subscribed at first login; hide retry actions. |
managed | This system already has completed subscription/stage evidence; do not classify it as initially subscribed. |
Request rejection codes
| HTTP | error | Action |
|---|---|---|
| 400 | invalid_body / invalid_json / invalid_parameter | Check JSON and required fields. |
| 400 | twofa_error | Provide valid verification data; backup codes must be strings. |
| 400 | invalid_plan / invalid_task_type / web_single_task_required | Use an enabled plan_code returned for your card; one account per request_id. |
| 401 | missing_cdkey / invalid_cdkey | Check credentials. |
| 403 | cdkey_disabled / insufficient_balance | Check card status and available points. |
| 404 | task_not_found | Check task ID and card ownership. |
| 409 | dedicated_worker_required | Ask the administrator to bind the card to a dedicated Worker before submitting new orders or restarting failed tasks. |
| 409 | idempotency_conflict | Do not change the payload for an existing request_id. |
| 409 | task_in_progress / task_not_cancellable | Query the original task. |
| 409 | submission_limit_reached / plan_not_configured | Contact support. |
| 409 | initial_already_subscribed | An existing subscription blocks opening another one. Resubmitting the original failed order performs a fresh check; changing cards does not bypass the stored restriction. |
| 5xx / timeout | internal_error / unconfirmed result | Query first; reuse the original request_id and payload if needed. |
Web · Code examples
Replace the placeholder card and account values. Examples run on your server.
Web · AI integration prompt
Copy this prompt and add your project stack.
View integration prompt
Integrate my project with the Pixel2 Cloud Web Subscription API.
Documentation: https://pixel.geminixs.us/api-doc?lang=en#web-subscriptions
Errors: https://pixel.geminixs.us/api-doc?lang=en#web-errors
Endpoint: POST https://pixel.geminixs.us/openapi.php
My project stack: [fill in]
Read the documentation first. Do not invent endpoints or fields.
1. Use a cdkd card in Authorization: Bearer. Read credentials from the environment; never put secrets in public frontend code or logs.
2. get_balance returns available_points, reserved_points, spent_points. Read the enabled plans and their cost_points from plans; preserve the returned plan_code to distinguish services. Never hard-code prices. Do not mix mobile remaining_uses or capitalized statuses into web handling.
3. submit_task: one account and one stable request_id. Provide task_type, email, password, and valid twofa or recovery_email. twofa is a Base32 secret or an 8-digit backup code string preserving leading zeros, not a 6-digit rotating OTP.
4. Save task_id/request_id. Poll get_status every 5 seconds while queued/dispatched/running. Stop at succeeded/failed/cancelled. success:true only describes the request, not completion.
5. For a failed, refunded order under the same card and email, resubmit with a new request_id to requeue its original task ID, even if credentials are unchanged. The Worker deletes the old browser profile and creates a fresh one before execution. The original plan, price, completed PSC and subscription stages are retained; only unfinished work is reserved and executed. Cancelled orders still require changed credentials to requeue. Queued, running and successful orders only update credentials. Reuse the original request_id and payload after an uncertain network result; a replay never reserves points or starts work twice. Check status for the current state.
6. During processing display only the returned stage label: 处理环境, 登录中 or 订阅中. Terminal task messages are empty; use status for the outcome. Do not depend on task error_code/login_error/payment_error fields.
7. initial_already_subscribed stops this attempt. Explicit customer resubmission of a failed order performs a fresh subscription check. Stages completed by this system remain intact.
8. initial_subscription_unconfirmed stops work for review. Do not treat it as unsubscribed. Settlement is reserved/captured/refunded; never refund twice in the client.
9. cancel_task only cancels queued tasks. Distinguish HTTP error/message from task status inside data.
10. Deliver runnable code, configuration instructions and mocked tests. Do not use private admin/Worker endpoints or run real purchases during integration tests.Mobile · Balance
CDK subscriptions and CDK1 link extraction use a separate mobile ledger. get_balance/stats returns remaining_uses. Submission deducts one use per task; pending_queue_cost is zero.
{
"action": "get_balance",
"cdkey": "YOUR_CARD_KEY"
}{
"success": true,
"message": "查询成功",
"key_type": "subscribe",
"remaining_uses": 9,
"pending_queue_cost": 0,
"status_counts": {
"pending": 1,
"running": 0,
"success": 3,
"failed": 0,
"cancelled": 0
}
}Mobile · Submit tasks
Use submit_task/submit. CDK automatically selects run_all; CDK1 selects extract_link. A supplied task_type must match the card. Every account requires email, password and twofa (or totp). Recovery email is not supported.
Choose exactly one input shape: single-account fields, a tasks array, or account_data text with email----password----2FA or backup code per line. Up to 100 accounts; batch validation is atomic.
Use backup codes as strings; 8 digits gain the bym- prefix once. Keep leading zeros. Existing active emails cannot be submitted again; the default limit is 10 submissions per email, including deleted history; the actual limit follows the service configuration.
{
"action": "submit_task",
"email": "[email protected]",
"password": "YOUR_ACCOUNT_PASSWORD",
"twofa": "YOUR_2FA_SECRET"
}{
"success": true,
"message": "已提交 1 条任务",
"submitted_count": 1,
"task_type": "run_all",
"cost_per_item": 1,
"remaining_uses": 9,
"task_ids": [
"550e8400-e29b-41d4-a716-446655440000"
],
"task_id": "550e8400-e29b-41d4-a716-446655440000"
}Batch JSON or multiline input
{
"action": "submit_task",
"tasks": [
{ "email": "[email protected]", "password": "PASSWORD_A", "twofa": "2FA_SECRET_A" },
{ "email": "[email protected]", "password": "PASSWORD_B", "totp": "2FA_SECRET_B" }
]
}{
"action": "submit_task",
"account_data": "[email protected]_A----2FA_SECRET_A\[email protected]_B----2FA_SECRET_B"
}Mobile · Query tasks
Use get_status/list/detail. Authenticate with the owning card and pass task_id or email, not both. Without either filter, data is an array. Poll every 3–5 seconds; times are Beijing time (UTC+8).
| status | raw_status | Action |
|---|---|---|
| Pending | queued | Continue polling; cancellation is allowed. |
| Running | running | Continue polling. |
| Success | done | Stop polling; read link when present. |
| Failed | failed or a specific error | Stop polling and inspect status/raw_status. |
| Cancelled | cancelled | Stop polling. |
{
"action": "get_status",
"task_id": "550e8400-e29b-41d4-a716-446655440000"
}{
"success": true,
"message": "查询成功",
"data": {
"id": "550e8400-e29b-41d4-a716-446655440000",
"email": "[email protected]",
"status": "Success",
"raw_status": "done",
"message": "",
"task_type": "run_all",
"link": "",
"percent": 100,
"created_at": "2026-11-06 12:00:00",
"updated_at": "2026-11-06 12:03:00",
"completed_at": "2026-11-06 12:03:00"
}
}List example
{
"action": "list",
"limit": 100,
"offset": 0
}{
"success": true,
"message": "查询成功",
"data": [],
"total": 0,
"limit": 100,
"offset": 0
}Mobile · Cancel a task
cancel_task/cancel requires the task_id of an owned queued task. Running and terminal tasks cannot be cancelled. A successful cancellation refunds one use and moves the record to trash; repeated cancellation does not refund again.
{
"action": "cancel_task",
"task_id": "550e8400-e29b-41d4-a716-446655440000"
}{
"success": true,
"message": "任务已取消,已退还 1 次使用次数",
"cancelled_count": 1,
"refunded": 1,
"remaining_uses": 10
}Mobile · Errors
HTTP rejection uses success:false, error and message. A successful query can still contain a Failed task. Mobile failures follow the existing manual handling process; do not apply web-point refunds.
The following categories are for administrator diagnostics; customer task responses do not include reason fields.
| raw_status | Meaning | Action |
|---|---|---|
| password_error | Incorrect password | Verify credentials. |
| totp_error / totp_invalid / totp_not_enabled | 2FA verification failed or not enabled | Check the secret/backup code and account settings. |
| ineligible | Account is not eligible | Check account requirements. |
| captcha | Account verification required | Resolve verification manually. |
| account_suspended / account_error | Account issue | Check account access. |
| payment_error | Payment profile issue | Contact support with the task ID. |
| google_server_error / failed / unknown | Service error or failed task | Keep the task ID and contact support. |
{
"success": false,
"error": "insufficient_balance",
"message": "卡密剩余次数不足,本次需要 1 次"
}| HTTP | Codes | Action |
|---|---|---|
| 400 | invalid_body / invalid_json / invalid_parameter / invalid_action | Check JSON, action and required fields. |
| 400 | invalid_task_type / unsupported_parameter | Do not send web plans or recovery_email to mobile cards. |
| 400 | invalid_submission_format / batch_size_exceeded / duplicate_email | Choose one input shape with 1–100 unique accounts. |
| 401 | missing_cdkey / invalid_cdkey | Use valid credentials. |
| 403 | cdkey_disabled / insufficient_balance | Check card status and uses. |
| 404 | task_not_found | Check task ownership and deletion state. |
| 405 | method_not_allowed | Use POST. |
| 409 | task_in_progress / submission_limit_reached / task_not_cancellable | Check task state and submission count. |
| 413 | payload_too_large | Keep request below 10 MB. |
| 500 | internal_error | Query original tasks before resending. |
Mobile · Code examples
Replace the placeholder card and account values. Examples run on your server.
Mobile · AI integration prompt
Copy this prompt and add your project stack.
View integration prompt
Integrate my project with the Pixel2 Cloud Mobile API.
Documentation: https://pixel.geminixs.us/api-doc?lang=en#submit
Endpoint: POST https://pixel.geminixs.us/openapi.php
My project stack: [fill in]
1. Authenticate with a CDK/CDK1 card in Authorization: Bearer, loaded from the environment. Never log account credentials.
2. get_balance returns remaining_uses. CDK selects run_all subscription; CDK1 selects extract_link. Each new task costs one use. Do not send web point plans, recovery_email or web request_id conventions.
3. submit_task accepts one email/password/twofa account, a tasks array, or account_data lines. Select exactly one format, at most 100 accounts. Use a Base32 secret or an 8-digit backup code string preserving leading zeros; not a 6-digit OTP.
4. Batch validation is atomic. Invalid accounts, duplicate emails or insufficient balance reject the whole batch. Save returned task_ids.
5. Poll get_status by task_id or email every 5 seconds. data.status is Pending/Running/Success/Failed/Cancelled; raw_status retains the specific failure. Stop at terminal status.
6. Use status/raw_status for task outcomes. During processing, message is one of 处理环境, 登录中 or 订阅中; terminal messages are empty.
7. cancel_task can cancel only queued tasks owned by the card, refunds one use and moves the record to trash. Mobile failures follow the service's manual handling process, not automatic web-point refunds.
8. After an unconfirmed network result, query the original account/task before resubmitting. Do not invent mobile request_id idempotency. Distinguish success:false requests from queried Failed tasks.
9. Deliver working code, configuration and mocked tests. Do not use admin/Worker endpoints or run real purchases during tests.