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

AEE Site Index API

Public, unauthenticated read access to the site-wide index surfaces behind a-fsw.com — cross-content search, the 232-item media library of equipment photography and diagrams, and the content-type and post-status registries — via the WordPress core REST API. Verified live on 2026-09-10.

AEE Site Index API is one of 3 APIs that Aerospace Engineering Equipment publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Search, Media, and Content. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, organized into 3 resource areas, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version wp/v2.

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

5 operations 5 paths 5 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://a-fsw.com/wp-json
Resource Areas
3

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. They span 3 resource areas: Search, Media, Registries. Each is listed below with its method, path, parameters, and response codes.

Search 1

Cross-content search across AEE posts, pages and products.

GET
/wp/v2/search
Search site content
search 8 params → 200400401
Media 2

The AEE media library — product photography, equipment diagrams and application imagery.

GET
/wp/v2/media
List media
listMedia 23 params → 200400401
GET
/wp/v2/media/{id}
Get a media item
getMediaItem 4 params → 200400401404
Registries 2

Content-type and post-status registries describing the shape of the AEE content surface.

GET
/wp/v2/types
List content types
listContentTypes 1 param → 200400401
GET
/wp/v2/statuses
List post statuses
listPostStatuses 1 param → 200400401

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are MediaItem (29 properties), ContentType (11 properties), PostStatus (5 properties), SearchResult (5 properties). Each schema is shown below with its type and property counts.

Error
object
WordPress REST API error envelope. Not RFC 9457 problem+json; served as application/json.
3 properties 2 required
SearchResult
object
A single cross-content search hit.
5 properties
MediaItem
object
A single media library attachment.
29 properties
ContentType
object
A registered content type.
11 properties
PostStatus
object
A registered post status.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aerospaceengineeringequipmentco-site-api-openapi.yml Raw ↑

Other APIs Aerospace Engineering Equipment publishes across the network.

AEE Products API
AEE Content API
Where this information came from

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