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

Application Research Components API

Operations for managing component descriptors

Application Research Components API is one of 36 APIs that Application Research publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 5 JSON Schema definitions.

Tagged areas include Components. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, code examples, and 5 JSON Schemas.

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

Requests are made against 2 base URLs: https://api.ocm.example.com/v1, https://staging.ocm.example.com/v1.

9 operations 5 paths 29 schemas 1 DELETE4 GET3 POST1 PUT

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.score.dev/v1
Authentication
HTTP Bearer, API Key, OpenID Connect
License
Resource Areas
1

Authentication & Security 3

Application Research Components API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as X-API-Key (apiKey). It supports OpenID Connect (oidc) discovered at https://auth.ocm.example.com/.well-known/openid-configuration. By default, every request must be authenticated.

  • bearerAuth — JWT-based authentication
  • apiKey — API key authentication
  • oidc — OpenID Connect authentication

Paths & Operations 9

Across 5 paths, the API surfaces 9 operations — 1 DELETE, 4 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Components 9

Operations for managing component descriptors

GET
/components
Application Research List component descriptors
listComponents 3 params → 200400500
POST
/components
Application Research Create a component descriptor
createComponent body → 201400409500
GET
/components/{name}
Application Research Get a component descriptor by name
getComponent 2 params → 200404500
PUT
/components/{name}
Application Research Update a component descriptor
updateComponent 1 param body → 200400404500
DELETE
/components/{name}
Application Research Delete a component descriptor
deleteComponent 2 params → 204404500
GET
/components/{name}/versions
Application Research List all versions of a component
listComponentVersions 1 param → 200404500
GET
/components/{name}/references
Application Research List component references
listComponentReferences 2 params → 200404500
POST
/components/{name}/references
Application Research Add a component reference
addComponentReference 2 params body → 201400404500
POST
/transfer
Application Research Transfer components between repositories
transferComponents body → 202400500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are Resource (10 properties), Component (9 properties), Source (7 properties), ComponentReference (6 properties). Each schema is shown below with its type and property counts.

RepositoryContext
object
Repository context for component storage
3 properties 1 required
ElementName
string
Element name for resources and sources
TransferResult
object
Result of transfer operation
4 properties
TransferRequest
object
Request to transfer components
4 properties 2 required
NestedComponentDigests
object
Digests for nested components
4 properties 2 required
Label
object
A label with name-value pair
5 properties 2 required
Source
object
Component source
7 properties 2 required
Version
string
Semantic version string
Input
object
Input specification for local resources
1 property 1 required
ComponentDescriptorListResponse
object
4 properties
Provider
object
Component provider information
2 properties 1 required
ComponentReference
object
Reference to another component
6 properties 3 required
Resource
object
Component resource
10 properties 2 required
DigestSpec
object
Cryptographic digest specification
3 properties 3 required
VersionListResponse
object
2 properties
Component
object
Component definition
9 properties 3 required
ComponentDescriptor
object
Complete component descriptor
4 properties 2 required
SrcRef
object
Reference to a component-local source
2 properties
ComponentName
string
Fully qualified component name
ComponentReferenceListResponse
array
Meta
object
Component descriptor metadata
1 property 1 required
Signature
object
Component signature
3 properties 2 required
SignatureSpec
object
Signature specification
3 properties 3 required
Error
object
Error response
3 properties 2 required
Merge
object
2 properties
NestedDigestSpec
object
4 properties 1 required
Access
object
Access specification for resources and sources
1 property 1 required
Labels
array
IdentityAttribute
object
Identity attributes for element identification

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

application-research-components-api-openapi.yml Raw ↑

Other APIs Application Research publishes across the network.

Application Research API Resources API
Application Research Applications API
Application Research Bundles API
Application Research Capabilities API
Application Research Claim Results API
Application Research Claims API
Application Research Configurations API
Application Research Consumption Bundles API
Application Research Containers API
Application Research Credentials API
Application Research Dapr API
Application Research Data Products API
Where this information came from

This is an independent, third-party profile of Application Research Components 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.