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

APIContext Open API

OpenAPI validation

APIContext Open API is one of 56 APIs that APIContext publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include OpenAPI. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 2 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version v2026-09-02.

Requests are made against the base URL https://client.apimetrics.io.

2 operations 2 paths 8 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2026-09-02
Base URL
https://client.apimetrics.io
Authentication
OAuth 2.0, API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 2

APIContext Open API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 3 scopes. An API key is passed in the header as X-Api-Key (ApiKey).

Paths & Operations 2

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

Open API 2

OpenAPI validation

POST
/api/2/openapi/tag
Tag-Project-For-Openapi
tag-project-for-openapi 4 params → 200422
POST
/api/2/openapi/validate/{result_key_str}deprecated
Validate-Openapi
validate-openapi 2 params → 200422

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are OpenApiFileInfo (7 properties), TagProjectError (5 properties), ValidationError (5 properties), ValidateError (5 properties). Each schema is shown below with its type and property counts.

TagProjectError
object
5 properties 4 required
ValidationError
object
5 properties 3 required
OpenApiFileInfo
object
Per-file validation summary, keyed by file ID in the tagger response.
7 properties 7 required
ValidateResponse
object
3 properties 1 required
ValidateError
object
A single schema-validation failure, as produced by the ajv-backed schema-validator function.
5 properties 3 required
TagProjectResponse
object
5 properties 4 required
HTTPValidationError
object
1 property
TagProjectMatch
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

apicontext-open-api-api-openapi.yml Raw ↑

Other APIs APIContext publishes across the network.

APIContext Schedules API
APIContext Workflows API
APIContext Results API
APIContext Agents API
APIContext Projects API
APIContext Insights API
APIContext Reports API
APIContext Account API
APIContext Account Settings API
APIContext Analytics API
APIContext API Keys API
APIContext API Monitor Statistics API
Where this information came from

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