diff --git a/accounts-billing/billing.mdx b/accounts-billing/billing.mdx
new file mode 100644
index 00000000..fe3a22de
--- /dev/null
+++ b/accounts-billing/billing.mdx
@@ -0,0 +1,124 @@
+---
+title: "Billing overview"
+sidebarTitle: "Billing overview"
+description: "Understand how Runpod billing works, manage your credits, and configure payment methods."
+---
+
+Runpod uses a credit-based billing system where you add funds to your account and charges are deducted as you use resources. All compute and storage charges are billed per second, with no fees for data transfer.
+
+## Credits and balance
+
+Your Runpod account balance represents prepaid credits that are consumed as you use resources. Credits are deducted in real-time based on your active Pods, Serverless endpoints, and storage.
+
+To add credits to your account:
+
+1. Navigate to the [Billing page](https://www.console.runpod.io/user/billing) in the Runpod console.
+2. Select a dollar amount for credits to add (or click **Other** to enter a custom amount).
+3. Complete the payment using your preferred payment method.
+
+You can view your current balance and recent transactions on the Billing page at any time.
+
+### Low balance behavior
+
+Runpod monitors your account balance and takes protective action when funds run low:
+
+- When your balance is projected to cover less than 10 seconds of remaining runtime, Runpod automatically stops all your Pods.
+- Stopped Pods retain their volume storage, but you continue to accrue storage charges.
+- If your balance is completely depleted, Pods and their associated storage may be deleted.
+
+
+Set up [automatic payments](#auto-pay) to avoid service interruptions.
+
+
+### Auto-pay
+
+Auto-pay automatically reloads your account balance when it falls below a threshold, helping you avoid service interruptions from low funds.
+
+To configure auto-pay:
+
+1. Navigate to the [Billing page](https://www.console.runpod.io/user/billing) in the Runpod console.
+2. Add a credit card to your account if you haven't already.
+3. Enable auto-pay and configure your settings:
+ - **Threshold**: The balance at which auto-pay triggers.
+ - **Amount**: The dollar amount to add when triggered.
+
+When your balance drops near your configured threshold, Runpod charges your default saved card for the auto-pay amount. To prevent excessive charges, auto-pay attempts are limited to once per hour.
+
+### Minimum balance requirements
+
+To deploy a new Pod, your account must have at least one hour's worth of credits for your selected configuration. If your balance is insufficient, you can deposit additional funds, select a lower-cost GPU, or use a Spot instance.
+
+## Payment methods
+
+Runpod accepts several payment methods:
+
+| Method | Details |
+|--------|---------|
+| Credit card | Visa, Mastercard, American Express, and other cards [supported by Stripe](https://stripe.com/docs/payments/cards/supported-card-brands). Prepaid cards should deposit at least \$100 per transaction. |
+| Cryptocurrency | Accepted via integrated payment processors. Complete any required KYC verification before your first crypto payment. |
+| Business invoicing | Available for transactions over \$5,000. Supports ACH, wire transfer, and credit card. [Contact our sales team](https://ecykq.share.hsforms.com/2MZdZATC3Rb62Dgci7knjbA) to set up invoicing. |
+
+If your card is declined, see [Manage payment card declines](/accounts-billing/manage-payment-cards) for troubleshooting steps.
+
+## Spending limits
+
+Runpod accounts have a default spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges due to misconfigured workloads or runaway processes.
+
+Spending limits increase automatically over time based on your account history. If you need a higher limit immediately, [contact support](https://www.runpod.io/contact) with details about your use case.
+
+## Pricing by product
+
+Each Runpod product has its own pricing structure. See the detailed pricing pages for rates and billing specifics:
+
+
+
+ On-demand, savings plans, and spot instance pricing for GPU Pods.
+
+
+ Pay-per-second pricing for flex and active workers.
+
+
+
+### Storage pricing summary
+
+Storage is billed based on type and usage:
+
+| Storage type | Rate | Billing frequency |
+|-------------|------|-------------------|
+| Container disk (running Pods) | \$0.10/GB/month | Per second |
+| Volume disk (running Pods) | \$0.10/GB/month | Per second |
+| Volume disk (stopped Pods) | \$0.20/GB/month | Per second |
+| Network volumes (under 1TB) | \$0.07/GB/month | Hourly |
+| Network volumes (over 1TB) | \$0.05/GB/month | Hourly |
+
+You are not charged for storage when the host machine is unavailable.
+
+
+Runpod is not designed for long-term data storage. Storage supports active compute workloads. If your account runs out of funds, storage may be deleted and cannot be recovered. Back up critical data regularly to external storage.
+
+
+## View spending history
+
+To review your spending and payment history:
+
+1. Navigate to the [Billing page](https://www.console.runpod.io/user/billing).
+2. Review recent spending in the **Billing Explorer** section.
+
+For detailed cost attribution by team or project, see [Cost centers](/accounts-billing/cost-centers).
+
+## Refunds and credits
+
+Runpod credits are non-refundable and cannot be withdrawn once deposited. Credits can only be used for Runpod services.
+
+If you're new to Runpod and want to evaluate the platform, you can start with as little as \$10. Visit the [Discord community](https://discord.gg/pJ3P2DbUUq) to ask questions before committing to a larger deposit.
+
+## Billing support
+
+If you have questions about billing or believe you've been charged incorrectly, [contact support](https://www.runpod.io/contact) with the following information:
+
+- Your account email address.
+- The resource type (Pod, Serverless endpoint, or storage).
+- The resource ID or name.
+- The date and approximate time of the charge in question.
+
+For general questions about planning your Runpod expenses, email [help@runpod.io](mailto:help@runpod.io).
diff --git a/accounts-billing/cost-centers.mdx b/accounts-billing/cost-centers.mdx
new file mode 100644
index 00000000..aa0c5930
--- /dev/null
+++ b/accounts-billing/cost-centers.mdx
@@ -0,0 +1,125 @@
+---
+title: "Cost centers"
+description: "Track and organize Runpod spending by team, project, or department."
+tag: "NEW"
+---
+
+Cost centers let you attach billing labels to your Runpod resources to track and manage spending across your organization. By grouping your compute resources into cost centers, you can attribute charges to specific teams, projects, or departments.
+
+## Why use cost centers
+
+Cost centers help answer common questions about cloud GPU spending:
+
+- How much did each team spend on Runpod this month?
+- What is the total project cost for a specific customer or initiative?
+- Which cost centers are driving increases in GPU and storage spend?
+- Can we reconcile Runpod spend with our internal budgets and GL cost centers?
+
+By organizing resources into cost centers, you can:
+
+- **Attribute spending accurately.** Understand which teams, projects, or resources are driving costs.
+- **Reduce uncategorized spend.** Resources without cost centers are easy to identify and assign, reducing unknown charges at month-end.
+- **Support budgeting and variance analysis.** Per-cost-center totals make it easier to compare actual Runpod spend against planned budgets.
+
+## Supported resources
+
+Cost centers track billable resources across the Runpod platform:
+
+| Resource type | How costs are tracked |
+|--------------|----------------------|
+| Pods | GPU compute and storage costs are combined into a single Pod charge. |
+| Serverless endpoints | All endpoint usage is tracked under the assigned cost center. |
+| Network volumes | Storage costs for volumes are tracked separately from compute resources. |
+| Instant Clusters | Cluster compute costs are tracked under the assigned cost center. |
+
+Each resource can belong to only one cost center at a time. Resources without an assigned cost center appear as uncategorized.
+
+## Create a cost center
+
+To create a new cost center:
+
+1. Navigate to the [Cost center page](https://www.console.runpod.io/user/cost-center/tags) in the Runpod console.
+2. Select **Add a new cost center**.
+3. Enter a name for the cost center.
+4. Select **Create cost center** to confirm.
+
+Choose names that align with your organization's structure, such as team names, project codes, or department identifiers. Consistent naming makes it easier to map Runpod spend to your internal cost tracking systems.
+
+
+You can edit the name of a cost center at any time after creation.
+
+
+## Add resources to a cost center
+
+Resources are added to cost centers from the Cost center page. You can assign multiple resources at once using bulk selection.
+
+To add uncategorized resources to a cost center:
+
+1. Navigate to the [Cost center page](https://www.console.runpod.io/user/cost-center/tags).
+2. Scroll to the **Uncategorized resources** section.
+3. Use the tabs to filter by resource type (Pods, Serverless Endpoints, Storage Volumes, or Instant Clusters) if needed.
+4. Select the checkbox next to each resource you want to assign.
+5. Select **Add resources to cost center** and choose the target cost center from the dropdown.
+
+The selected resources will move from the uncategorized list to the chosen cost center.
+
+## Uncategorized resources
+
+Any resource without an assigned cost center appears in the **Uncategorized resources** section at the bottom of the **Cost center** page. Uncategorized resources still generate charges, but those charges won't be attributed to any specific cost center on your invoices.
+
+To maintain accurate cost attribution:
+
+- Review the uncategorized resources list regularly, especially before month-end close.
+- Assign new resources to cost centers promptly after creation.
+- Use the resource type tabs to quickly find and categorize specific resource types.
+
+## Edit a cost center
+
+To rename a cost center:
+
+1. Navigate to the [Cost center page](https://www.console.runpod.io/user/cost-center/tags).
+2. Locate the cost center you want to edit.
+3. Select the edit icon next to the cost center name.
+4. Enter the new name and confirm the change.
+
+Renaming a cost center updates its name across the console and on future invoices. Historical invoices retain the original name.
+
+## Delete a cost center
+
+To delete a cost center:
+
+1. Navigate to the [Cost center page](https://www.console.runpod.io/user/cost-center/tags).
+2. Locate the cost center you want to delete.
+3. Select the delete icon next to the cost center name.
+4. Confirm the deletion.
+
+
+Deleting a cost center moves all its assigned resources to the uncategorized list. Consider reassigning resources to another cost center before deletion if you want to maintain cost attribution.
+
+
+## View cost center spend on invoices
+
+Your Runpod invoices include a breakdown of total spend by cost center. Invoices are generated monthly and show how charges are distributed across your organization's cost centers for that period.
+
+To view invoices with cost center data:
+
+1. Navigate to the [Cost center page](https://www.console.runpod.io/user/cost-center/tags).
+2. Select the **Invoices** tab.
+
+Each invoice shows the total amount spent per cost center during that month, making it easy to allocate charges to the appropriate teams or budgets in your financial systems.
+
+
+Invoices reflect the cost center assigned to each resource at the end of the billing month. If you change a resource's cost center after the month ends, the change applies to future invoices only—previous invoices are not updated.
+
+
+## Best practices
+
+Establishing good habits around cost centers helps maintain accurate spend attribution over time.
+
+**Categorize resources early.** Assign resources to cost centers as soon as they're created. This prevents charges from accumulating in the uncategorized bucket and reduces month-end cleanup work.
+
+**Use consistent naming conventions.** Align cost center names with your organization's existing naming schemes for teams, projects, or departments. This simplifies reconciliation with internal financial systems.
+
+**Review uncategorized resources regularly.** Check the uncategorized resources list weekly or before each billing cycle to catch any resources that were created without cost center assignments.
+
+**Plan for organizational changes.** When teams or projects are reorganized, update cost center assignments promptly. Consider creating the new cost center before migrating resources to ensure continuous attribution.
diff --git a/accounts-billing/manage-accounts.mdx b/accounts-billing/manage-accounts.mdx
new file mode 100644
index 00000000..6e89f0b0
--- /dev/null
+++ b/accounts-billing/manage-accounts.mdx
@@ -0,0 +1,129 @@
+---
+title: "Manage accounts"
+description: "Create accounts, manage teams, and configure user permissions in Runpod."
+---
+
+To access Runpod resources, you need to either create your own account or join an existing team through an invitation. This guide explains how to set up and manage accounts, teams, and user roles.
+
+## Create an account
+
+Sign up for a Runpod account at [console.runpod.io/signup](https://www.console.runpod.io/signup).
+
+Once created, you can use your account to deploy Pods, create Serverless endpoints, and access other Runpod services. Personal accounts can be converted to team accounts at any time to enable collaboration features.
+
+## Convert to a team account
+
+Team accounts enable multiple users to collaborate on projects and share resources.
+
+To convert your personal account into a team account:
+
+1. Navigate to the [Team page](https://www.console.runpod.io/team) in the Runpod console.
+2. Select **Convert to a Team Account**.
+3. Enter a team name and confirm the conversion.
+
+
+
+You can revert your account back to a personal account at any time. To revert, scroll to the bottom of the [Team page](https://www.console.runpod.io/team) and select **Delete Team**.
+
+
+
+## Invite team members
+
+Team accounts can invite new members to collaborate. Each invitation includes a specific role that determines the member's permissions.
+
+
+
+To invite a new member:
+
+1. Navigate to the [Team page](https://www.console.runpod.io/team) in the Runpod console.
+2. In the **Members** section, select **Invite New Member**.
+3. Choose [the appropriate role](#roles-and-permissions) for the new member.
+4. Enter the email address of the person you want to invite and click **Create Invite**.
+5. Copy the generated invitation link from the **Pending Invites** section and share it with the person you want to invite.
+
+Invitation links remain active until used or manually revoked. You can view all pending invitations in the team management interface.
+
+## Join a team
+
+When invited to join a team, you'll receive an invitation link from a team member. To accept:
+
+1. Click the invitation link provided by the team member.
+2. Select **Join Team** to accept the invitation.
+
+Your account will gain access to the team's resources based on the role assigned to you.
+
+## Roles and permissions
+
+Runpod provides four distinct roles to control access within team accounts. Each role includes specific permissions designed for different responsibilities.
+
+| Permission | Basic | Billing | Dev | Admin |
+|------------|-------|---------|-----|-------|
+| Access team account | ✅ | ✅ | ✅ | ✅ |
+| Connect to existing Pods | ✅ | ❌ | ✅ | ✅ |
+| Create/delete/start/stop Pods | ❌ | ❌ | ✅ | ✅ |
+| Create/delete Serverless endpoints | ❌ | ❌ | ✅ | ✅ |
+| Send requests to Serverless endpoints | ✅ | ❌ | ✅ | ✅ |
+| Connect to existing Instant Clusters | ✅ | ❌ | ✅ | ✅ |
+| Create/delete/start/stop Instant Clusters | ❌ | ❌ | ❌ | ✅ |
+| Create/update/delete network volumes | ❌ | ❌ | ✅ | ✅ |
+| View billing information | ❌ | ✅ | ❌ | ✅ |
+| Manage payment methods | ❌ | ✅ | ❌ | ✅ |
+| Invite team members | ❌ | ❌ | ❌ | ✅ |
+| Manage team permissions | ❌ | ❌ | ❌ | ✅ |
+| Modify team account settings | ❌ | ❌ | ❌ | ✅ |
+| Access audit logs | ❌ | ❌ | ❌ | ✅ |
+
+### Basic role
+
+The basic role provides essential access for users who need to work with existing resources without management capabilities.
+
+This role allows users to access the team account and connect to already-deployed computing resources (e.g., Pods and Serverless endpoints) for development work. Users with this role cannot view billing information, start or stop Pods, or create new resources.
+
+### Billing role
+
+The billing role focuses exclusively on financial management aspects of the account.
+
+Users with this role can access all billing information, manage payment methods, and view invoices. They cannot access computing resources, making this role ideal for finance team members who need billing access without operational permissions.
+
+### Dev role
+
+The dev role extends basic permissions with additional capabilities for active development work.
+
+This role includes all basic permissions plus the ability to start, stop, and create Pods. Developers can fully manage computing resources for their work while remaining restricted from billing information and account settings.
+
+### Admin role
+
+The admin role provides complete control over all account features and settings.
+
+Administrators have unrestricted access to manage team members, configure account settings, handle billing, and control all team computing resources. This role should be reserved for team leaders and trusted members who need full account access.
+
+## Account spend limits
+
+By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it.
+
+## Monitor account activity
+
+Runpod provides comprehensive audit logs to track all actions performed within your account. This feature helps maintain security and accountability across team operations.
+
+Access audit logs at [console.runpod.io/user/audit-logs](https://www.console.runpod.io/user/audit-logs).
+
+The audit system records detailed information about each action, including the user who performed it, the affected resource, and the timestamp. You can filter logs by date range, user, resource type, resource ID, and specific actions to investigate account activity or troubleshoot issues.
+
+Regular review of audit logs helps identify unusual activity and ensures team members use resources appropriately.
+
+## Best practices
+
+When managing team accounts, establish clear role assignments based on each member's responsibilities. Regularly review team membership and remove access for members who no longer need it.
+
+For enhanced security, use the principle of least privilege by assigning the minimum role necessary for each team member's work. Consider creating separate accounts for billing management to isolate financial access from technical operations.
+
+Monitor audit logs periodically to ensure compliance with your organization's policies and identify any unauthorized activities early.
+
+## Next steps
+
+After setting up your account and team you can:
+
+* [Create API keys](/get-started/api-keys) to enable programmatic access to Runpod services.
+* [Deploy your first Pod](/get-started) to start using GPU resources.
+* Configure [Serverless endpoints](/serverless/overview) for scalable AI inference.
+* Set up [billing and payment methods](https://console.runpod.io/user/billing) for your team.
\ No newline at end of file
diff --git a/accounts-billing/manage-payment-cards.mdx b/accounts-billing/manage-payment-cards.mdx
new file mode 100644
index 00000000..7cd4ac89
--- /dev/null
+++ b/accounts-billing/manage-payment-cards.mdx
@@ -0,0 +1,65 @@
+---
+title: "Troubleshoot payment card declines"
+sidebarTitle: "Payment card declines"
+description: "Resolve declined payment cards and prevent service interruptions on Runpod."
+---
+
+Payment card declines can occur when adding funds to your Runpod account. This guide explains common causes and how to resolve them.
+
+## Common causes of card declines
+
+Card payments may be declined for several reasons:
+
+| Cause | Description |
+|-------|-------------|
+| Fraud protection | Your bank flagged the transaction as potentially fraudulent, especially for international or first-time purchases. |
+| Insufficient funds | The card doesn't have enough available credit or balance. |
+| Card restrictions | Some cards block online purchases, international transactions, or specific merchant categories. |
+| Expired card | The card's expiration date has passed. |
+| Incorrect details | The card number, expiration date, CVV, or billing address doesn't match the issuer's records. |
+| Prepaid card limits | Prepaid cards may have transaction minimums. Stripe recommends deposits of at least \$100 for prepaid cards. |
+
+## Troubleshoot a declined card
+
+Follow these steps to resolve a card decline:
+
+### Step 1: Check your card details
+
+Verify that the card number, expiration date, CVV, and billing address are entered correctly. Even small discrepancies can cause declines.
+
+### Step 2: Contact your bank
+
+Your bank can tell you why the transaction was declined and resolve any blocks on your card. Payment processors don't share specific decline reasons due to privacy regulations, so your bank is the best source of information.
+
+Common bank-side issues include:
+
+- Fraud alerts that require you to confirm the transaction is legitimate.
+- Daily spending limits that have been reached.
+- Blocks on international transactions (Runpod processes payments through Stripe).
+
+
+Contact your bank before trying multiple cards. If the payment processor detects several failed attempts from your account in a short period, it may temporarily block all payment attempts. These blocks typically clear after 24 hours.
+
+
+### Step 3: Try an alternative payment method
+
+If your card continues to decline, consider these alternatives:
+
+- **Different card**: Use another credit or debit card from a different issuer.
+- **Cryptocurrency**: Runpod accepts crypto payments through integrated processors.
+- **Business invoicing**: For deposits over \$5,000, [contact sales](https://ecykq.share.hsforms.com/2MZdZATC3Rb62Dgci7knjbA) to arrange invoicing via ACH or wire transfer.
+
+For supported card brands, see [Stripe's documentation](https://stripe.com/docs/payments/cards/supported-card-brands).
+
+### Step 4: Contact Runpod support
+
+If you've verified your card details and spoken with your bank but still can't complete a payment, [contact Runpod support](https://www.runpod.io/contact) for assistance.
+
+## Prevent service interruptions
+
+To avoid disruptions from unexpected card declines:
+
+- **Enable auto-pay.** Configure [automatic payments](/accounts-billing/billing#auto-pay) to reload your balance before it runs low. If a charge fails, you'll have time to resolve the issue before your resources are affected.
+- **Add a backup card.** Keep a secondary payment method on file in case your primary card is declined.
+- **Monitor your balance.** Check your Runpod balance regularly on the [Billing page](https://www.console.runpod.io/user/billing) and add funds before they run critically low.
+- **Notify your bank.** If you plan to make a large deposit, contact your bank in advance to prevent fraud blocks.
diff --git a/accounts-billing/referrals.mdx b/accounts-billing/referrals.mdx
new file mode 100644
index 00000000..513dfcaa
--- /dev/null
+++ b/accounts-billing/referrals.mdx
@@ -0,0 +1,78 @@
+---
+title: "Referral, affiliate, and creator programs"
+sidebarTitle: "Referral programs"
+description: "Earn additional revenue through Runpod's referral, affiliate, and creator programs"
+---
+
+Runpod offers three programs that help you earn additional revenue while helping us grow our community. Whether you're referring new users, creating popular templates, or driving significant traffic, there's a program that fits your contribution style.
+
+## Runpod referral program
+
+Earn Runpod Credits when users you refer spend on Serverless or Pods. The referral program rewards both you and the person you refer, creating a win-win situation for everyone involved.
+
+### How rewards work
+
+When someone signs up using your referral link and starts spending on Runpod, you earn a percentage of their spend as Runpod Credits:
+
+- **5% commission** on all Serverless spend for the first 6 months.
+- **3% commission** on all Pod spend for the first 6 months.
+- **Bonus credits** for both you and your referral after they load \$10 on their account. The bonus amount depends on your location:
+ - **Non-European customers** receive a random weighted bonus between \$5 and \$500.
+ - **European customers** receive a fixed \$5 bonus.
+ - **Cross-region referrals**: If a European customer refers a non-European customer, the European customer receives \$5 and the non-European customer receives the random weighted bonus (\$5-\$500). If a non-European customer refers a European customer, the non-European customer receives the random weighted bonus and the European customer receives \$5.
+
+If you referred users before June 16, 2025, you're part of our beta program group. This means you'll continue earning commissions on their spend indefinitely, not just for 6 months.
+
+## Runpod affiliate program
+
+The affiliate program is designed for high-performing referrers who want to earn cash instead of credits. Through our partnership with Partnerstack, eligible referrers can earn 10% cash commissions on all referral spend.
+
+### Eligibility and rewards
+
+To qualify for the affiliate program, you need to have referred at least 25 paying users through the standard referral program. Once eligible, you can choose to upgrade to the affiliate program, which offers:
+
+- **10% cash commission** on all referral spend for the first 6 months.
+- Professional tracking and reporting through Partnerstack.
+- Direct cash payments instead of Runpod Credits.
+
+Once you opt into the affiliate program, this decision is permanent. Choose carefully based on whether you prefer cash payments or Runpod Credits.
+
+For beta program participants (users referred before June 26, 2025), a special arrangement applies. These users will be eligible for Partnerstack commissions during their first 6 months. After that period, they'll return to the standard referral program but continue generating commissions indefinitely.
+
+## Runpod creator program
+
+The creator program rewards users who build popular [Pod templates](/pods/templates/overview) that others use on the platform. Every time someone runs a Pod using your template, you earn a percentage of their spend.
+
+### How it works
+
+Template creators earn **1% in Runpod Credits** for every dollar spent using their templates. This creates a passive income stream that grows with your template's popularity.
+
+For example, if 20 users run Pods using your template at \$0.54/hour for a full week, you'll earn \$18.14 in credits. The more useful and popular your template, the more you can earn.
+
+### Getting started with templates
+
+To participate in the creator program, your template must accumulate at least 1 day of total runtime across all users. Focus on creating templates that solve real problems or make it easier for users to get started with specific workloads.
+
+## How to participate
+
+Getting started with any of these programs is straightforward:
+
+1. Navigate to your [referral dashboard](https://www.console.runpod.io/user/referrals) in the Runpod console.
+2. Find your unique referral link (it will look something like `https://runpod.io?ref=5t99c9je`).
+3. Share this link with potential users through your preferred channels.
+
+For the creator program, simply publish templates through your Runpod account and promote them to potential users.
+
+## Important details
+
+Understanding how these programs work will help you maximize your earnings:
+
+1. **Referral commissions are based on actual usage, not purchases.** If someone you refer buys \$1,000 in credits, you won't earn commission until they actually use those credits on Pods or Serverless workloads.
+2. **New accounts only.** Referral links only work for brand new Runpod users. If someone already has an account, referring them won't generate commissions.
+3. **Bonus credit distribution varies by location.** Non-European customers receive credits through a weighted random system between \$5 and \$500, while European customers receive a fixed \$5 bonus. For non-European customers, most will receive a bonus of \$5, with about 96% receiving \$10 or less.
+
+## Support
+
+Have questions about maximizing your earnings or need help with any of these programs? [Contact our support team](https://contact.runpod.io/hc/en-us/requests/new) for assistance.
+
+Remember, if you're transitioning to the affiliate program, you'll keep all earnings accumulated through the referral program before making the switch.
\ No newline at end of file
diff --git a/docs.json b/docs.json
index b15a9105..6f44ae71 100644
--- a/docs.json
+++ b/docs.json
@@ -39,8 +39,8 @@
"overview",
"get-started",
"get-started/concepts",
- "get-started/manage-accounts",
- "get-started/api-keys" ]
+ "get-started/api-keys"
+ ]
},
{
"group": "Serverless",
@@ -151,7 +151,8 @@
"pods/templates/environment-variables",
"pods/templates/secrets"
]
- }
+ },
+ "fine-tune"
]
},
{
@@ -183,6 +184,16 @@
}
]
},
+ {
+ "group": "Accounts and billing",
+ "pages": [
+ "accounts-billing/manage-accounts",
+ "accounts-billing/billing",
+ "accounts-billing/cost-centers",
+ "accounts-billing/referrals",
+ "accounts-billing/manage-payment-cards"
+ ]
+ },
{
"group": "Integrations",
"pages": [
@@ -205,17 +216,11 @@
"hub/revenue-sharing"
]
},
- {
- "group": "Fine-tuning",
- "pages": ["fine-tune"]
- },
{
"group": "Reference",
"pages": [
"references/gpu-types",
"references/cpu-types",
- "references/billing-information",
- "references/referrals",
"references/security-and-compliance",
{
"group": "Troubleshooting",
@@ -227,8 +232,7 @@
"references/troubleshooting/token-authentication-enabled",
"references/troubleshooting/leaked-api-keys",
"references/troubleshooting/storage-full",
- "references/troubleshooting/troubleshooting-502-errors",
- "references/troubleshooting/manage-payment-cards"
+ "references/troubleshooting/troubleshooting-502-errors"
]
},
{
@@ -631,11 +635,11 @@
},
{
"source": "/get-started/billing-information",
- "destination": "/references/billing-information"
+ "destination": "/accounts-billing/billing"
},
{
"source": "/get-started/referrals",
- "destination": "/references/referrals"
+ "destination": "/accounts-billing/referrals"
},
{
"source": "/tutorials/overview",
@@ -711,7 +715,7 @@
},
{
"source": "/references/faq/manage-cards",
- "destination": "/references/troubleshooting/manage-payment-cards"
+ "destination": "/accounts-billing/manage-payment-cards"
},
{
"source": "/runpodctl/reference/create",
@@ -740,6 +744,22 @@
{
"source": "/runpodctl/reference/runpodctl",
"destination": "/runpodctl/overview"
+ },
+ {
+ "source": "/get-started/manage-accounts",
+ "destination": "/accounts-billing/manage-accounts"
+ },
+ {
+ "source": "/references/billing-information",
+ "destination": "/accounts-billing/billing"
+ },
+ {
+ "source": "/references/referrals",
+ "destination": "/accounts-billing/referrals"
+ },
+ {
+ "source": "/references/troubleshooting/manage-payment-cards",
+ "destination": "/accounts-billing/manage-payment-cards"
}
]
}