A clear path from
sign-in to your first project.

Your first coding session

Start with five small steps. No API knowledge needed.

Your account brings your coding apps, model choices, credit and support together. You can use a ready-made app or connect your own application through the API.

1. Create or sign in to your account. Use the site where you registered. Create an account or sign in.
2. Confirm your email. Follow the verification message and complete any profile or security checks shown.
3. Check your access. Open your dashboard to see your Credit Wallet, active package and any remaining coding time. Visit Pricing if you need access.
4. Open the Setup Wizard. Choose an app, your operating system and a model. Follow the instructions for that exact combination.
5. Open a project and ask for a small change. For example: “Explain the files in this project before changing anything.” Review any file or terminal permissions your app asks for.

Create an account and verify your email

Find your account, confirm your inbox and reach the dashboard.

1. Choose Create an account and enter an accurate name, email and password. Keep a record of the site you used.
2. Open the verification email. Check Spam or Junk if it is missing. Use the latest verification link or code you requested.
3. Return to the site and sign in. If the site asks for an email code or authenticator code, enter it on the sign-in screen.
4. Complete any required name, mobile or email-correction form. When an email correction is required, verify the new address before continuing.

If you see “already registered,” use Sign in or password recovery instead of opening another account. Reseller enrollment separately limits duplicate people/device/network registrations.

Sign in, recover access and sign out

Use the correct account and complete security checks.

1. Open Sign in on your registered site. Enter the email or username the form requests, and your password.
2. Complete email verification or two-factor authentication if prompted. A login code and your API key are different things.
3. For a forgotten password, use Forgot password on that site. Open the newest recovery email and set a new password.
4. Use Sign out on a shared device. To disconnect a separate integration, revoke that integration’s API key in the dashboard.

Accounts and balances are not automatically interchangeable between all four brands. Use the account and API address your dashboard supplies. Some managed apps can find your account site automatically; if an app asks, select the site where you registered.

Find your way around the dashboard

Know where each setting, balance and setup tool lives.

Labels can differ slightly between sites. The guide’s dashboard buttons open the relevant section. Options that depend on a plan, device or available offer appear only when eligible.

Use the Setup Wizard

One app, one operating system, one clear set of instructions.

1. Open Setup Wizard from your dashboard. If you see Quickstart, open it to reach setup.
2. Choose your coding app. Then select Windows, macOS or Linux where that app supports it.
3. Pick a model from the choices shown. Choose reasoning effort if the app and model support it.
4. Keep the recommended connection region unless you have a reason to choose another available region. VIP choices require eligible access.
5. Copy the complete script, or download the installer/configuration the wizard provides. Read the instructions outside the code box before running it.
6. Run the script on your own computer, in the terminal the wizard names. Open the installed app and follow its connection instructions.
7. Open a project and send a small test request. Keep your setup details private: a personalized script can include your own credential.

Choose the right coding app

A practical comparison of every setup option.

You do not need a direct account with each model provider to use your service account. Native consumer desktop products are different from the managed clients listed here. Use the download your dashboard identifies, rather than an app with a similar name.

Set up codexclaude

Start a terminal coding session from your project folder.

1. In the wizard, select codexclaude and your operating system. Choose your model and connection.
2. Run the full setup command the wizard supplies. It installs the managed launcher and its supported Codex runtime.
3. Open a terminal in your project folder. On Windows, open the folder and choose Open in Terminal; on macOS/Linux, open Terminal and change to the folder.
4. Run codexclaude. Complete any sign-in requested by the launcher.
5. Use its model picker to select a model and supported effort. Check the account/status display for wallet credit, plan windows and any Unlimited timer.
6. Ask for one small task. Approve local file, terminal or network actions only when you understand them. Review the changes before applying them to production.

cd /path/to/your/project
codexclaude

For an update requirement, rerun the current dashboard setup or accept the managed updater. The launcher’s package version and the underlying Codex CLI version are separate; check both if support asks. Do not repeatedly install an old downloaded archive.

Set up claudecodex

Use a managed Claude Code-style terminal workflow.

1. Choose claudecodex in the wizard and run the setup for your operating system.
2. Open your project folder in a terminal, then run claudecodex. Sign in when asked.
3. Review the status banner. It can show your membership and expiry, Credit Wallet, plan-window usage and available Unlimited time.
4. Choose a supported model from the launcher. Select only effort/fast-mode options offered for that model.
5. Describe your task. Inspect proposed changes and approve local tools as needed.

