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
Pexafy

Pexafy Usage API

Quota counters.

Documentation Provider Profile APIs.io OpenAPI GitHub

Pexafy Usage API is one of 5 APIs that Pexafy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Usage. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and pricing.

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

Requests are made against 2 base URLs: https://api.pexafy.com/api/v1, https://api.pexafy.com.

5 operations 5 paths 12 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.pexafy.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Pexafy Usage API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (apiKey). An API key is passed in the header as x-api-key (ApiKeyAuth).

  • apiKey — Send the key as a bearer token. Keys carry scopes; a read scoped key gets a 403 on anything under /collections.
  • ApiKeyAuth — Pass your Pexafy API key in this header. Get your API key at [pexafy.com/dashboard/api-keys/create](https://pexafy.com/dashboard/api-keys/create/).

Paths & Operations 5

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

usage 5

Quota counters.

GET
/usage
Quota counters for the current period
getUsage → 200401429
GET
/api/v1/usage
Current month usage
get_usage_api_v1_usage_get → 200422
GET
/api/v1/usage/daily
Daily usage history
get_daily_usage_api_v1_usage_daily_get 1 param → 200422
GET
/api/v1/usage/monthly
Monthly usage history
get_monthly_usage_api_v1_usage_monthly_get 1 param → 200422
GET
/api/v1/usage/by-key
Usage by API key
get_usage_by_key_api_v1_usage_by_key_get → 200422

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Usage (7 properties), UsageResponse (4 properties), UsageByKeyResponse (4 properties), DailyUsageResponse (4 properties). Each schema is shown below with its type and property counts.

Meta
object
2 properties
ErrorEnvelope
object
Every failure uses this shape, whatever the status code.
2 properties 2 required
UsageEnvelope
object
3 properties 2 required
Usage
object
Quota counters for the calling key's account.
7 properties
Meta_2
object
2 properties
UsageByKeyResponse
object
4 properties
UsageResponse
object
4 properties
MonthlyUsageResponse
object
4 properties
DailyUsageResponse
object
4 properties
HTTPValidationError
object
1 property
ApiError
object
3 properties 2 required
ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pexafy-usage-api-openapi.yml Raw ↑

Other APIs Pexafy publishes across the network.

Pexafy Collections API
AE Profile APIs.io
Pexafy Facets API
AE Profile APIs.io
Pexafy Photos API
AE Profile APIs.io
Pexafy Search API
AE Profile APIs.io
#Usage
← Back to P APIs
API Details
ID
pexafy:pexafy-usage-api
Base URL
https://api.pexafy.com
Docs
https://docs.pexafy.com
Provider
Pexafy
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=pexafy-usage-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/pexafy-usage-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 Pexafy Usage 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.