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

Frontline Billing API

View billing plan details, credits, and renewal information

Frontline Billing API is one of 43 APIs that Frontline 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 a getting-started guide.

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

Requests are made against a single base URL, https://prod-api.getfrontline.ai.

7 operations 7 paths 11 schemas 5 GET2 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://prod-api.getfrontline.ai/public/v1
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Frontline Billing API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (Account API Key) (accountApiKey). It accepts HTTP bearer tokens (User API Key) (userApiKey).

  • accountApiKey — Account-level API key (GENERAL). Authenticates on behalf of the entire account. Use for read-only and analytics endpoints marked as account-level in this docum…
  • userApiKey — User-level API key (USER). Authenticates on behalf of a specific user. Required for write operations and user-owned resources. Also accepted on all account-lev…

Paths & Operations 7

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

Billing 7

View billing plan details, credits, and renewal information

GET
/public/v1/billing
Get billing plan details
getBillingPlan → 200401404
GET
/public/v1/billing/usage
Get Studio usage details
getStudioUsage → 200401
GET
/public/v1/billing/credits/history
Get credit consumption history
getCreditHistory 2 params → 200401
GET
/public/v1/billing/max/usage
Get Max usage details
getMaxUsage → 200401
GET
/public/v1/billing/max/seats
List Max seat assignments
getMaxSeats → 200401
POST
/public/v1/billing/max/seats/assign
Assign a Max seat to a user
assignMaxSeat body → 200400404
POST
/public/v1/billing/max/seats/unassign
Unassign a user's Max seat
unassignMaxSeat body → 200400404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are PublicCreditHistoryItem (7 properties), PublicMaxUsage (5 properties), PublicStudioUsage (5 properties), PublicMaxSeats (5 properties). Each schema is shown below with its type and property counts.

ErrorBody
object
3 properties 2 required
PublicMaxUsage
object
5 properties
PublicCreditHistory
object
1 property 1 required
PublicMaxSeatInput
object
1 property 1 required
PublicCreditHistoryItem
object
7 properties 3 required
PublicMaxSeatUser
object
5 properties 1 required
PublicMaxSeats
object
5 properties 5 required
PublicStudioUsage
object
5 properties
BillingPlan
object
4 properties 4 required
PublicMaxSeatResult
object
3 properties 3 required
Error
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

frontline-billing-api-openapi.yml Raw ↑

Other APIs Frontline publishes across the network.

Frontline Account API
Frontline Agent Builder API
Frontline Agents API
Frontline AI Models API
Frontline Flow Variables API
Frontline Flows API
Frontline Incoming Webhooks API
Frontline Intents API
Frontline Object activities API
Frontline Object aggregations API
Frontline Object export API
Frontline Object fields API
Where this information came from

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