cd /path/to/your/project
claudecodex

The model picker and account banner belong to the managed launcher. If your terminal opens a different native Claude installation, rerun setup and check which command it installed. Updates may be mandatory when an older client is no longer compatible.

Set up native Codex CLI or Claude Code

Keep your preferred native terminal workflow.

1. Open the wizard and choose Codex CLI or Claude Code. Select your operating system.
2. Choose a model that the wizard allows for that native app. Native client families do not expose every cross-family model selection.
3. Run the supplied setup script. It downloads the supported current app and merges the service connection settings.
4. Reopen your terminal, enter your project folder and start the app with the command shown by the wizard.
5. Confirm the selected service/model before your first pass. If you need the extended model picker, choose codexclaude or claudecodex instead.

A web subscription, a dashboard login, a native app’s provider login and a service API key are distinct credentials. Follow the service setup instructions rather than changing unrelated provider accounts.

Set up Claude Desktop on Windows

Install, connect, open a project and keep the app current.

1. Open Claude Desktop or choose it in the wizard. Download the current Windows installer from your dashboard.
2. Finish any existing coding work. Run the installer and approve the genuine Windows administrator prompt when requested.
3. If you used a personalized setup, follow the account-import instructions; otherwise sign in with your service account. Do not create a direct provider account just to use this client.
4. Create a chat or choose a project folder. Grant the app access only to the project you want it to use.
5. Pick your model and ask for a small task. Review tool/file permissions, proposed edits and terminal actions.
6. Use the app’s settings for supported local integrations, account controls and updates. Keep one account’s project history separate from another account.

Desktop/Start shortcuts and existing owned taskbar links are repaired during a managed update. Windows may ask for consent before creating a new taskbar pin. The coding app runs as your normal interactive user; the installer’s administrator approval is for installation/owned cleanup.

Install updates and replace older desktop versions

Use current installers without deleting your account history.

1. Save your work and allow active tasks to finish. Open the update notice or the app’s update settings.
2. Choose the verified update/install option. Approve Windows UAC when the installer asks.
3. Leave the updater running while it prepares owned app instances, saves drafts and removes supported older installations.
4. Open the updated app from its repaired shortcut. Confirm the version shown by the app or dashboard download label.
5. If the update is canceled or fails, record the exact message and installed version. Use the current dashboard installer and contact support if it still reopens an older version.

Do not delete your AppData/profile folder as an update fix: it can contain encrypted connections, chats, drafts and project settings. An update may need time to finish active work; repeatedly launching installers can create competing update attempts.

Set up VS Code and Cursor

Connect inside your editor and keep tools under your control.

1. Choose VS Code or Cursor in the wizard. Install the supported editor first if the instructions require it.
2. For VS Code, download the service extension from Setup Extensions. Use Extensions → … → Install from VSIX when the dashboard provides a VSIX file.
3. Run the extension’s connect/sign-in command and complete any verification or two-factor check.
4. Choose a supported model/effort and open your project. Keep existing workspace/provider settings unless the wizard explicitly asks you to change them.
5. Allow local filesystem, terminal or MCP operations only for work you intend to authorize. Inspect changed files before committing them.

Cursor setup and VS Code extension setup are different integrations. An app may filter incompatible models; do not force a model by forging another app’s identity. If you switch account or model, start a fresh chat when existing reasoning/tool state cannot be carried over safely.

Set up Antigravity

Install and configure the integration in one guided sequence.

1. Choose Antigravity in the wizard, then your operating system and an available model.
2. Copy the complete all-in-one script and run it locally in the named terminal. It installs/configures the supported integration for your own account.
3. Open the app and select your project folder. Check the service connection and chosen model.
4. Send a small task and review local tool approvals. Keep any existing Google profiles and unrelated settings unless you deliberately change them.

Use the current wizard’s compatibility list rather than assuming every third-party Antigravity feature is available through every model. Existing provider subscriptions and service API usage are separate products.

OpenCode.ai, Zed, OpenClaw and Hermes

Use the matching setup instead of copying another editor’s configuration.

1. Open Setup Extensions or the Setup Wizard and choose the exact app.
2. Select an operating system and model supported by that app. Follow the installation steps shown, including any prerequisite app download.
3. Apply the generated provider configuration or setup script. Keep backups and preserve other providers/workspaces.
4. Open a local project, select the service’s configured provider/model and submit a small test task.
5. If the app reports an unknown provider/model, compare the base URL, API-key field and model ID with your current wizard output.

