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 Files API

Input and result files for the Batch API (JSONL, up to 200 MB and 50,000 records). Served by the inference endpoint (inference.openrelay.inc).

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

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

This API exposes 5 operations across 5 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.

5 operations 5 paths 3 schemas 2 GET3 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 Files 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 5

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

Files 5

Input and result files for the Batch API (JSONL, up to 200 MB and 50,000 records). Served by the inference endpoint (inference.openrelay.inc).

POST
/v1/files
Upload a JSONL input file for the Batch API
uploadFile body → 200400401404413429
POST
/v1/files/presign
Mint a signed URL for a direct JSONL upload
presignFileUpload body → 200400401404
GET
/v1/files/{id}
Get a file's metadata
getFile 1 param → 200401404
POST
/v1/files/{id}/complete
Register a presigned upload after the PUT succeeds
completeFileUpload 1 param → 200400401404
GET
/v1/files/{id}/content
Download a file's raw JSONL content
getFileContent 1 param → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are FileObject (7 properties), PresignUploadResponse (3 properties), InferenceError (1 property). Each schema is shown below with its type and property counts.

PresignUploadResponse
object
A minted file id and a signed URL for a direct browser upload.
3 properties 3 required
InferenceError
object
Error shape returned by the inference endpoint (OpenAI-compatible).
1 property 1 required
FileObject
object
A file stored for the Batch API (OpenAI-compatible).
7 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openrelay-files-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 Internal API
OpenRelay Organizations API
OpenRelay Provider API
OpenRelay Registry Credentials API
OpenRelay Runners API
Where this information came from

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