On this page
purchaseSupportPlan
mutation · in the family Billing and the wallet
What it does
Buy the quarterly handholding plan — sized by your recent usage, charged to the stored card, covering this month and the next two. It starts serving human incidents 72 hours after purchase; renewals are automatic until you cancel.
Buy the quarterly handholding plan: classes the trailing quarter's usage, charges the tier OFF-SESSION to the stored card (the purchaseTokensNow ladder), and arms the plan — it serves HUMAN incidents 72 h after purchase (the CAA activation wait; the $150 per-incident lane stays open meanwhile). The quarter covers the purchase month + 2 (renewals are AUTOMATIC — the billing engine collects each next quarter until you cancel). Already covered refuses CONFLICT (nothing to buy); a canceled-but-covered plan RESUMES instead (the cancel clears, nothing mints, no new wait); a lapsed/never plan mints + the wait re-arms. Wallet + stored method required. Requires the unrestricted capability. Template class A16_BILLING (hand-derived v93).
What happens
Charges real money to the stored card off-session. If a canceled plan is still inside its paid quarter, this resumes it instead (no new charge, no new wait).
Who may call it
Capability area: Billing and the wallet — Your platform bill, token purchases and the usage and cost reads.
- Owner
- Manager
- Associate Manager
- An API key whose scope allows
api:purchaseSupportPlan
Returns
SupportPlanReport SupportPlanReport! — The caller group's handholding-plan report (the quarterly HUMAN-support plans, consumption-sized): the LIVE size classing (what a purchase today charges), the ruled per-incident price, and the plan's standing in the ONE coverage vocabulary.
Example request
mutation ExamplePurchaseSupportPlan {
purchaseSupportPlan {
sizeClass
quarterUsdCents
basisTokensPerMonth
thresholdsVersion
incidentUsdCents
standing
onboardingUntil
onboardingCovers
purchasedAt
activatesAt
coveredThroughMonth
canceledAt
}
}
Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.
Example response
{
"data": {
"purchaseSupportPlan": {
"sizeClass": "<size class>",
"quarterUsdCents": 1,
"basisTokensPerMonth": 1,
"thresholdsVersion": 1,
"incidentUsdCents": 1,
"standing": "<standing>",
"onboardingUntil": "<onboarding until>",
"onboardingCovers": true,
"purchasedAt": "2027-01-31T00:00:00.000Z",
"activatesAt": "2027-01-31T00:00:00.000Z",
"coveredThroughMonth": "<covered through month>",
"canceledAt": "2027-01-31T00:00:00.000Z"
}
},
"extensions": {
"at": {
"callId": "01EXAMPLE-CALL-ID",
"version": {
"requested": {
"name": "genesis",
"number": 0
},
"serviced": {
"name": "genesis",
"number": 0
}
}
}
}
}
Errors this call can answer
VALIDATION/INVALID— Something in the request is not valid. (VALIDATION)AUTHN/REQUIRED— Sign in to do this. (AUTHN)AUTHZ/FORBIDDEN— Your role does not allow this action. (AUTHZ)RATE_LIMIT/THROTTLED— Too many requests in a short time. (RATE_LIMIT)CONFLICT/*— The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)VALIDATION/VERSION_REQUIRED— The request did not say which app version it came from. (VALIDATION)