OpenCode.ai also has its own dashboard setup section. Zed, OpenClaw and Hermes are grouped under setup extensions on some sites. The app’s local tool permissions remain local; buying API access does not automatically grant terminal or filesystem access.

Desktop Chat and Windows Management Tool

Understand the separate chat and setup applications.

Desktop Chat: open its dashboard download page, choose an available Windows/macOS build, install it and follow the service sign-in/setup instructions. Select a model, start a conversation and use the features shown by that build. Check your balance before paid chat requests.

Windows Management Tool: download it from Windows tools, run it with the requested administrator approval, sign in and select the client you want to install or configure. Review the detected app and account before applying changes. It can manage supported Codex/managed-client configuration and current model lists.

Use a coding client for project-file or terminal work. A chat conversation alone does not authorize an app to run commands on your device. Some desktop downloads depend on your plan or operating system.

Chat, Cowork, Projects and history

Choose the workspace that matches the work you want to do.

1. Use New Chat for a fresh conversation. Choose Chat for questions, Research for source-based investigation, or Cowork for supported project/task work.
2. Use Projects or the folder button to connect the intended local folder. Select the project before asking the app to inspect or change files.
3. Use the sidebar/history search to reopen an existing conversation. Start a fresh chat after switching accounts or when incompatible model state cannot be reused.
4. Use Stop to cancel a current task, then inspect any work already completed. Do not assume cancellation undoes file changes.
5. Use the account/model controls to confirm who is signed in, which model is selected and what access remains.

Enter sends a message; Shift+Enter adds a line. Use the keyboard shortcuts shown by your installed build. A conversation history entry and a local project folder are separate: deleting a chat does not mean a file edit is reverted.

Attach files, images and spoken prompts

Give the model the material needed for your task.

1. Choose Attach and select the intended files/images, or use drag-and-drop where supported.
2. Review the attachment list before sending. Remove the wrong file and check that you have permission to share its contents.
3. Choose a model/mode that supports the supplied content. A model or account restriction can make an attachment or image option unavailable.
4. For the Mic option, allow the required microphone permission only if you want voice input. Review the transcribed prompt before submitting.
5. Send the request and inspect the answer; an attachment is not automatic permission to execute anything inside it.

Available image/voice features depend on the current build, device and model. The Image response mode is separate from attaching an image for analysis. Follow any stated limits or unsupported-feature message rather than repeatedly resending a large file.

Web research and answer comparison

Use sources and a second perspective without losing context.

1. Choose Research or enable the Web search control when the current workflow supports it.
2. Ask a focused question and specify any date/location constraints. Check the actual sources/citations returned.
3. Open the comparison control when you want another model perspective. Choose a compatible model and explicitly start the comparison.
4. Review both answers against the task and sources. A comparison is an additional generation request and can consume its own credit/time.
5. Use Stop to cancel work you no longer need. Keep the request ID for a failed search or comparison.

Do not treat an unsourced answer as a successful live search. Tool/provider failures should remain visible. Research and comparison use the service models and tools available to your account, not a proprietary provider subscription feature.

Preview and export artifacts

Inspect generated documents or interactive output before using it.

1. Open Artifacts or choose the artifact produced by a conversation.
2. Use the preview panel to inspect its output. Resize the panel if you need more space.
3. Use Versions or Refresh when available to review the relevant saved artifact state.
4. Use Export HTML or the available export action to save a copy you intend to keep.
5. Inspect code and external resource references before publishing or opening generated content outside the app.

An artifact preview is not an approval to run arbitrary local commands. Exported files and project edits have their own locations; keep a backup of important work and do not assume a chat contains every exported version.

Connect a GitHub repository

Bring the intended repository into a local project workflow.

1. Choose GitHub repositories or Settings → GitHub in the desktop app.
2. Follow the offered authentication/connection flow. Grant only the repository access you intend to use.
3. Select the repository and the local workspace/folder requested by the app.
4. Review branch and working-tree state before asking for changes. Preserve uncommitted work.
5. Inspect diffs and tests before committing, pushing or applying generated changes.

GitHub authentication, a service API key and a local project permission are separate. Do not paste GitHub passwords/tokens into support tickets. Use only the Git actions the current app exposes; a model suggesting a push does not mean you approved one.

