BLAZINGFAST — PRODUCT AND AUTOMATION BRIEFS
Reviewed: 7 October 2026. Current Python, Node.js, PHP and Go release is shown below.
Production release: SDK/CLI 0.1.17; contract 2026-10-07.1. Check GET /v1/version and GET /v1/capabilities before using optional workflow features. Strict response validation is enforced.


Choose a product:
01-vps.txt                    VPS compute and lifecycle
02-dedicated-servers.txt      Dedicated inventory, installation and management
03-web-hosting.txt            cPanel website and email hosting
04-domains.txt                Registrations and domain management
05-dns.txt                    Zones, records, templates and imports
06-website-protection.txt     HTTP/HTTPS proxy, mitigation and country access
07-tcp-proxy.txt              TCP forwarding, limits and statistics
08-storage.txt                Storage volume attachment and management
09-backups-snapshots.txt      VPS recovery operations
10-ssh-firewall.txt           Access keys and network policies
11-billing-orders.txt         Catalog, orders, invoices and balance payment
12-affiliates-partnerships.txt Affiliate rewards and integration discussions
13-catalog-discovery.txt      Simple regions, products, images and SSH-key discovery
14-integration-workflows.txt  Quote/deploy/status, references, errors and webhooks

GET STARTED
Customer portal: https://my.blazingfast.io
Guides: https://docs.blazingfast.io/howto/api
API origin: https://api.blazingfast.io (do not append /v1 for SDK configuration)
Endpoint schema: https://docs.blazingfast.io/api/public/openapi/userapi-v1
API keys and current SDK downloads: https://my.blazingfast.io/settings/api
Hosted MCP permissions and approvals: https://my.blazingfast.io/settings/connections

CLI: Install the downloaded Python archive in a Python 3.10+ virtual environment
on Windows, macOS or Linux. Set BF_API_BASE_URL and either BF_API_KEY plus
BF_API_SECRET (signed key), or BF_API_BEARER (complete issued bearer token).
Use bf for new integrations. bf-api is an actively supported compatibility alias
of the same CLI, not a separate lower-level interface. Both are included in the
Python SDK archive and use the same commands, authentication and package version.
Start with bf version, bf capabilities and bf service list. Secrets and .env files
are not loaded automatically. Pagination is endpoint-specific: page/limit,
cursor/next_cursor or offset/next_offset. Use limit for sizes, and follow each
endpoint's own defaults/bounds. page_size/pageSize are deprecated HTTP aliases
only where documented. The service CLI uses --limit; --page-size remains compatible.
See https://docs.blazingfast.io/api/integration-guide for all pagination models.
Use the portal's API origin for your environment. Keep TLS verification enabled.

HOSTED MCP: Copy its endpoint from Settings -> API -> MCP. Authenticate via
OAuth and select permissions/policy: Read only, Write with approval or Full access.
Use get_operation_request to track a returned request, not repeat the action.
Hosted MCP never returns passwords or private keys. Client support varies.

LOCAL MCP: The Python package installs bf-api-mcp, a stdio server on your machine.
It uses your API key, has viewing tools by default, and a smaller tool catalog.
BF_API_MCP_ENABLE_MUTATIONS=1 exposes selected writes; they execute directly,
without hosted dashboard approval. Keep BF_API_MCP_ENABLE_CREDENTIALS disabled.

INTERPRETING THESE BRIEFS
SERVICE_UUID, PRODUCT_UUID, VARIANT_UUID, INVOICE_UUID and ORDER_UUID are distinct
IDs returned by discovery. Example domains/IPs/keys are placeholders, not defaults.
Read the resource before modifying it. Product availability, prices, periods,
OS choices, region, stock and account permissions must be discovered live.
Some API/SDK operations have no CLI or MCP equivalent; the briefs say so.
API calls stay within the authenticated account/project's allowed resources.

Create order -> inspect unpaid invoice -> explicitly authorize payment -> track
provisioning. Draft order creation does not charge the account. Atomic deployment is the documented exception; accepted is not completed. Balance payment
may be partial. Preserve the same retry key and payload after an uncertain result;
read state before retrying. Do not automatically retry payments or destructive work.

The brief set covers BlazingFast, not Snabb's separate API/CLI/runtime. Customer
object-storage, license automation and a public reseller API are not claimed here.
Partner pricing/support terms require an agreed commercial proposal.

Support reports should include action, time/timezone, client version, HTTP status,
error code and request ID. Never include API secrets, passwords or private keys.