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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Lit Protocol

Lit Protocol Billing API

The Billing API from Lit Protocol — 4 operation(s) for billing.

Documentation Provider Profile APIs.io OpenAPI GitHub

Lit Protocol Billing API is one of 5 APIs that Lit Protocol 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 and API documentation.

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

Requests are made against a single base URL, /core/v1/.

4 operations 4 paths 7 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.chipotle.litprotocol.com/core/v1
Resource Areas
1

Paths & Operations 4

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

Billing 4
GET
/billing/stripe_config
GET /billing/stripeconfig — returns the Stripe publishable key. No auth required; the publishable key is safe to expose.
billing_stripe_config → default
GET
/billing/balance
GET /billing/balance — returns the current credit balance for the authenticated user.
billing_balance 1 param → default
POST
/billing/create_payment_intent
POST /billing/createpaymentintent — creates a Stripe PaymentIntent and returns the clientsecret for use with Stripe.js confirmCardPayment.
billing_create_payment_intent 1 param body → default
POST
/billing/confirm_payment
POST /billing/confirmpayment — verifies a succeeded PaymentIntent and credits the account.
billing_confirm_payment 1 param body → default

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are CreatePaymentIntentResponse (2 properties), BillingBalanceResponse (2 properties), CreatePaymentIntentRequest (1 property), StripeConfigResponse (1 property). Each schema is shown below with its type and property counts.

BillingBalanceResponse
object
GET /billing/balance — current credit balance for the authenticated API key.
2 properties 2 required
ConfirmPaymentRequest
object
POST /billing/confirmpayment
1 property 1 required
AccountOpResponse
object
Response for account config operations (addpkptogroup, removepkpfromgroup, addusageapikey, removeusageapikey).
1 property 1 required
ErrMessage
string
CreatePaymentIntentResponse
object
POST /billing/createpaymentintent — client secret for Stripe.js confirmCardPayment.
2 properties 2 required
StripeConfigResponse
object
GET /billing/stripeconfig — returns the Stripe publishable key for Stripe.js.
1 property 1 required
CreatePaymentIntentRequest
object
POST /billing/createpaymentintent
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lit-protocol-billing-api-openapi.yml Raw ↑

Other APIs Lit Protocol publishes across the network.

Lit Network Node JSON-RPC (SDK-mediated)
AE Profile APIs.io
Lit Protocol Account Management API
AE Profile APIs.io
Lit Protocol Actions API
AE Profile APIs.io
Lit Protocol Configuration API
AE Profile APIs.io
#Billing
← Back to L APIs
API Details
ID
lit-protocol:lit-protocol-billing-api
Base URL
https://api.chipotle.litprotocol.com/core/v1
Docs
https://developer.litprotocol.com/
Provider
Lit Protocol
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lit-protocol-billing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lit-protocol-billing-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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