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

OpenRelay Registry Credentials API

Private container-registry credentials for pulling images.

OpenRelay Registry Credentials API is one of 19 APIs that OpenRelay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against 3 base URLs: https://api.openrelay.inc, https://api.beta.openrelay.inc, http://localhost:8083.

3 operations 3 paths 3 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.openrelay.inc
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

OpenRelay Registry Credentials API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey).

  • apiKey — OpenRelay API key. Send it as Authorization: Bearer vl….

Paths & Operations 3

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

Registry Credentials 3

Private container-registry credentials for pulling images.

GET
/v1/orgs/{orgId}/registry-credentials
List an org's registry credentials (no secrets)
listOrgRegistryCredentials 1 param → 200401403
POST
/v1/orgs/{orgId}/registry-credentials/create
Create a registry credential (credentials stored encrypted)
createOrgRegistryCredential 1 param body → 200400401403
DELETE
/v1/orgs/{orgId}/registry-credentials/{id}
Delete a registry credential
deleteOrgRegistryCredential 2 params → 204401403

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are RegistryCredentialSummary (5 properties), CreateRegistryCredentialRequest (4 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties 1 required
RegistryCredentialSummary
object
5 properties 5 required
CreateRegistryCredentialRequest
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openrelay-registry-credentials-api-openapi.yml Raw ↑

Other APIs OpenRelay publishes across the network.

OpenRelay Inference API
OpenRelay Account API
OpenRelay API Keys API
OpenRelay Batches API
OpenRelay Billing API
OpenRelay Catalog API
OpenRelay Clusters API
OpenRelay Files API
OpenRelay Internal API
OpenRelay Organizations API
OpenRelay Provider API
OpenRelay Runners API
Where this information came from

This is an independent, third-party profile of OpenRelay Registry Credentials 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.