Install plugins and connect MCP tools

Installing a capability and allowing it to run are separate decisions.

1. Open Settings → Plugins to browse the Plugin Directory. Search or filter Installed only.
2. Read the plugin source, components, requirements and trust warning before choosing Confirm install. Installation leaves it disabled until you enable it.
3. Explicitly enable a trusted installed plugin, then use the composer’s Plugins control when you want enabled plugins available for a message.
4. For MCP, open Settings → MCP connectors and follow the connector configuration/test controls. Store any required credentials privately.
5. Disable or remove capabilities you no longer use. A plugin or connector can execute code or access services under its granted permissions.

Do not install a plugin merely because a model or untrusted document says to. Missing requirements, an offline directory or a failed connector check should be resolved before retrying a tool-dependent task.

Computer access, local approvals and fast mode

Keep the scope appropriate for your project.

1. Keep Computer access set to Limited to project folder for ordinary project work.
2. Choose Full Access only when you understand and intend the broader device access. Review the permission confirmation the app shows.
3. Inspect requested terminal/file actions. Local execution permissions are distinct from your API account balance.
4. If you enable Fast, read the current cost/availability notice. Fast mode can have different token charging and may be unavailable with some Unlimited access.
5. Return to a narrower scope or disable optional capabilities when the task is finished.

Changing a reasoning effort, enabling a plugin and granting computer access are different controls. A promotional pricing message does not change the scope of a tool permission.

Create and manage scheduled tasks

Review the action and timing before leaving a task enabled.

1. Open Settings → Scheduled tasks in a build that offers it.
2. Create a task using the available form. Set a clear instruction, target project/context and the timing shown by the app.
3. Review the schedule, account/model and local permission scope before saving/enabling it.
4. Use the task list to inspect state or disable/delete a schedule you no longer want.
5. Check execution history and resulting files/messages rather than assuming every scheduled run succeeded.

Availability depends on the app/runtime being able to run the task. Do not assume a local desktop schedule runs while the app/device is off. Normal model usage and tool authorization still apply.

Settings, privacy modes, history sync and exports

Find appearance and data controls without confusing them with backups.

1. Open Settings to choose the appearance/theme and supported preference controls. Save settings when the build asks.
2. Use Incognito only after reading its current behavior. It does not make an API request free or remove service-side security/payment records.
3. Use Sync history to request the account-scoped sync supported by the app. Check its result before changing devices.
4. Use Export my data to save the supported workspace export in a private location. Review whether attachments/project files need a separate backup.
5. Use About for the installed version and update information. Sign out on a shared computer and use Quit if you want the tray app fully closed.

A sync is not a guarantee that every local file, credential or external connector is backed up. Keep exports private and maintain independent project backups.

Choose a model

Use the public catalogue and your app’s compatibility list.

Open Models or your app’s picker. The current public service catalogue includes the selections below. Availability can differ by app, account and supported endpoint; authenticated GET /v1/models is the API client’s source of available IDs.

1. Start with the default suggested by your app if you are unsure.
2. Use the exact model ID in API requests. In a desktop/terminal app, use the named picker instead of editing request headers.
3. Choose a supported reasoning effort. If an option is absent, that app/model combination may not support it.
4. When changing models during a long tool conversation, start a fresh conversation if the client asks. Preserve full continuation state in custom integrations.

Use power-ai 4.5

Find the managed coding option and check eligibility.

1. Open the wizard or supported model picker and look for MagnetAPI.org — power-ai 4.5 / power-ai.
2. If the option is greyed out, read the eligibility message. It is restricted to eligible Lite-or-higher subscriber access; the account’s current entitlement check is authoritative.
3. Choose an available compatible app and generate its setup. Send a small coding task to confirm the connection.
4. For a connection error, include the app, selected model and request ID in your support report.

power-ai is a managed service selection, not a separate API key or a reason to change your private credentials. Do not guess internal model names or routing settings.

Reasoning effort, fast mode and model status

Control supported request settings and understand the price shown.

Reasoning effort is a request setting such as Low, High or Extra High. More effort can mean more processing time and reasoning tokens. Select only options shown for the model you use. Fast mode is a separate option and may be unavailable while certain Unlimited access is active.

