Billing & Payments

Your money goes into a General Balance for infrastructure or an AI Balance for LLM credits. Three payment methods add funds: credit card for instant top-ups, cryptocurrency for top-ups that need no payment-provider account, and bank transfer for large deposits. Every transaction is logged, every payment generates an invoice, and both are readable over HTTP.

---

Check your balances

You can read both balances in one call or query either one on its own:

CLI

# See both balances at once
hoody wallet balances get

# General balance only
hoody wallet balance get

# AI balance only
hoody wallet credits get

SDK

import { HoodyClient } from 'hoody-sdk';
const client = new HoodyClient({ baseURL: 'https://api.hoody.com', token: process.env.HOODY_TOKEN });

// All balances: general + AI
const balances = await client.api.wallet.getBalances();
console.log(balances.data);
// { general_balance: "125.50", ai_limit: "50.00", ai_usage: "23.45", ai_remaining: "26.55", ai_usage_status: "live" }
// If ai_usage_status is "unavailable", treat ai_remaining as unknown.

// General balance only
const general = await client.api.wallet.getBalance();

// AI balance only
const ai = await client.api.wallet.getCredits();

HTTP

# Aggregate balances
curl -X GET "https://api.hoody.com/api/v1/wallet/balances" \
  -H "Authorization: Bearer $TOKEN"

# General balance
curl -X GET "https://api.hoody.com/api/v1/wallet/balances/general" \
  -H "Authorization: Bearer $TOKEN"

# AI balance
curl -X GET "https://api.hoody.com/api/v1/wallet/balances/ai" \
  -H "Authorization: Bearer $TOKEN"

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

Each link reads one of the three balance views without a CLI or SDK install.

Copy

# Both balances
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/balances&method=GET&bearer_token=TOKEN&response=transparent

# General only
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/balances/general&method=GET&bearer_token=TOKEN&response=transparent

# AI only
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/balances/ai&method=GET&bearer_token=TOKEN&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

---

Three payment methods

Credit Cards

Providers: Visa, MasterCard, American Express Processor: Stripe (PCI-compliant) Fees: None Speed: Instant

Save a card once and pay from it whenever you want. Hoody never sees your card number; Stripe stores and processes it.

Cryptocurrencies

Supported: BTC, ETH, USDT, USDC, LTC, 100+ more Processor: NOWPayments Fees: +5% processing Speed: 5-60 minutes (blockchain confirmation)

You do not need a NOWPayments account or an identity check, but you do need an authenticated Hoody account: creating and checking a crypto invoice are bearer-authenticated wallet calls.

Bank Transfer

Minimum: $500+ Fees: None from Hoody (your bank may charge) Speed: 1-3 business days

Contact support for account details. Best for large deposits and enterprise accounts.

---

Add a payment method

Save a credit card for repeat payments:

CLI

# card.json holds the Stripe.js one-time token: {"token": "tok_1LgR....Dc2"}
hoody wallet payments methods create --type credit_card --name "Personal Visa" \
  --details @card.json --is-default

SDK

const paymentMethod = await client.api.wallet.createPaymentMethod({
  type: 'credit_card',
  name: 'Personal Visa',
  details: { token: 'tok_1LgR....Dc2' },  // Stripe.js one-time token
  is_default: true,
});
console.log(paymentMethod.data.id); // "507f1f77bcf86cd799439131"

HTTP

curl -X POST "https://api.hoody.com/api/v1/wallet/payment-methods/" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Personal Visa",
    "type": "credit_card",
    "details": { "token": "tok_1LgR....Dc2" },
    "is_default": true
  }'

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

Saves a card from a one-time Stripe token. Generate that token with Stripe.js in your own frontend first — this link cannot create one.

Copy

https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/payment-methods/&method=POST&bearer_token=TOKEN&json={"name":"Personal%20Visa","type":"credit_card","details":{"token":"tok_1LgR....Dc2"},"is_default":true}&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

Note

The token is a one-time Stripe token generated by frontend JavaScript. Hoody never handles raw card details. All card data is stored by Stripe (PCI DSS Level 1).

Manage saved cards

CLI

# List all payment methods
hoody wallet payments methods list

# Set a card as default
hoody wallet payments methods default set $PAYMENT_METHOD_ID

# Delete a card
hoody wallet payments methods delete $PAYMENT_METHOD_ID

SDK

// List all
const methods = await client.api.wallet.listPaymentMethods();

// Set default
await client.api.wallet.setDefaultPaymentMethod(PAYMENT_METHOD_ID);

// Delete
await client.api.wallet.deletePaymentMethod(PAYMENT_METHOD_ID);

HTTP

# List all
curl -X GET "https://api.hoody.com/api/v1/wallet/payment-methods/" \
  -H "Authorization: Bearer $TOKEN"

# Set default
curl -X PUT "https://api.hoody.com/api/v1/wallet/payment-methods/$PAYMENT_METHOD_ID/default" \
  -H "Authorization: Bearer $TOKEN"

# Delete
curl -X DELETE "https://api.hoody.com/api/v1/wallet/payment-methods/$PAYMENT_METHOD_ID" \
  -H "Authorization: Bearer $TOKEN"

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

