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

Accelsius API Discovery

The WordPress REST route-discovery documents served at accelsius.com/wp-json/ and accelsius.com/wp-json/wp/v2 - the only machine-readable API description documents Accelsius serves. They enumerate 387 routes across 16 namespaces with per-route HTTP methods and full argument schemas, and they are the source every OpenAPI document in this profile was derived from. The root index also advertises the site name, home URL, timezone offset and the application-passwords authorization endpoint. Pass _fields - the untrimmed index is ~285KB.

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

Tagged areas include Discovery, Metadata, Specifications, and WordPress. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 2 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://accelsius.com/wp-json.

2 operations 2 paths 1 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://accelsius.com/wp-json
Authentication
HTTP Basic
Contact
Resource Areas
1

Authentication & Security 1

Accelsius API Discovery declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword).

  • applicationPassword — WordPress Application Passwords over HTTP Basic. Advertised by the site at https://accelsius.com/wp-json/ under authentication.application-passwords. Every ope…

Paths & Operations 2

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

Discovery 2

WordPress REST route-discovery indexes served by accelsius.com.

GET
/
Get the WordPress REST root index
getRootIndex 3 params → 200
GET
/wp/v2
Get the wp/v2 namespace index
getWpV2Index 2 params → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is RouteIndex (13 properties). Each schema is shown below with its type and property counts.

RouteIndex
object
A WordPress REST discovery document.
13 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

accelsius-discovery-api-openapi.yml Raw ↑

Other APIs Accelsius publishes across the network.

Accelsius Resources Content API
Accelsius News API
Accelsius Pages API
Accelsius Media API
Accelsius Search API
Accelsius Categories API
Accelsius Media Folders API
Accelsius Registry API
Accelsius Tags API
Where this information came from

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