1. Open the app’s model/effort controls. Choose a supported value and confirm the model before sending your next pass.
2. Read the account rate/effort notice currently shown by the app or dashboard. A temporary equal-effort pricing offer is not a permanent guarantee.
3. Check Usage & activity after a test pass. Input, output, cache and reported reasoning usage can affect the charge according to your saved rate card.

Managed codexclaude and claudecodex usage can receive the managed-client saving shown by your account. That saving does not automatically apply to every editor or a custom application.

Projects, files, terminal tools and MCP

Let the client work on the intended project, with your approval.

1. Create or open a project folder in your chosen coding app. Keep important work in source control or a separate backup.
2. Describe the outcome and any constraints: files to touch, commands to avoid, and how you want the result tested.
3. Review each permission prompt. A model proposing a command is different from your app executing that command.
4. Use MCP or local tool integrations only when your app offers them. Configure server credentials locally and keep them out of shared chats.
5. Inspect changes, run the project’s checks and decide whether to keep or revert them.

The API can return structured tool calls, but your application owns tool execution. The service does not automatically gain access to your computer, project or database when you create an API key. Long operations and updates should be allowed to finish safely.

Connection regions and VIP access

Use available regions without changing your account identity.

1. Open the wizard’s connection/region selector, or your dashboard’s connection settings.
2. Keep Automatic when you do not need a specific location. Choose another available standard region if the wizard offers it.
3. Use Frankfurt VIP only when your account has active VIP access and the chosen client is approved for it.
4. Generate the new connection instructions and restart the client’s connection after its current pass finishes.

Use the exact region URL supplied for your site. Do not send a site’s key to a guessed hostname. VIP provides eligible regional access; it does not remove key restrictions, funding requirements or unsupported-model errors.

An active Flex package provides its included VIP access for that package’s lifetime, including while paused until expiry. Separate paid VIP benefits keep their own terms.

Understand your wallet and credits

Separate purchased money, plan allocations and coding time.

Open Wallet & payments to see the balances and transaction history your site exposes. Look at the resource label before buying or using it; an Unlimited purchase buys time, not a generic cash-wallet deposit.

Add credit with PayPal or Paymento crypto

Complete a payment and confirm that the correct benefit arrived.

1. Open Topup / Credits. Choose wallet credit or the exact package you want.
2. Review the amount, currency, discount, account email and product description on the confirmation screen.
3. Choose PayPal or Paymento cryptocurrency. A payment approval or card-saving/recurring consent applies only if that checkout explicitly offers it and you accept.
4. For crypto, select the correct coin and network and pay the quoted amount before the payment deadline. Follow the provider’s address/network instructions exactly.
5. Return to the site after payment. Refresh Wallet & payments and check both the payment status and the purchased balance/package.
6. Keep the order/payment reference and receipt. If payment is complete but the benefit is missing, open a support ticket instead of paying for the same order again.

Pending crypto confirmations are not proof that funds have cleared. Do not reuse an expired quote or send a different network/amount without checking its instructions. Never send support full card numbers, wallet seed phrases or payment passwords.

Buy and start an All Models Unlimited session

Understand the timer before your first pass.

1. Open Pricing or Unlimited sessions. Choose an available duration and Standard or Flex option.
2. Read the model scope, pause support, usage-window labels, activation and maximum expiry before paying. Not every duration offers both variants.
3. Complete the checkout and find the purchase in your dashboard. Multiple allocations can be queued; the dashboard shows which one is active.
4. Submit your first eligible coding pass to start unused coding time. Login, purchase, gift issuance and dashboard reads do not start an unused countdown.
5. Watch the active timer and remaining time. Once a pass is admitted, a later provider failure does not rewind elapsed coding time.

Queued, paused, expired or incompatible allocations cannot pay for the current request. Older Claude-only purchases retain their original scope even though they are no longer offered as new public plans. New All Models offers cover supported public model selections, subject to app compatibility.

Standard, Flex and Platinum: what differs

Read window labels without confusing them with a clock or wallet.

A five-hour window starts with the first coding pass and resets exactly every five hours from that start. It is a usage allowance, not five continuous hours of free wall-clock time. A reset does not refill a separate monthly plan allocation. The dashboard reports usage without exposing private allowance budgets.

Where a 24-hour window is currently disabled, its card shows that status rather than invented usage. If an eligible limit is activated, check the card’s actual usage/reset information. Do not assume that all Flex products have Platinum terms.

Pause, resume and stack coding time

Keep track of remaining time and absolute expiry.

