InfraRabbit provider feed, version 1

An open format for a hosting provider to publish its own prices as one JSON file. Anyone can read it, InfraRabbit included, without scraping your site.

Spec licence: CC BY 4.0. Current version: 1.0. Shaped with EDIS Global's feed (schema 2.0) as a starting point; this is an acknowledgement, not an endorsement by or of anyone.

Why publish a feed

• One fetch a day instead of scraping: your servers see one small request, not a crawler walking your pages.
• Exact prices: we show what you publish, to the cent, with the currency, the VAT basis and the billing period.
• You control accuracy: a number is right because you wrote it, and a price change you announce shows up with its date.

How to publish

1. Write one JSON file per location (or one file per provider with a plan list per location file; v1 keeps it to one location per file). Follow the schema; see the example.
2. Serve it at a stable public URL of your own, over HTTPS, as application/json. Regenerate it whenever a price changes, and at least daily.
3. Tell us the URL (next section). Publishing the URL and telling us is your permission to read it; nothing else is needed, and we read it no more than once a day.
4. Check the file with the validator below before you tell us.

Rules of the format: state, never estimate. Leave out what you do not know; never write 0 for an unknown (0 means free). Prices are the ones you publish, in your own currency. Unknown fields are allowed and ignored, so you can add your own.

How to tell us

Write to inbox@infrarabbit.com with the feed URL, or use the corrections page if a number of ours differs from your feed. We read the feed, show the prices and date them from your generated_at.

Fields

Required fields are marked. Types follow JSON Schema; dates are ISO 8601; a TB is 1000 GB unless gb_per_tb says otherwise.

Example

The same file as example.json:

{
  "schema_version": "1.0",
  "provider": {
    "name": "Example Hosting B.V.",
    "url": "https://www.example-hosting.test",
    "contact": "feeds@example-hosting.test"
  },
  "generated_at": "2026-11-13T06:00:00Z",
  "location": {
    "id": "nl-ams",
    "country": "NL",
    "city": "Amsterdam",
    "display_name": "Netherlands - Amsterdam",
    "datacenter": "Example DC1"
  },
  "plans": [
    {
      "id": "vps-s",
      "name": "VPS S",
      "url": "https://www.example-hosting.test/vps/s",
      "order_url": "https://my.example-hosting.test/order?plan=vps-s",
      "vcpu": 1,
      "vcpu_type": "shared",
      "cpu_model": "AMD EPYC 7543",
      "ram_gb": 2,
      "disk_gb": 40,
      "disk_type": "NVMe",
      "traffic_tb": 2,
      "traffic_counted": "in+out",
      "port_speed_mbps": 1000,
      "ipv4_included": 1,
      "ipv6_prefix": "/64",
      "price": {
        "amount": 4.5,
        "currency": "EUR",
        "vat_included": false,
        "billing_period": "month"
      },
      "terms": [
        {
          "months": 12,
          "price_per_month": 4.0,
          "setup_fee": 0
        }
      ],
      "setup_fee": 0,
      "availability": {
        "status": "in_stock",
        "checked_at": "2026-11-13T05:55:00Z"
      }
    },
    {
      "id": "vps-m",
      "name": "VPS M",
      "url": "https://www.example-hosting.test/vps/m",
      "vcpu": 4,
      "vcpu_type": "dedicated",
      "ram_gb": 8,
      "disk_gb": 160,
      "disk_type": "NVMe",
      "traffic_tb": 10,
      "gb_per_tb": 1000,
      "traffic_counted": "out",
      "bandwidth_mbps_guaranteed": 250,
      "port_speed_mbps": 1000,
      "ipv4_included": 1,
      "price": {
        "amount": 16,
        "currency": "EUR",
        "vat_included": false,
        "billing_period": "month"
      },
      "availability": {
        "status": "unknown"
      },
      "end_of_sale_date": "2027-06-30"
    }
  ],
  "addons": [
    {
      "type": "extra_ipv4",
      "price": {
        "amount": 2,
        "currency": "EUR",
        "vat_included": false,
        "billing_period": "month"
      }
    },
    {
      "type": "backups",
      "price": {
        "amount": 1.2,
        "currency": "EUR",
        "vat_included": false,
        "billing_period": "month"
      }
    },
    {
      "type": "traffic_overage_per_tb",
      "price": {
        "amount": 1,
        "currency": "EUR",
        "vat_included": false,
        "billing_period": "once"
      }
    }
  ],
  "policies": {
    "port_25": "on_request",
    "sla_percent": 99.9,
    "money_back_days": 14,
    "aup_url": "https://www.example-hosting.test/aup"
  },
  "changes": [
    {
      "effective_date": "2027-01-01",
      "plan_id": "vps-s",
      "old_price": 4.5,
      "new_price": 5.0,
      "note": "Announced 2026-11-01 on our blog."
    }
  ]
}

Validation

Post your file to the validator. It reads only what you send; it never fetches a URL, so there is no GET form with ?url=. Answers are JSON: valid and a list of errors, each with a path (a JSON pointer) and a message. At most 512 KB per file, rate limited like our other public requests.

curl -sS -X POST --data-binary @feed.json \
  -H "Content-Type: application/json" \
  https://infrarabbit.com/spec/provider-feed/validate

Status 200 means the file was read (see valid); 400 means it is not JSON; 413 means it is too large; 429 means slow down.

Badge

If you publish the feed, you can say so. Paste this text link on your site:

<a href="https://infrarabbit.com/spec/provider-feed">Prices published in InfraRabbit feed format v1</a>

Versioning and changelog

The version is in schema_version. Within version 1 we only add optional fields and values; a file that is valid today stays valid. A change that could break a valid file becomes version 2 at a new address (v2.schema.json); version 1 stays online.

• 1.0 (13 November 2026): first version.