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

UsageRail API

UsageRail API as documented publicly: 16 operations. Contract generated from the documentation by API Evangelist (2026-11-02); not the provider's own document.

UsageRail API is published by UsageRail on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 16 operations across 15 paths, organized into 7 resource areas, and defines 22 schemas. It is described by OpenAPI 3.1.0, at version 2026-11-02.

Requests are made against a single base URL, https://api.usagerail.com.

16 operations 15 paths 22 schemas 1 DELETE6 GET9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2026-11-02
Base URL
https://api.usagerail.com
Authentication
HTTP Bearer
Resource Areas
7

Authentication & Security 1

UsageRail API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer). By default, every request must be authenticated.

Paths & Operations 16

Across 15 paths, the API surfaces 16 operations — 1 DELETE, 6 GET, 9 POST. They span 7 resource areas: Healthz, Check, Consumers, Generate, Hello, Items, Keys. Each is listed below with its method, path, parameters, and response codes.

Healthz 1
GET
/healthz
Health check endpoint
get_healthz → 200
Check 2
GET
/v1/check
GET /v1/check
get_v1_check → 200
POST
/v1/check
POST /v1/check
post_v1_check body → 201
Consumers 9
POST
/v1/consumers
POST /v1/consumers
post_v1_consumers body → 201
GET
/v1/consumers/{id}
Get a customer
get_v1_consumers_id 1 param → 200
POST
/v1/consumers/{id}/checkout
Checkout
post_v1_consumers_id_checkout 1 param body → 201
POST
/v1/consumers/{id}/claim
Claim an email or external ID
post_v1_consumers_id_claim 1 param body → 201
POST
/v1/consumers/{id}/credits/adjust
Adjust a balance
post_v1_consumers_id_credits_adjust 1 param body → 201
POST
/v1/consumers/{id}/keys
Create a key
post_v1_consumers_id_keys 1 param body → 201
POST
/v1/consumers/{id}/plan
Plans
post_v1_consumers_id_plan 1 param body → 201
POST
/v1/consumers/{id}/portal-link
Portal sign-in links
post_v1_consumers_id_portal_link 1 param body → 201
GET
/v1/consumers/{id}/usage
Usage
get_v1_consumers_id_usage 2 params → 200
Generate 1
POST
/v1/generate
Generate endpoint
post_v1_generate body → 201
Hello 1
GET
/v1/hello
GET /v1/hello
get_v1_hello → 200
Items 1
GET
/v1/items/{id}
Retrieve an item by ID
get_v1_items_id 1 param → 200
Keys 1
DELETE
/v1/keys/{keyId}
Revoke a key
delete_v1_keys_keyId 1 param → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are GetV1ConsumersIdUsageResponse (6 properties), PostV1ConsumersIdCheckoutRequest (5 properties), PostV1ConsumersIdKeysResponse (4 properties), PostV1ConsumersIdPlanRequest (3 properties). Each schema is shown below with its type and property counts.

GetHealthzResponse
object
1 property
PostV1CheckRequest
object
3 properties
PostV1ConsumersRequest
object
2 properties
PostV1ConsumersResponse
object
1 property
GetV1ConsumersIdResponse
object
1 property
PostV1ConsumersIdCheckoutRequest
object
5 properties 3 required
PostV1ConsumersIdCheckoutResponse
object
1 property
PostV1ConsumersIdClaimRequest
object
2 properties
PostV1ConsumersIdClaimResponse
object
1 property
PostV1ConsumersIdCreditsAdjustRequest
object
2 properties 2 required
PostV1ConsumersIdCreditsAdjustResponse
object
1 property
PostV1ConsumersIdKeysRequest
object
1 property
PostV1ConsumersIdKeysResponse
object
4 properties
PostV1ConsumersIdPlanRequest
object
3 properties 1 required
PostV1ConsumersIdPlanResponse
object
2 properties
PostV1ConsumersIdPortalLinkRequest
object
1 property
PostV1ConsumersIdPortalLinkResponse
object
2 properties
GetV1ConsumersIdUsageResponse
object
6 properties
PostV1GenerateRequest
object
1 property
PostV1GenerateResponse
object
1 property
GetV1ItemsIdResponse
object
1 property
DeleteV1KeysKeyidResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

usagerail-openapi-generated.yml Raw ↑
Where this information came from

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