1. Open Unlimited sessions and find an allocation marked Pause Enabled. Read its remaining time and final expiry.
2. Finish any active coding pass, then use Pause. Pausing does not interrupt or undo work already admitted.
3. Use Resume when you want that eligible allocation available again. A paused allocation cannot pay for new passes.
4. For another purchase, review its queue position. Stacking normally preserves finite benefits by letting queued allocations activate after earlier access is depleted.
5. If a screen offers replacing existing access immediately, read and explicitly accept any forfeiture warning. Choose stacking when you want to keep existing benefits.

Pausing preserves eligible remaining coding duration, not the allocation’s absolute final expiry. Flex VIP remains available while paused until Flex expires. Where the dashboard offers a reset token, read which active window it resets before confirming; it does not create a new package or wallet deposit.

Existing memberships and included benefits

Review your tier, period, windows and eligible rewards.

1. Open Membership or your plan card. Check the active tier, expiry/renewal date and billing period.
2. Review the five-hour and any configured 24-hour usage windows separately from your monthly allocation.
3. Use the models available in your authenticated catalogue. Existing Lite-and-higher memberships include the public model range, subject to normal access/client checks.
4. If your dashboard offers an included/free Unlimited reward, choose Redeem and confirm that it appears in your allocations. Unused time starts on the first eligible coding pass.
5. Review renewal/cancellation controls for that exact contract. A prepaid package and an explicitly authorized recurring membership do not renew in the same way.

The public pricing page currently focuses on Standard/Flex Unlimited offers. Existing saved memberships and paid benefits keep their terms; this guide does not reopen retired products or promise a benefit that your account does not show.

Track usage, windows and each coding pass

Read real measurements and keep a useful request reference.

1. Open Usage & activity. Choose the date range or request view your dashboard offers.
2. Check your Credit Wallet and plan card separately. Compare the model, time, request ID and available token/charge details.
3. For a limit, read its start/reset time and percentage used. A five-hour window, 24-hour window and monthly allocation are separate.
4. For a current API pass, use the live usage endpoints. Some providers report final counts only when the request completes.
5. If a figure looks wrong, give support the request ID and approximate time, with the relevant receipt or screenshot.

Unreported token counts remain unknown, rather than zero. Live telemetry is diagnostic; a browser’s local estimate is not a payment receipt. Account/usage reads do not start unused Unlimited time or reserve a new coding allowance.

Payments, receipts and refund requests

Keep enough information to resolve an order without exposing payment secrets.

1. Open Wallet & payments and find the payment/order entry for the exact product.
2. Compare the method, amount, status, account and resulting benefit. Save the receipt/reference where available.
3. For pending crypto, read the confirmation/payment deadline status. For PayPal, distinguish an approved checkout from a completed payment.
4. If a settled order is missing its benefit, submit one support ticket with the order reference and approximate payment time.
5. Read the published refund policy for the site/product before purchase. Request any case-specific review through support rather than assuming a refund is automatic.

For MagnetAPI, the Refunds policy explains the published policy and review process. Never include full card details, payment passwords or wallet seed phrases in a report.

Create, restrict and manage API keys

Give each app a named key, not your dashboard login.

1. Open API Keys. Complete normal sign-in, email and two-factor checks first.
2. Choose Create User API Key. Give it a clear label, such as “Website production” or “Laptop coding.” Up to 20 active User API Keys are available per site.
3. Allow only the permissions your app needs: account/usage, models, Responses, Chat Completions, legacy Completions or Messages.
4. If offered, set expiry, a spending limit and trusted-IP restrictions. Confirm that your real app/server IP is included before enabling an allowlist.
5. Save the key securely and note the account/site it belongs to. Put it in your application’s server-side environment or secret store.
6. Use the key’s usage/health/security controls to monitor it. Revoke an unused key. For replacement/rotation, update the intended app and confirm it works before removing older configuration.

API Documentation → explains the first request, endpoints, examples, tool calls and live usage.

Profile, email, password and two-factor security

Keep a working verified email and control account access.

1. Open Settings / Profile to review your name, registered email and other requested contact details.
2. Use the email-change or correction flow for an incorrect address. Enter the code sent to the new address; required verification must finish before protected dashboard access.
3. Use Security to set up an authenticator if offered. Follow the QR/secret instructions privately and confirm with your current authenticator code.
4. Change your password through the account/password control, or use recovery if you cannot sign in. Do not reuse a support email as a place to send passwords.
5. Review API-key alerts, trusted-IP rules and key health. Revoke compromised integration keys and update only the apps that used them.

