Enterprise: Postpaid Billing, Invoices With Your Company Details, Reconcilable Usage
Prepaid credits are fine for an individual developer. Company procurement gets stuck on three things: can we pay in arrears, can we get an invoice with our legal entity on it, and can we reconcile the usage line by line.
All three are supported.
Postpaid: use first, billed twice a month
Enterprise accounts can switch to postpaid: call first, get billed twice a month. No forecasting usage, no lump sum up front, and no service interruption because the balance ran out at 3am.
The bill page shows both the next billing date and usage accrued in the current period, so you can see where the period is heading instead of finding out when the bill lands.
Invoices carry your company name and address
Once issued, a bill produces a downloadable PDF receipt with your company name and address — the field most often rejected by finance on an expense claim. Set them once in the dashboard and every subsequent receipt carries them.
One thing to know: name and address take effect together. When you change one, update both.
Reconcilable usage detail
Enterprise usage exports per period with timestamp, endpoint and amount. Finance reconciles it against the bill; engineering reconciles it against their own call log. Both sides can self-serve.
The usual sources of discrepancy are failed requests aren't billed and retries. Anything those two don't explain, bring to us.
What happens if a bill goes unpaid
An issued bill that stays unpaid triggers a reminder email first. Continued non-payment suspends API access, restored on payment. It's stated here so you know before integrating, rather than on the day the service stops.
Paying a bill
Balance offset, partial payment, and multi-chain stablecoins (USDT / USDC / PYUSD on TRC20 / ERC20 / Solana) — the same rail as top-ups, described in multi-chain stablecoin top-ups.
Getting set up
Enterprise accounts are enabled manually. Contact us with your company name, expected volume and preferred settlement, and we'll configure the postpaid limit, a dedicated rate limit and your invoice details.
Related
- Pricing — per-endpoint prices and billing rules
- Docs — the endpoint list
- Usage doesn't add up? — reading the detail
Related articles
- Self-Hosted Source Code Is Live: Run the Whole Stack on Your Own Machines Three server-side packages (app, web, Pugongying) with request signing, device registration, automatic captcha solving and a full automation toolkit. How it differs from the hosted API.
- Docs Reorganised: Playground or Swagger UI, and When to Use Which Endpoints regrouped into two data families, Pugongying split into six sub-sections. Playground for your first hour, Swagger UI while coding — it's generated from code and can't drift.
- Multi-Chain Stablecoin Top-Ups: USDT / USDC / PYUSD on TRC20, ERC20 and Solana How to pick a chain, why the decimal tail on the amount due must match exactly, why exchange withdrawal fees break matching, and what happens on the wrong network.
- Pugongying Content Square and Keyword Analytics: Decide What to Say Before Who Says It Content Square for category-level distribution, keyword/daily to bet on rising rather than high, related for long-tail expansion, and why the live pool is a different pool.
About the Rnote Xiaohongshu API
Skip building a RedNote scraper: one API key gets you notes, comments, users, search, products and Pugongying creator data. Pay per call, charged only for successful requests.