List saved cards, set one as default, or delete one.

Copy

# List
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/payment-methods/&method=GET&bearer_token=TOKEN&response=transparent

# Set default
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/payment-methods/PAYMENT_METHOD_ID/default&method=PUT&bearer_token=TOKEN&response=transparent

# Delete
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/payment-methods/PAYMENT_METHOD_ID&method=DELETE&bearer_token=TOKEN&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

---

Make a payment

Add funds to your General Balance with a card via Stripe Checkout:

CLI

# Card top-ups complete on Stripe's hosted checkout page, so they run
# through the SDK/HTTP API or the dashboard rather than a direct CLI charge.
# From the CLI, check your balance and transactions:
hoody wallet balance get
hoody wallet transactions list

Caution

Direct card charging is not available from the CLI, the SDK or the API. Add funds through the Stripe Checkout flow below (hoody wallet payments stripe checkout create), or the dashboard, to add funds.

SDK

// Card top-up via Stripe Checkout. Redirect the user to the returned
// checkout URL; the wallet is credited after Stripe confirms settlement
// (webhook), not instantly.
const checkout = await client.api.wallet.createStripeCheckout({
  amount: '100.00',
  idempotency_key: 'topup-2026-06-10-001',
});
// checkout.data.checkout_url: hosted Stripe Checkout URL to open
// checkout.data.intent.id: payment intent id (poll with getStripePaymentIntent)

HTTP

curl -X POST "https://api.hoody.com/api/v1/wallet/payments/stripe/checkout" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "100.00",
    "idempotency_key": "topup-2026-06-10-001"
  }'

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

Opens a Stripe Checkout session; follow the returned redirect URL to complete the charge. The wallet is credited after Stripe confirms settlement, not instantly.

Copy

https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/payments/stripe/checkout&method=POST&bearer_token=TOKEN&json={"amount":"100.00","idempotency_key":"topup-2026-06-10-001"}&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

Redirect the user to the returned checkout URL. Funds are credited after Stripe confirms settlement, usually within seconds. There are no additional fees, and an invoice is generated automatically.

---

Cryptocurrency payments

Crypto payments work from any country and need no NOWPayments account or identity check; creating and checking the invoice still requires an authenticated Hoody account.

Payment flow

1. Create a hosted invoice

   Call the dashboard or API with the USD amount and, optionally, an idempotency_key. The API returns data.invoice_url.

2. Complete payment on the hosted invoice

   Redirect the user to data.invoice_url, where the cryptocurrency and payment destination are handled.

3. Wait for confirmation

   • Bitcoin: 15-60 minutes (1-6 confirmations)
   • Ethereum: 5-15 minutes (12 confirmations)
   • Litecoin: 10-30 minutes (6 confirmations)
   • Stablecoins (USDT/USDC): 5-15 minutes (varies by chain)

4. Funds added

   Hoody credits your balance, generates an invoice, and sends a confirmation email.

Caution

+5% processing fee on all crypto payments. This covers volatility risk during blockchain confirmation, network fees, and exchange costs. Example: deposit $100 worth of crypto, you pay $105 equivalent, and your General Balance receives $100.

Supported currencies

BTC, ETH, USDT, USDC, LTC, and 100+ more via NOWPayments. Check the payment interface for the complete list.

---

Bank transfer

Bank transfers are for large deposits and enterprise accounts.

1. Contact support

   Email with your desired amount, account ID, and preferred currency (USD, EUR).

2. Receive bank details

   Account number, routing details, SWIFT/BIC code, and a reference number (required for crediting).

3. Send the transfer

   Include the reference number in the transfer notes. Without it, crediting may be delayed.

4. Funds arrive (1-3 business days)

   Hoody credits your balance, generates an invoice, and sends an email confirmation.

Caution

Always include the reference number in your bank transfer. Without it, support has to match the transfer to your account by hand, which delays crediting.

Hoody charges no fee on bank transfers. Your bank may charge wire, SWIFT, or conversion fees.

---

Transaction history

Every payment, charge, transfer, and refund lands in the same transaction list:

CLI

# List recent transactions
hoody wallet transactions list

# Get details for a specific transaction
hoody wallet transactions get $TRANSACTION_ID

SDK

// List transactions
const txns = await client.api.wallet.listTransactions({ limit: 50, sort_by: 'created_at', sort_order: 'desc' });

// Get a specific transaction
const txn = await client.api.wallet.getTransaction(TRANSACTION_ID);

HTTP

# List transactions
curl -X GET "https://api.hoody.com/api/v1/wallet/transactions?limit=50&sort_by=created_at&sort_order=desc" \
  -H "Authorization: Bearer $TOKEN"

# Get specific transaction
curl -X GET "https://api.hoody.com/api/v1/wallet/transactions/$TRANSACTION_ID" \
  -H "Authorization: Bearer $TOKEN"

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

Lists recent transactions or fetches one by ID.

Copy

# List
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/transactions?limit=50%26sort_by=created_at%26sort_order=desc&method=GET&bearer_token=TOKEN&response=transparent

# Get one
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/transactions/TRANSACTION_ID&method=GET&bearer_token=TOKEN&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

Each transaction includes: unique ID, amount, currency, type (payment, credit, debit, refund, adjustment), status (pending, completed, failed, cancelled), timestamp, and related invoice.

---

Invoices

Every payment generates an invoice automatically. Download them for accounting, taxes, or client billing:

CLI

# List all invoices
hoody wallet invoices list

# Download invoice as PDF (-o raw is required: the default output
# JSON-stringifies the binary body and is not a usable PDF)
hoody wallet invoices download $INVOICE_ID -o raw > invoice.pdf

# Generate invoice for a transaction that's missing one
hoody wallet invoices create $TRANSACTION_ID

SDK

// List invoices
const invoices = await client.api.wallet.listInvoices({ limit: 10, sort_by: 'created_at', sort_order: 'desc' });

// Download PDF
const pdf = await client.api.wallet.downloadInvoice(INVOICE_ID);

// Generate missing invoice
await client.api.wallet.createInvoice(TRANSACTION_ID);

HTTP

# List invoices
curl -X GET "https://api.hoody.com/api/v1/wallet/invoices/?limit=10&sort_order=desc" \
  -H "Authorization: Bearer $TOKEN"

# Download PDF
curl -X GET "https://api.hoody.com/api/v1/wallet/invoices/$INVOICE_ID/pdf" \
  -H "Authorization: Bearer $TOKEN" -o invoice.pdf

# Generate missing invoice
curl -X POST "https://api.hoody.com/api/v1/wallet/invoices/generate/$TRANSACTION_ID" \
  -H "Authorization: Bearer $TOKEN"

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

Lists invoices or generates one for a transaction that’s missing it. The PDF download (see the HTTP tab above) is a plain GET too, returning raw PDF bytes instead of JSON — fetch it with the CLI or HTTP tab shown above.

Copy

# List
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/invoices/?limit=10%26sort_order=desc&method=GET&bearer_token=TOKEN&response=transparent

# Generate missing
https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/invoices/generate/TRANSACTION_ID&method=POST&bearer_token=TOKEN&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

---

Payment method comparison

Method	Speed	Fees	Best For
Credit Card	Instant	None	Regular top-ups, automation
Cryptocurrency	5-60 min	+5%	Privacy, international, no-account
Bank Transfer	1-3 days	Bank fees vary	Large deposits ($500+), enterprise

Pick the method by what you need most: speed (card), privacy (crypto), or volume (bank transfer).

---

Troubleshooting

Credit card declined

Your bank may flag hosting purchases as suspicious. Call your bank to whitelist Stripe. Verify the card hasn’t expired and the billing address matches. Check payment status:

CLI

hoody wallet transactions list --limit 10  # no CLI command for payment-intent status; use the SDK/HTTP tab

SDK

// For a card payment, look up its Stripe intent (crypto: getCryptoPaymentIntent)
const status = await client.api.wallet.getStripePaymentIntent(PAYMENT_ID);

HTTP

# Card payment (crypto: /wallet/payments/crypto/intents/$PAYMENT_ID)
curl -X GET "https://api.hoody.com/api/v1/wallet/payments/stripe/intents/$PAYMENT_ID" \
  -H "Authorization: Bearer $TOKEN"

URL

?

One request, one link

cURL runs inside your container and can wrap any HTTP request into a single GET URL. The call stops being something you need a client for and becomes something you can paste into a browser, send in a chat, bookmark, schedule with cron, or drop into a no-code tool.

Nothing is installed on the machine that opens it. The link does carry whatever credentials the call needs, so treat it as you would treat those credentials.

Slashes, colons and braces pass through as they are. The one character you must encode is an & inside a value, which happens when the wrapped URL carries its own query string. Left raw it ends the value early, and the rest is read as cURL's own parameters, so you get a 200 on a request you did not make.

How the wrapping works Chaining calls into one link Turning a link into a shortcut

Looks up a card payment’s Stripe intent status.

Copy

https://PROJECT_ID-CONTAINER_ID-curl-1.SERVER.containers.hoody.com/api/v1/curl/request?url=https://api.hoody.com/api/v1/wallet/payments/stripe/intents/PAYMENT_ID&method=GET&bearer_token=TOKEN&response=transparent

The link carries a credential and executes with it, so it is as sensitive as the credential itself — and it passes through the cURL service's request log on the way, not just the target's. Share it only where you would share the secret, and prefer a delegated token with minimal permissions and an expiry: see API tokens.

Crypto payment not credited

Check the blockchain explorer for your transaction hash. Bitcoin needs 1-6 confirmations, Ethereum needs 12. If confirmed but not credited, contact support with the transaction hash and payment reference.

Bank transfer missing after 3+ days

Verify you included the reference number. Check with your bank that the transfer was processed and not held for review. SWIFT transfers can take up to 5 days. Contact support with your bank confirmation and transfer details.

---

What’s Next

Wallet & Balance Management The dual-balance system and how to transfer between General and AI balances

Wallet & Payments API Full endpoint reference with every parameter and response schema

Rent Servers Browse the marketplace and provision bare metal infrastructure