Cookie settings control optional analytics separately from necessary authentication/security. You can review the site’s privacy notice and terms. Required account/email verification is not bypassed by closing a popup.

Redeem a gift card or marketplace purchase

Make sure you are using the right seller and activation flow.

1. Check the seller and exact product you bought. A service gift code and another provider’s API key are not interchangeable.
2. For a MagnetAPI gift, open magnetapi.org/redeem and enter the code in the redemption wizard.
3. In Step 2, enter your accurate email address and complete the verification sent to it. Gift credit is not loaded before email verification.
4. Complete the account/credential steps the wizard shows, then check the dashboard for the promised Credit Wallet and coding time.
5. Submit your first eligible coding pass when you are ready to start unused Unlimited time. Merely redeeming the gift or signing in does not start its coding countdown.

Invite a friend and follow your rewards

Use your own referral link and check eligibility before promising a benefit.

1. Open Referrals and copy your personal referral link.
2. Share the link with your friend so the signup is attributed correctly. Explain the current offer shown on your referral page.
3. If the Discord bot offers /refer, first use its account-linking flow. Enter the friend’s name and email only with their permission, then confirm the invitation.
4. Check referral/reward status in your dashboard. Signup, email verification and a qualifying paid purchase are different milestones.
5. If an invitation or reward is missing, give support the referral/order reference and approximate time. Do not open duplicate accounts to claim rewards.

Referral benefits, qualifying amounts and offer dates can change. Your current dashboard’s terms govern eligibility. A reward is not confirmed merely because an invitation was sent.

Gifts, VPN, daily check-in and raffles

Find eligible extras and distinguish history from an active offer.

1. Open Benefits / Free Offers. Choose the gift, VPN, daily check-in or raffle entry shown for your account.
2. For a gift/VPN claim, read eligibility and stock/availability, then use the claim/redeem button once. Follow the received setup details privately.
3. For daily check-in, open its card and claim when eligible. A cooldown or unavailable message means you should wait or read the current rules.
4. For a raffle, inspect your ticket numbers, qualification rules, closing/draw dates and current status. A past raffle can remain visible as history.
5. If the Discord bot offers a separate raffle command, read that raffle’s own rules; bot and website raffles are not automatically the same draw.

Do not assume a dated promotion, free item or raffle is still active because a historical page exists. Available buttons and current terms determine what you can claim now. Keep issued license/account details out of public messages.

Optional ways to earn API credit

Review what uses your device or internet connection before starting.

Earning features appear only in supporting apps/accounts. They are optional and are separate from buying API access.

CPU mining in Windows Management

1. Open the earning/mining screen and read the current promotion and resource requirements.
2. Choose the offered CPU/memory settings, explicitly authorize the current session and press START.
3. Watch accepted/rejected shares, accepted work and credited transactions. Accepted pool work determines credit; a displayed local speed alone does not guarantee payment.
4. Use STOP to stop mining. Closing to the tray can continue an explicitly started session; Quit, sign-out, update and reboot stop it. A new process requires Start again.

Earn API $ / connection sharing in Claude Desktop

1. Read the connection-sharing/resale explanation. Enabling it allows participating customer traffic to use your residential internet connection and bandwidth.
2. Only opt in if you have permission to share that connection. Review the app’s consent, Windows administrator approval and current earning terms.
3. Press Start and keep the visible sharing controls available. Use Stop whenever you want to end sharing.
4. Review server-verified earning/credit transactions. Keeping a window open is not by itself proof of a paid connectable session; rates can change.
5. Quit, sign-out, update or reboot stops sharing. It does not silently restart in a fresh app process.

Start and use a reseller account

A separate portal for supplying access to your own clients.

1. Open Reseller Program and read the current terms. Register through the MyAPI.world reseller portal.
2. Enter accurate identity/contact details and verify your email. Current enrollment does not require an opening deposit or card.
3. Open your portal and review products, available models, balances, trial inventory and the customer list.
4. When trial accounts are available, assign one to the intended recipient and send their activation instructions. The recipient’s activation/verification steps matter.
5. Choose PayPal or Paymento when you decide to fund your reseller wallet. Review the quote before issuing paid customer access.
6. Use the portal to issue/manage customer products and follow usage. Developers can use Reseller API Documentation for provisioning integrations.

