BLAZINGFAST — AFFILIATE REWARDS AND PARTNER INTEGRATIONS
Reviewed: 5 October 2026. Setup: 00-index.txt.
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.

PURPOSE
Affiliate referral rewards and business integrations are distinct arrangements.
Use the customer portal for available referral links, qualifying rewards and
earned-balance accounting. Do not assume rewards are withdrawable or guaranteed.

API / CLI / MCP
There is no documented public affiliate-management or reseller-administration
endpoint, CLI command or MCP tool. Generic invoice, balance and service tools
do not manage referrals, partner customers or affiliate payouts.
For platform integration, use the product-specific customer APIs with scoped
account-owned credentials; see the product briefs and capability matrix.

PARTNERSHIP EVALUATION
Identify intended products, regions, expected volumes and ordering workflows.
Agree account ownership, who bills the end customer, payment model, support
responsibilities and cancellation/reconciliation procedures before a pilot.
Commercial discounts, wholesale rates, credit terms, SLAs and reseller rights
require an agreed proposal; no universal partner pricing is promised here.
Customer API access does not automatically authorize cross-account administration,
customer impersonation or resale. Keep each integration's credentials separate.

NEXT STEP
Use the support contact in the portal to arrange a technical/commercial discussion.
Start a limited pilot only after its scope, permissions and acceptance criteria
are agreed. No private customer data or live credentials belong in a demo pack.