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

xpoz-ai Account API

Access keys, plan, and usage of the signed-in user.

xpoz-ai Account API is one of 10 APIs that xpoz-ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

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

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

Requests are made against a single base URL, /.

6 operations 5 paths 10 schemas 4 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://api.xpoz.ai
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

xpoz-ai Account API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (AccessKey). It accepts HTTP bearer tokens (JWT) (UserSession).

  • AccessKey — XPOZ API access key, created from the dashboard or POST /api/tokens. Send as Authorization: Bearer .
  • UserSession — Descope session JWT of a logged-in dashboard user. Send as Authorization: Bearer .

Paths & Operations 6

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

Account 6

Access keys, plan, and usage of the signed-in user.

GET
/api/tokens
List access keys
getTokens → 200401500
POST
/api/tokens
Create an access key
postTokens body → 200400401500
POST
/api/tokens/rotate
Rotate access key
postTokensRotate → 200400401500
GET
/api/plan
Get current plan
getPlan → 200401500
GET
/api/usage
Get usage
getUsage → 200401500
GET
/api/usage-history
Get usage history
getUsageHistory 2 params → 200400401500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are AccessKeyRecord (15 properties), Plan (10 properties), PlanFeatures (8 properties), UsageHistory (5 properties). Each schema is shown below with its type and property counts.

SimpleError
object
2 properties 2 required
LegacyFailure
object
3 properties 2 required
AccessKeyCreated
object
4 properties 4 required
UsageHistory
object
5 properties 5 required
Usage
object
4 properties 4 required
Plan
object
10 properties 5 required
AccessKeyRecord
object
15 properties
UsageBucket
object
5 properties 5 required
MessageError
object
1 property 1 required
PlanFeatures
object
8 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xpoz-ai-account-api-openapi.yml Raw ↑

Other APIs xpoz-ai publishes across the network.

xpoz-ai Billing API
xpoz-ai Crawl Settings API
xpoz-ai Instagram (live) API
xpoz-ai Operations API
xpoz-ai Platform API
xpoz-ai Reddit (live) API
xpoz-ai System Status API
xpoz-ai TikTok (live) API
xpoz-ai Twitter (live) API
Where this information came from

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