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

Redocly Scout Agent API

The Scout agent is the self-hosted worker half of Scout, deployed inside the customer's own infrastructure (Redocly documents an AWS ECS task definition). Its API is small and operational: a health check plus two webhook receivers that accept GitHub and GitLab events, authenticated by the x-hub-signature-256 and x-gitlab-token signature headers respectively. Errors are RFC 9457 problem documents and the 500 problem carries an `event` member naming the incoming webhook event.

Redocly Scout Agent API is one of 12 APIs that Redocly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Discovery, Webhook, and Self-Hosted. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 operations across 3 paths, organized into 2 resource areas, and defines 37 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, {host}.

3 operations 3 paths 37 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
http://{host}
Authentication
API Key, API Key
License
Terms of Service
Resource Areas
2

Authentication & Security 2

Redocly Scout Agent API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-hub-signature-256 (GithubApiKey). An API key is passed in the header as x-gitlab-token (GitlabApiKey).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. They span 2 resource areas: Health, Webhooks. Each is listed below with its method, path, parameters, and response codes.

Health 1

Operations related to health checks.

GET
/health
Get health status
health → 200400500
Webhooks 2

Operations related to incoming git webhooks.

POST
/webhooks/github
Create GitHub webhook event
processGithubWebhook body → 200401500
POST
/webhooks/gitlab
Create GitLab webhook event
processGitlabWebhook body → 200401500

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are repository (90 properties), pull-request (48 properties), merge-request-details (22 properties), user (20 properties). Each schema is shown below with its type and property counts.

Health
object
1 property 1 required
committer
object
Metaproperties for Git author/committer information.
4 properties 2 required
commit
object
11 properties 11 required
user
object
20 properties 18 required
license
object
5 properties 5 required
repository
object
A git repository.
90 properties 76 required
installation-lite
object
Installation.
2 properties 2 required
organization
object
13 properties 12 required
push
object
15 properties 13 required
team
object
Groups of organization members that gives permissions on specified. repositories.
12 properties 11 required
label
object
7 properties 7 required
milestone
object
A collection of related issues and pull requests.
16 properties 16 required
link
object
1 property 1 required
author-association
string
How the author is associated with the repository.
auto-merge
object
The status of auto merging a pull request.
4 properties 4 required
pull-request
object
48 properties 48 required
pull-request-opened
object
7 properties 5 required
pull-request-reopened
object
7 properties 5 required
pull-request-synchronize
object
9 properties 7 required
WebhookResponse
object
3 properties 1 required
project
object
GitLab Project details.
15 properties 15 required
repository-2
object
GitLab repository details.
9 properties 7 required
author
object
Author details.
2 properties 2 required
commit-2
object
Commit details.
8 properties 9 required
push-2
object
15 properties 15 required
user-2
object
3 properties 3 required
source
object
Merge request source details.
14 properties 14 required
commit-flat
object
Flattened commit details.
6 properties 6 required
merge-request-details
object
Merge request details.
22 properties 22 required
label-2
object
GitLab label details.
9 properties 10 required
updated-by-id
object
2 properties 2 required
updated-at
object
2 properties 2 required
labels
object
Object specifying labels changes.
2 properties 2 required
changes
object
Object containing merge request change details.
3 properties 3 required
merge-request-open
object
7 properties 7 required
merge-request-reopen
object
7 properties 7 required
merge-request-update
object
7 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

redocly-scout-agent-openapi.yaml Raw ↑

Other APIs Redocly publishes across the network.

Redocly Realm
Redocly Reunite
Redocly Revel
Redocly Reef
Redocly Redoc
Redocly CLI
Redocly Respect Monitoring
Arazzo Specification (Redocly Tooling)
Redocly Realm Search API
Redocly Docs MCP Server
Redocly Scout API
Where this information came from

This is an independent, third-party profile of Redocly Scout Agent 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.