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

Helicone Stripe API

The Stripe API from Helicone — 22 operation(s) for stripe.

Helicone Stripe API is one of 33 APIs that Helicone publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Stripe. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, pricing, an API reference, and an engineering blog.

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

Requests are made against 2 base URLs: https://api.helicone.ai/, http://localhost:8585/.

25 operations 22 paths 12 schemas 3 DELETE10 GET12 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://ai-gateway.helicone.ai
Authentication
API Key
License
MIT
Resource Areas
1

Authentication & Security 1

Helicone Stripe API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_key).

  • api_key — Bearer token authentication. Format: 'Bearer YOURAPIKEY'

Paths & Operations 25

Across 22 paths, the API surfaces 25 operations — 3 DELETE, 10 GET, 12 POST. Each is listed below with its method, path, parameters, and response codes.

Stripe 25
GET
/v1/stripe/subscription/cost-for-prompts
Get cost for prompts
GetCostForPrompts → 200
GET
/v1/stripe/subscription/cost-for-evals
Get cost for evals
GetCostForEvals → 200
GET
/v1/stripe/subscription/cost-for-experiments
Get cost for experiments
GetCostForExperiments → 200
GET
/v1/stripe/subscription/free/usage
Get free usage
GetFreeUsage → 200
POST
/v1/stripe/cloud/checkout-session
Create cloud gateway checkout session
CreateCloudGatewayCheckoutSession body → 200
POST
/v1/stripe/subscription/new-customer/upgrade-to-pro
Upgrade to pro
UpgradeToPro body → 200
POST
/v1/stripe/subscription/existing-customer/upgrade-to-pro
Upgrade existing customer
UpgradeExistingCustomer body → 200
POST
/v1/stripe/subscription/new-customer/upgrade-to-team-bundle
Upgrade to team bundle
UpgradeToTeamBundle body → 200
POST
/v1/stripe/subscription/existing-customer/upgrade-to-team-bundle
Upgrade existing customer to team bundle
UpgradeExistingCustomerToTeamBundle body → 200
POST
/v1/stripe/subscription/manage-subscription
Manage subscription
ManageSubscription → 200
POST
/v1/stripe/subscription/undo-cancel-subscription
Undo cancel subscription
UndoCancelSubscription → 200
POST
/v1/stripe/subscription/add-ons/{productType}
Add ons
AddOns 1 param → 200
DELETE
/v1/stripe/subscription/add-ons/{productType}
Delete add ons
DeleteAddOns 1 param → 200
GET
/v1/stripe/subscription/preview-invoice
Preview invoice
PreviewInvoice → 200
POST
/v1/stripe/subscription/cancel-subscription
Cancel subscription
CancelSubscription → 200
POST
/v1/stripe/subscription/migrate-to-pro
Migrate to pro
MigrateToPro → 200
GET
/v1/stripe/payment-intents/search
Search payment intents
SearchPaymentIntents 3 params → 200
GET
/v1/stripe/subscription
Get subscription
GetSubscription → 200
GET
/v1/stripe/auto-topoff/settings
Get auto topoff settings
GetAutoTopoffSettings → 200
POST
/v1/stripe/auto-topoff/settings
Update auto topoff settings
UpdateAutoTopoffSettings body → 200
DELETE
/v1/stripe/auto-topoff/settings
Disable auto topoff
DisableAutoTopoff → 200
GET
/v1/stripe/payment-methods
Get payment methods
GetPaymentMethods → 200
POST
/v1/stripe/payment-methods/setup-session
Create setup session
CreateSetupSession body → 200
DELETE
/v1/stripe/payment-methods/{paymentMethodId}
Remove payment method
RemovePaymentMethod 1 param → 200
GET
/v1/stripe/subscription/usage-stats
Get usage stats
GetUsageStats → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are LLMUsage (8 properties), PaymentIntentRecord (7 properties), AutoTopoffSettings (6 properties), PaymentMethod (5 properties). Each schema is shown below with its type and property counts.

PaymentMethod
object
5 properties 5 required
UpgradeToProRequest
object
3 properties
CreateSetupSessionRequest
object
1 property
UpdateAutoTopoffSettingsRequest
object
4 properties 4 required
CreateCloudGatewayCheckoutSessionRequest
object
2 properties 1 required
DailyUsageDataPoint
object
3 properties 3 required
LLMUsage
object
8 properties 8 required
AutoTopoffSettings
object
6 properties 6 required
UpgradeToTeamBundleRequest
object
1 property
StripePaymentIntentsResponse
object
4 properties 4 required
UsageStatsResponse
object
4 properties 4 required
PaymentIntentRecord
object
7 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

helicone-stripe-api-openapi.yml Raw ↑

Other APIs Helicone publishes across the network.

Helicone Agent API
Helicone API Key API
Helicone Comparison API
Helicone Credits API
Helicone Customer API
Helicone Dashboard API
Helicone Dataset API
Helicone Evals API
Helicone Evaluator API
Helicone Experiment API
Helicone HeliconeSql API
Helicone Integration API
Where this information came from

This is an independent, third-party profile of Helicone Stripe 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.