How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

StakPak Billing (V2) API

The Billing (V2) API from StakPak — 6 operation(s) for billing (v2).

StakPak Billing (V2) API is one of 20 APIs that StakPak publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Billing (V2). The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 6 operations across 6 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://apiv2.stakpak.dev, http://localhost:4000.

6 operations 6 paths 14 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://apiv2.stakpak.dev
Authentication
HTTP Bearer, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

StakPak Billing (V2) API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Api_Key). It accepts HTTP bearer tokens (JWT) (Token). An API key is passed in the cookie as .idToken (cookie).

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Billing (V2) 6
GET
/v2/{account}/billing
Get Billing Customer
get_billing_customer_handler 1 param → 200400
POST
/v2/{account}/billing/attach
Attach Product
post_attach_product_handler body → 200400
POST
/v2/{account}/billing/cancel
Cancel Product
post_cancel_product_handler body → 200400
POST
/v2/{account}/billing/checkout
Create Checkout Session
post_checkout_handler body → 200400
POST
/v2/{account}/billing/portal
Get Billing Portal URL
post_billing_portal_handler body → 200400
GET
/v2/{account}/billing/products/{product_id}
Get Product
get_product_handler 3 params → 200400404

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are BillingFeatureInfo (11 properties), PostAttachProductPayload (9 properties), PostCheckoutPayload (7 properties), BillingProductInfo (7 properties). Each schema is shown below with its type and property counts.

GetProductResponse
PostCancelProductPayload
object
3 properties 1 required
PostCheckoutPayload
object
7 properties 1 required
ErrorBody
object
2 properties 2 required
PostBillingPortalResponse
object
1 property 1 required
GetBillingCustomerResponse
object
5 properties 4 required
PostCheckoutResponse
object
4 properties 4 required
CheckoutOption
object
2 properties 2 required
BillingFeatureInfo
object
Minimal feature info returned for billing
11 properties 7 required
PostAttachProductPayload
object
9 properties 1 required
PostBillingPortalPayload
object
1 property
BillingProductInfo
object
Minimal product info returned for billing
7 properties 4 required
PostAttachProductResponse
object
6 properties 3 required
ErrorResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stakpak-billing-v2-api-openapi.yml Raw ↑

Other APIs StakPak publishes across the network.

StakPak Account API
StakPak Account (V2) API
StakPak Agents API
StakPak Agents (V2) API
StakPak Chat API
StakPak Commands API
StakPak Knowledge API
StakPak Knowledge Registry API
StakPak MCP API
StakPak Memory API
StakPak Memory (V2) API
StakPak Organizations API
Where this information came from

This is an independent, third-party profile of StakPak Billing (V2) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.