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

Relevance AI Billing API

The billing API from Relevance AI — 19 operation(s) for billing.

Relevance AI Billing API is one of 32 APIs that Relevance AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Billing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 22 operations across 19 paths, and defines 37 schemas. It is described by OpenAPI 3.2.0, at version latest.

Requests are made against a single base URL, /latest.

22 operations 19 paths 37 schemas 1 DELETE7 GET12 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://api-{region}.stack.tryrelevance.com/latest
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Relevance AI Billing API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (AuthorizationHeader). By default, every request must be authenticated.

  • AuthorizationHeader — Authorization credentials. Header authorization should be in the form of: project:apikey

Paths & Operations 22

Across 19 paths, the API surfaces 22 operations — 1 DELETE, 7 GET, 12 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Billing 22
GET
/organizations/{organization_id}/billing/totals
GetBillingTotals
GetBillingTotals 2 params → 200
GET
/organizations/{organization_id}/billing/get_billing_frontend_link
GetBillingFrontendLink
GetBillingFrontendLink 3 params → 200
GET
/organizations/{organization_id}/billing/checkout
GetBillingCheckoutSession
GetBillingCheckoutSession 2 params → 200
POST
/organizations/{organization_id}/billing/update
UpdateOrganizationBilling
UpdateOrganizationBilling 1 param body → 200
POST
/organizations/{organization_id}/subscription/sync
SyncSubscription
SyncSubscription 1 param body → 200
POST
/organizations/{organization_id}/subscription/downgrade
DowngradeSubscription
DowngradeSubscription 1 param body → 200
POST
/organizations/{organization_id}/billing/subscription/change
ChangeBillingSubscription
ChangeBillingSubscription 1 param body → 200
POST
/organizations/{organization_id}/downgrade/cancel
CancelDowngrade
CancelDowngrade 1 param body → 200
POST
/organizations/{organization_id}/subscription/cancel
CancelSubscription
CancelSubscription 1 param body → 200
POST
/organizations/{organization_id}/credits/buy
BuyCredits
BuyCredits 1 param body → 200
POST
/organizations/{organization_id}/credits/checkout
CreditPurchaseCheckoutSession
CreditPurchaseCheckoutSession 1 param body → 200
GET
/organizations/{organization_id}/checkout/status
GetCheckoutCompletionStatus
GetCheckoutCompletionStatus 2 params → 200
POST
/organizations/{organization_id}/trial/trigger
TriggerOrganizationPlanTrial
TriggerOrganizationPlanTrial 1 param body → 200
POST
/organizations/{organization_id}/aggregate/agents/credits
AggregateAgentsCreditsUsed
AggregateAgentsCreditsUsed 1 param body → 200
POST
/organizations/{organization_id}/aggregate/tools/credits
AggregateToolsCreditsUsed
AggregateToolsCreditsUsed 1 param body → 200
GET
/organizations/{organization_id}/retention-offer/eligibility
GetRetentionOfferEligibility
GetRetentionOfferEligibility 1 param → 200
POST
/organizations/{organization_id}/retention-offer/accept
AcceptRetentionOffer
AcceptRetentionOffer 1 param body → 200
GET
/billing/{organization_id}/overage
GetOverageConfig
GetOverageConfig 1 param → 200
PUT
/billing/{organization_id}/overage
UpdateOverageConfig
UpdateOverageConfig 1 param body → 200
GET
/billing/{organization_id}/auto-recharge/{currency}
GetAutoRechargeConfig
GetAutoRechargeConfig 2 params → 200
PUT
/billing/{organization_id}/auto-recharge/{currency}
UpsertAutoRechargeConfig
UpsertAutoRechargeConfig 2 params body → 200
DELETE
/billing/{organization_id}/auto-recharge/{currency}
DeleteAutoRechargeConfig
DeleteAutoRechargeConfig 2 params body → 200

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are ChangeBillingSubscriptionInput (5 properties), DowngradeSubscriptionInput (4 properties), GetRetentionOfferEligibilityOutput (3 properties), UpdateOrganizationBillingInput (3 properties). Each schema is shown below with its type and property counts.

AggregateToolsCreditsUsedOutput
object
3 properties 2 required
DeleteAutoRechargeConfigOutput
object
1 property 1 required
DowngradeSubscriptionOutput
object
CancelDowngradeOutput
object
UpdateOverageConfigInput
object
3 properties
UpdateOverageConfigOutput
object
3 properties
AggregateToolsCreditsUsedInput
object
2 properties
GetCheckoutCompletionStatusOutput
object
1 property 1 required
UpsertAutoRechargeConfigOutput
object
2 properties 2 required
AcceptRetentionOfferOutput
object
2 properties 2 required
CancelSubscriptionInput
object
1 property
CreditPurchaseCheckoutSessionOutput
object
2 properties 2 required
AggregateAgentsCreditsUsedOutput
object
3 properties 2 required
CancelSubscriptionOutput
object
GetBillingTotalsOutput
object
1 property 1 required
BuyCreditsInput
object
2 properties 2 required
AggregateAgentsCreditsUsedInput
object
2 properties
GetBillingCheckoutSessionOutput
object
1 property 1 required
GetOverageConfigOutput
object
3 properties
CancelDowngradeInput
object
1 property 1 required
ChangeBillingSubscriptionInput
object
5 properties 3 required
DowngradeSubscriptionInput
object
4 properties 2 required
SyncSubscriptionOutput
object
UpdateOrganizationBillingInput
object
3 properties 2 required
UpdateOrganizationBillingOutput
object
1 property
TriggerOrganizationPlanTrialInput
object
1 property
AcceptRetentionOfferInput
object
2 properties
GetRetentionOfferEligibilityOutput
object
3 properties 1 required
SyncSubscriptionInput
CreditPurchaseCheckoutSessionInput
object
2 properties 2 required
ChangeBillingSubscriptionOutput
object
2 properties 2 required
BuyCreditsOutput
object
GetBillingFrontendLinkOutput
object
1 property 1 required
TriggerOrganizationPlanTrialOutput
object
1 property
GetAutoRechargeConfigOutput
object
1 property 1 required
UpsertAutoRechargeConfigInput
object
2 properties 2 required
DeleteAutoRechargeConfigInput

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relevance-ai-billing-api-openapi.yml Raw ↑

Other APIs Relevance AI publishes across the network.

Relevance AI MCP Server
Relevance AI Agent Debug Configs API
Relevance AI Agent Runtime Events API
Relevance AI Agents API
Relevance AI Alarms API
Relevance AI Analytics API
Relevance AI Apify API
Relevance AI Auth API
Relevance AI Branding Kit API
Relevance AI Branding Kits API
Relevance AI Chat API
Relevance AI Evals API
Where this information came from

This is an independent, third-party profile of Relevance AI Billing 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.