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

verifly-email Billing API

Credit packages and Stripe / crypto checkout. Agent-native crypto pay.

verifly-email Billing API is one of 11 APIs that verifly-email publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 8 JSON Schema definitions.

Tagged areas include Billing. The published artifact set on APIs.io includes an OpenAPI specification and 8 JSON Schemas.

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

Requests are made against a single base URL, https://verifly.email.

4 operations 3 paths 12 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://verifly.email
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

verifly-email Billing API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Verifly API key) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Use 'Authorization: Bearer vfyourapikey'. Get a key with no human via POST /api/v1/autonomous/register. Never expose API keys in prompts, logs, screenshots, cl…

Paths & Operations 4

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

Billing 4

Credit packages and Stripe / crypto checkout. Agent-native crypto pay.

GET
/api/v1/billing
List credit packages or payment history
getBilling 1 param → 200401
POST
/api/v1/billing
Create a checkout to buy credits (Stripe or crypto)
createCheckout body → 200400401500
POST
/api/checkout
Create a Stripe checkout session (API key or session)
createStripeCheckout body → 200400401500
POST
/api/checkout/crypto
Create a crypto (Plisio) checkout (API key or session)
createCryptoCheckout body → 200400401500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are CryptoCheckoutResult (10 properties), SimpleCryptoResult (10 properties), StripeCheckoutResult (6 properties), BillingPackage (6 properties). Each schema is shown below with its type and property counts.

CheckoutRequest
object
4 properties 1 required
SimpleCryptoResult
object
10 properties 3 required
PackagesResult
object
2 properties 2 required
ErrorResult
object
2 properties 2 required
SimpleStripeResult
object
5 properties 2 required
HistoryResult
object
2 properties 2 required
BillingPackage
object
6 properties 5 required
SimpleCheckoutRequest
object
2 properties 1 required
StripeCheckoutResult
object
6 properties 2 required
SimpleCryptoRequest
object
3 properties 1 required
PackageRef
object
4 properties
CryptoCheckoutResult
object
10 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

verifly-email-billing-api-openapi.yml Raw ↑

Other APIs verifly-email publishes across the network.

verifly-email Account API
verifly-email Clean API
verifly-email Extract API
verifly-email Files API
verifly-email Jobs API
verifly-email List Cleaning API
verifly-email Onboarding API
verifly-email Tools API
verifly-email Verification API
verifly-email Verify API
Where this information came from

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