Only one reseller account per person is allowed; duplicate device/IP registrations may be blocked. If you share a legitimate network, contact support. Trial inventory and product availability shown in the portal are authoritative; customer API keys and reseller API keys have different purposes.

Promotions, announcements and the account inbox

Read current notices without assuming an old offer is available.

1. Open Promotions & alerts or the account message/inbox area your dashboard provides.
2. Read the offer’s closing time, time zone, eligible account/product and exact benefits.
3. Open the linked product page and confirm that checkout is still available before paying.
4. Use the account’s transaction/benefit view to confirm a completed purchase or claim.
5. Treat past announcements and expired offers as history. Paid benefits retain their saved terms; a historical page does not reopen new sales.

The dated All Models promotion that closed on 31 October 2026 is not advertised here as a current offer. Current Standard/Flex pricing and the quote you approve are authoritative. Required profile/email/security dialogs remain separate from promotion messages.

Assign reseller trial accounts

Help a new client activate their trial rather than losing it before they arrive.

1. Complete verified reseller enrollment and open the portal’s trial-account inventory.
2. When the starter inventory is available, choose an unused trial and enter the intended recipient’s details.
3. Send the activation invitation and ask the recipient to verify their email and complete their account setup.
4. The current starter suite advertises ten trial accounts, each with $15 trial Credit Wallet, 30 minutes All Models coding time, one day Lite and one day VIP. Check the issued trial’s actual terms/expiry before promising it.
5. Day-long trial benefits start on recipient activation. Unused coding-time admission still follows its displayed first-pass/expiry conditions. Review the recipient status before assigning another trial.

Trials are separate from paid deposits and are limited to the eligible starter inventory. They do not authorize duplicate reseller accounts or unearned wallet grants. Contact support when a legitimate invitation/verification fails.

Toolbox, project services and extra account tools

Use only the tools and resources your account actually offers.

1. Open the Toolbox or corresponding dashboard section if it is available on your site.
2. Read the tool description, required permissions and any price/slot/usage condition before creating a resource.
3. Choose the intended project/account and complete its setup form carefully.
4. Store connection details privately and test access from the app/project that will use them.
5. Keep backups and review active resources. Do not delete a project/service as a troubleshooting shortcut if it contains work you need.

These tools can depend on site, product or current capacity. The API reference lists available project/thread/file operations where exposed; it does not grant access to a different customer’s project or database.

Get help from Meryl S.

Explain the issue and keep the conversation in one place.

1. Open Support & diagnostics and choose the available Meryl S. chat helper.
2. Describe your goal, app, operating system, selected model and exact error. Include a request ID if you have one.
3. Follow the setup or diagnostic steps you understand. The helper does not need your password, OTP, full card number or wallet seed phrase.
4. For an account/payment issue, provide the order reference and time through the secure support flow. A payment must be verified before credit can be assigned.
5. End the chat when finished. A support conversation can be saved as a ticket; an inactive conversation may be archived after ten minutes in Waiting on Customer. Reply to the same thread when you need more help.

A saved ticket is a record, not a promise that an issue was fixed or that a payment was approved. Use the ticket number to continue rather than starting the same issue repeatedly.

Create a ticket and continue by email

You can ask for help even when sign-in fails.

1. Open your dashboard’s Support section for account ticket history, or the public MagnetAPI support form without an account.
2. Enter your name, a working email, an optional mobile number, a short subject and full issue/error details. Include the affected site and app.
3. Type the four security digits. They refresh every ten minutes; use Refresh numbers if the image expires.
4. Submit once and save your unique #1234567-style ticket number. The public form displays it immediately; email confirmation is queued.
5. Check Inbox and Spam/Junk. Keep the ticket subject/reply key and reply to the confirmation or staff email to continue the same conversation.
6. For dashboard-created account tickets, return to the same site’s ticket history to read/reply. A public visitor ticket does not create an account or reveal an existing account’s history.

Customer replies use hello@magnetapi.org. If you change the email subject completely or reply from a different address, staff may need to review the message before attaching it safely. Do not resend a payment or open duplicate tickets while waiting.

Fix common connection and account problems

Try the smallest safe check first.

For a support report, use: site → app/version → operating system → selected model → action → exact error → request/order ID → approximate time/time zone. Redact credentials and private project contents.

A short glossary

Understand the words you see in the app.