The balance and activity are examples, not your funds or requests. This preview cannot send AI requests or make payments. Your real sign-in is separate.
Affiliates
Preview partner-bot attribution, registrations, payment volume, downstream spend and webhook health.
AI Deals Demo
@modelgate_demo_partner
- Referrer
- Bot owner in Model Gate (demo)
- Webhook endpoint
https://model-gate.com/api/v1/telegram/webhook/DEMO…- Last webhook received
- 38 seconds ago
- Last checked
- 1 minute ago
What users can monitor
The Demo preview intentionally uses synthetic figures and a non-secret placeholder endpoint.
Resell AI access with the Partner API
Build your own bot, website or application and set your own markup. Use the Partner API to create separate customer keys, configure usage limits and read accounting data. You collect payments and bill your customers in your own service; Model Gate debits your account at its effective tariff.
Example: your price ×2
Set usage_price_basis to user_price and usage_price_multiplier to 2.000000. For an operation with a $1.00 account debit, the valued usage is $2.00. If you charge your customer that $2.00, the difference is $1.00 before fees, taxes, refunds and other costs: a 100% markup, or a 50% gross margin—not a 100% margin.
API-key creation example
POST /api/v1/partner/keys · Content-Type: application/json
Required server-side headers: Authorization: Bearer mg_partner_..., Idempotency-Key.
{
"name": "Customer 123",
"rpm_limit": 30,
"concurrency_limit": 2,
"spend_limit": "20.0000000000",
"usage_price_basis": "user_price",
"usage_price_multiplier": "2.000000"
}Use a unique Idempotency-Key for each new management operation; reuse it only for a retry of the identical operation. Store the Partner API credential only on your server, never in a customer app. Save the new customer key when returned: its full value is shown only on creation or rotation. This page sends no API request.
Usage is a resettable USD quota, not a separate customer wallet or an automatic payment. spend_limit = 20.0000000000 caps valued usage, not your lifetime account spend. Key and group limits both apply; account balance is checked separately. Already admitted concurrent requests and delayed settlement can exceed the limit. Do not promise a strictly prepaid customer balance; reconcile finalized usage in your billing system.
Choose another supported multiplier for a different markup. Read usage_cost per finalized request or reconcile the key usage counter; keep cost and total_spent separate. Do not add the key and group usage for the same operation or bill cumulative counters twice. Usage resets and asynchronous settlement must be handled by your own ledger. Resale revenue is separate from local affiliate commissions and is not guaranteed profit.