Skip to content

Create post-paid-billing - #683

Merged
lavanya-gunreddi merged 14 commits into
mainfrom
lg-post-paid-billing-1
Sep 23, 2026
Merged

lavanya-gunreddi merged 14 commits into
mainfrom
lg-post-paid-billing-1

Conversation

@lavanya-gunreddi

Copy link
Copy Markdown
Contributor

new page for post paid billing

@mintlify

mintlify Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
runpod-docs 🟢 Ready View Preview Sep 23, 2026, 5:32 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@lavanya-gunreddi

Copy link
Copy Markdown
Contributor Author

@Promptless Apply rules from promptless.md and runpod style guide to all the files in this branch.

@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

On it — I'll apply the rules from promptless.md and the Runpod style guide across the files changed in this branch, and follow up here with the results.

@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Review done. The branch changes two files — the new post-paid billing page and its nav entry (nav looks correct). I found a handful of style-guide fixes to apply on the new page: separator em dashes, capitalization of "Pods", the meta description length, an unescaped "$0", and a list that should be bulleted. Applying those now.

Apply promptless.md and the Runpod style guide to accounts-billing/post-paid-billing.mdx:
remove em-dash separators, capitalize Pods, escape $0, lengthen the meta description
into the 110-160 char range, and convert the contract-types and prepaid-behaviors lists
to punctuated bullets. Also tightens prose to active voice and adds a billing-overview link.
@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Done — the style-guide fixes have been applied and pushed to this PR branch, so #683 now shows the updated post-paid billing page. Nav was left unchanged since it was already correct.

@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Done — I applied the Runpod style guide and promptless.md rules to the new post-paid-billing page and pushed the changes to this branch, so PR #683 now shows the updated page. The facts were already correct, so this was a style and readability pass: em-dash separators replaced with colons or periods, "Pods" capitalized, $0 escaped for MDX, the meta description expanded into the required 110–160 characters, the contract types and prepaid-behaviors note turned into punctuated bullets, prose tightened to active voice and second person, and a link to the billing overview page added. The docs.json nav entry was already correct and left unchanged.

One thing worth a quick check: the page uses both "account manager" and "account representative" for the enterprise contact — if those are the same role, standardizing on one term reads more clearly; if they're distinct, it's worth making that explicit.

Review: https://app.gopromptless.ai/suggestions/d1974308-3921-4488-b258-d950ad203181

@lavanya-gunreddi

Copy link
Copy Markdown
Contributor Author

@Promptless use account manager

@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Thanks — we're on it. We're researching the post-paid billing details now and drafting the documentation. We'll follow up here with the proposed changes shortly.

@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Got it — we'll standardize on "account manager" throughout the post-paid billing page and update the proposed changes accordingly.

@promptless

promptless Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Done — we standardized the enterprise-contact terminology on the post-paid billing page. The three remaining "account representative" references (in the eligibility note, the contract-types section, and the invoicing section) now say "account manager", so the page consistently tells enterprise customers to contact their Runpod account manager to convert their account, discuss pricing and contract structures, and handle invoicing. The update is pushed to the lg-post-paid-billing-1 branch and is part of this PR.

Review the full suggestion here: https://app.gopromptless.ai/suggestions/d1974308-3921-4488-b258-d950ad203181

@zackmckennarunpod

Copy link
Copy Markdown

"What gets billed" table — missing Public Endpoint. It's a real billed postpaid product (prerated passthrough, util/metronomeProductDefinitions.ts) alongside GPU/CPU Pods, Serverless, Instant Clusters, and Storage. Worth adding a row for it.

@zackmckennarunpod

Copy link
Copy Markdown

"Post-paid billing covers Secure Cloud resources only. Community Cloud usage is excluded from enterprise invoices." — this framing isn't quite right. Postpaid billing itself supports Community Cloud: the rate card rates both secure and community cloud types, and metering capture doesn't filter Community Cloud usage out. The reason no Community Cloud usage shows up on today's invoices is that postpaid accounts are currently organizations, and orgs don't have Community Cloud in the console — that's a console/product surfacing choice, not a billing-side exclusion.

Suggest rephrasing to something like: "Today, post-paid accounts are organizations, which use Secure Cloud. Community Cloud usage does not currently appear on enterprise invoices." That leaves room for Community Cloud to bill under postpaid later without needing a doc correction.

@zackmckennarunpod

Copy link
Copy Markdown
Public Endpoints Priced per request, metered as a passthrough at contracted rates.

one note to be clear -> the passthrough charges exactly what the public endpoints cost and we do not have contracted rates for public endpoints at this time.

Comment thread accounts-billing/post-paid-billing.mdx Outdated

## Contract types

You're billed at contracted rates rather than retail prices. Three contract structures are available:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would remove the contract types since the shape of the contract can vary greatly, and at this time postpaid is contigent on setting up a custom enterprise contract with sales (since we need to basically extend them a line of credit)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Promptless work on this comment

@promptless

promptless Bot commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

Thanks — I've picked up your request on the post-paid billing pull request and I'm reviewing it against the existing documentation now. I'll follow up here with the documentation updates or findings once that's done.

Per reviewer feedback: contract shape varies and post-paid is contingent
on a custom enterprise contract. Fold that framing into the intro.
@promptless

promptless Bot commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

Done — I removed the "Contract types" section from the post-paid billing page, since (as you noted) the contract shape varies a lot and post-paid is set up through a custom enterprise contract. I also reworded the intro so it now says usage is billed "under a custom enterprise contract at your contracted rates," which keeps that context without locking in a fixed set of contract structures. The change is pushed to the lg-post-paid-billing-1 branch and shows on this PR.

Review: https://app.gopromptless.ai/suggestions/d1974308-3921-4488-b258-d950ad203181

@lavanya-gunreddi
lavanya-gunreddi merged commit 6bedc9a into main Sep 23, 2026
4 checks passed
@lavanya-gunreddi
lavanya-gunreddi deleted the lg-post-paid-billing-1 branch September 23, 2026 17:35

This branch was successfully deployed

1 active deployment
staging 0ed5878b Deployed Sep 23, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants