agentleFS
hostingerhostinger/hostinger-agent-skills/skills/billing/SKILL.md

billing

Skill28 starsChanged 5 months agoMITView on GitHub

Hostinger Billing API for catalog browsing, payment method management, and subscription control. Use when checking pricing, managing payment methods, viewing subscriptions, or toggling auto-renewal.

  • Sends data out

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use testing.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 3 projects that use this

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. kortix-ai/suna★ 21ksame name
    2. kortix-ai/CompanyOS★ 21ksame name
    3. trycompai/comp★ 2.1ksame name
    4. theopenco/llmgateway★ 1.7ksame name
    5. brightdata/skills★ 270same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always fetch catalog prices before displaying to users — prices are in cents

    line 158
  2. Very specific:

    Use POST /api/domains/v1/portfolio for domain purchases

    line 163
  3. Very specific:

    Use POST /api/vps/v1/virtual-machines for VPS purchases

    line 164
  4. Distinctive:

    Prefer non-credit-card payment methods to avoid verification delays

    line 165
  5. Distinctive:

    If no payment method is specified in an order, the default method is used automatically

    line 169
  6. Distinctive:

    Remove unused payment methods to keep your account clean

    line 170
  7. Distinctive:

    Verify your API token is valid and not expired

    line 179
  8. Very specific:

    Check Authorization: Bearer <token> header format

    line 181
  9. Distinctive:

    Check order status in hPanel

    line 193

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hostinger Billing

The Billing API allows you to browse the Hostinger service catalog, manage payment methods, and control subscriptions programmatically. Orders are placed through resource-specific endpoints (e.g., domains and VPS), not a generic billing order endpoint.

Table of Contents

  • Core Concepts
  • Common Patterns
  • API Reference
  • Best Practices
  • Troubleshooting
  • References

Core Concepts

Catalog

The catalog contains available products and pricing. Prices are displayed in cents (integer), e.g., 1799 means $17.99. Use the catalog to discover available services and their item_id values before placing orders.

Orders

Orders are placed through resource-specific endpoints (e.g., POST /api/domains/v1/portfolio, POST /api/vps/v1/virtual-machines) by referencing catalog item_id values and a payment method. There is no longer a generic billing order endpoint. Orders created via API are set for automatic renewal by default. Some credit_card payments may require additional verification.

Payment Methods

Payment methods must be added via hPanel. The API lets you list, set a default, or delete existing payment methods.

Subscriptions

Subscriptions represent active service plans. You can list subscriptions and toggle auto-renewal on or off.

Common Patterns

Browse Catalog and Place an Order

CLI (curl):

# Get available catalog items
curl -X GET "https://developers.hostinger.com/api/billing/v1/catalog" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json"

# Filter catalog by category
curl -X GET "https://developers.hostinger.com/api/billing/v1/catalog?category=vps" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

Python SDK:

from hostinger_api import Hostinger

client = Hostinger(api_token="YOUR_API_TOKEN")

# List catalog items
catalog = client.billing.catalog.get_catalog_item_list()
for item in catalog:
    print(f"{item.name}: {item.price / 100:.2f} USD")

TypeScript SDK:

import { Hostinger } from "hostinger-api-sdk";

const client = new Hostinger({ apiToken: "YOUR_API_TOKEN" });

const catalog = await client.billing.catalog.list();
for (const item of catalog) {
  console.log(`${item.name}: ${(item.price / 100).toFixed(2)} USD`);
}

PHP SDK:

use Hostinger\Api\HostingerApi;

$client = new HostingerApi('YOUR_API_TOKEN');

$catalog = $client->billing->catalog->list();
foreach ($catalog as $item) {
    echo $item->name . ': ' . number_format($item->price / 100, 2) . " USD\n";
}

Manage Payment Methods

# List payment methods
curl -X GET "https://developers.hostinger.com/api/billing/v1/payment-methods" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Set default payment method
curl -X POST "https://developers.hostinger.com/api/billing/v1/payment-methods/517244" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Delete a payment method
curl -X DELETE "https://developers.hostinger.com/api/billing/v1/payment-methods/517244" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

Manage Subscriptions

# List all subscriptions
curl -X GET "https://developers.hostinger.com/api/billing/v1/subscriptions" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Disable auto-renewal for a subscription
curl -X DELETE "https://developers.hostinger.com/api/billing/v1/subscriptions/12345/auto-renewal/disable" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Enable auto-renewal for a subscription
curl -X PATCH "https://developers.hostinger.com/api/billing/v1/subscriptions/12345/auto-renewal/enable" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

API Reference

Catalog

MethodEndpointDescription
GET/api/billing/v1/catalogGet catalog items (filterable by category and name)

Orders

Removed: the generic POST /api/billing/v1/orders endpoint is no longer part of the API. Place orders through the resource-specific endpoints instead — POST /api/domains/v1/portfolio for domains and POST /api/vps/v1/virtual-machines for VPS.

Payment Methods

MethodEndpointDescription
GET/api/billing/v1/payment-methodsList payment methods
POST/api/billing/v1/payment-methods/{id}Set default payment method
DELETE/api/billing/v1/payment-methods/{id}Delete payment method

Subscriptions

MethodEndpointDescription
GET/api/billing/v1/subscriptionsList all subscriptions
DELETE/api/billing/v1/subscriptions/{id}/auto-renewal/disableDisable auto-renewal
PATCH/api/billing/v1/subscriptions/{id}/auto-renewal/enableEnable auto-renewal

Best Practices

Pricing

  • Always fetch catalog prices before displaying to users — prices are in cents
  • Divide by 100 and format appropriately for display

Orders

  • The generic /api/billing/v1/orders endpoint has been removed from the API
  • Use POST /api/domains/v1/portfolio for domain purchases
  • Use POST /api/vps/v1/virtual-machines for VPS purchases
  • Prefer non-credit-card payment methods to avoid verification delays

Payment Methods

  • New payment methods must be added through hPanel, not the API
  • If no payment method is specified in an order, the default method is used automatically
  • Remove unused payment methods to keep your account clean

Subscriptions

  • Monitor subscriptions to avoid unexpected service interruptions
  • Disable auto-renewal well before expiration if you intend to cancel

Troubleshooting

401 Unauthorized

  • Verify your API token is valid and not expired
  • Token permissions match the owning user's permissions
  • Check Authorization: Bearer <token> header format

422 Unprocessable Content

  • Invalid item_id in order request — verify against catalog
  • Invalid payment_method_id — list payment methods first

429 Too Many Requests

  • You've exceeded rate limits — back off and retry
  • Repeated violations may temporarily block your IP

Order Not Processing

  • credit_card payments may require additional verification
  • Check order status in hPanel
  • Try a different payment method

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.