Runlayer

Runlayer (operated by Anysource Inc.) is an enterprise AI control plane and enablement layer for AI agents. It sits as a governed layer between the AI clients employees already use (Claude, Cursor, ChatGPT, Codex, GitHub Copilot, VS Code, Windsurf — 300+ clients) and company systems, connecting them to 18,000+ MCP servers with identity, policy enforcement, runtime security (Runlayer Guard), and audit logging on every request. The platform pairs an MCP gateway, an agent builder (Runlayer Agents), a governed skills/plugins registry (Runlayer Catalog), agent IAM, shadow-AI discovery (Runlayer Watch), and observability. Developers get a tenant-scoped REST Management API (/api/v1), a first-party CLI, Python packages, an OAuth broker, and a platform self-MCP (Runlayer MCP). Backed by a $30M Series A from Felicis and Khosla Ventures (June 2026).

Runlayer is listed with 1 API on the APIs.io network. Tagged areas include Company, Artificial Intelligence, AI Agents, MCP, and API Gateway.

Runlayer’s developer surface includes documentation, API reference, getting-started guide, engineering blog, signup flow, CLI, authentication, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.9/100 thin ▬ flat Agent 9/100 agent aware Front door AI 6/6 dominant Heartbeat 70/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers

Company Artificial Intelligence AI Agents MCP API Gateway Security Governance Identity Observability Enterprise

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 32.9/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 9.7 / 17

Access Clarity 8.5 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 4.1 / 15

Agent readiness — 9/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/runlayer/"><img src="https://apis.io/badge/runlayer/card.svg" alt="Runlayer on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Operational Transparency scores 2.6 — up to +12.7 composite points
Access Clarity scores 50.0 — up to +10.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/runlayer/apis.yml: open an issue on github.com/api-evangelist/runlayer to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Runlayer Management API

Tenant-scoped RESTful API for programmatic management of an organization's MCP infrastructure — MCP server/connector management, user operations, audit logs, and analytics. Auth...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Runlayer MCP

First-party "platform self-MCP" — a hosted Runlayer MCP server that lets an assistant query and manage Runlayer itself (audit logs, analytics, server inventory, policies, plugin...

MCP SERVER

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Runlayer Authentication

apiKey/oauth2/openIdConnect · 4 schemes

SECURITY

Runlayer Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Runlayer Trust Center

SOC 2, HIPAA, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

Conformance

ErrorCatalog

Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 4

Authentication, authorization, and security posture

Authentication

Compliance

TrustCenter

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: runlayer
name: Runlayer
description: Runlayer (operated by Anysource Inc.) is an enterprise AI control plane and enablement layer for AI agents. It
  sits as a governed layer between the AI clients employees already use (Claude, Cursor, ChatGPT, Codex, GitHub Copilot, VS
  Code, Windsurf — 300+ clients) and company systems, connecting them to 18,000+ MCP servers with identity, policy enforcement,
  runtime security (Runlayer Guard), and audit logging on every request. The platform pairs an MCP gateway, an agent builder
  (Runlayer Agents), a governed skills/plugins registry (Runlayer Catalog), agent IAM, shadow-AI discovery (Runlayer Watch),
  and observability. Developers get a tenant-scoped REST Management API (/api/v1), a first-party CLI, Python packages, an
  OAuth broker, and a platform self-MCP (Runlayer MCP). Backed by a $30M Series A from Felicis and Khosla Ventures (June 2026).
url: https://raw.githubusercontent.com/api-evangelist/runlayer/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.runlayer.com/apple-touch-icon.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- felicis
- khosla-ventures
x-tier: stub
x-tier-reason: portfolio-lead
x-operated-by: Anysource Inc.
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
x-docs-hosting: vercel
tags:
- Company
- Artificial Intelligence
- AI Agents
- MCP
- API Gateway
- Security
- Governance
- Identity
- Observability
- Enterprise
tags_raw:
- Company
- AI
- AI Agents
- MCP
- Model Context Protocol
- API Gateway
- Security
- Governance
- Identity
- Observability
- Enterprise
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Runlayer Management API
  description: Tenant-scoped RESTful API for programmatic management of an organization's MCP infrastructure — MCP server/connector
    management, user operations, audit logs, and analytics. Authenticated with an x-runlayer-api-key header or an Agent Account
    OAuth token (M2M / RFC 8693 OBO).
  humanURL: https://docs.runlayer.com/platform-api
  baseURL: https://runlayer.com/api/v1
  properties:
  - type: Authentication
    url: authentication/runlayer-authentication.yml
  - type: Conventions
    url: conventions/runlayer-conventions.yml
  - type: ErrorCatalog
    url: errors/runlayer-error-codes.yml
  - type: Lifecycle
    url: lifecycle/runlayer-lifecycle.yml
common:
- type: Website
  url: https://runlayer.com
- type: Documentation
  url: https://docs.runlayer.com
- type: APIReference
  url: https://docs.runlayer.com/platform-api
- type: GettingStarted
  url: https://docs.runlayer.com/quickstart
- type: Blog
  url: https://runlayer.com/blog
- type: GitHubOrganization
  url: https://github.com/runlayer
- type: SignUp
  url: https://runlayer.com/book-a-demo
- type: TermsOfService
  url: https://runlayer.com/terms-of-service
- type: PrivacyPolicy
  url: https://runlayer.com/privacy-policy
- type: LLMsTxt
  url: llms/runlayer-llms.txt
- type: Packages
  url: packages/runlayer-packages.yml
- type: SDKs
  url: packages/runlayer-packages.yml
- type: CLI
  url: cli/runlayer-cli.yml
- type: MCPServer
  url: mcp/runlayer-mcp.yml
- type: Authentication
  url: authentication/runlayer-authentication.yml
- type: Conventions
  url: conventions/runlayer-conventions.yml
- type: Conformance
  url: conformance/runlayer-conformance.yml
- type: Compliance
  url: https://trust.runlayer.com
- type: TrustCenter
  url: security/runlayer-trust-center.yml
- type: DomainSecurity
  url: security/runlayer-domain-security.yml
- type: ErrorCatalog
  url: errors/runlayer-error-codes.yml
- type: Lifecycle
  url: lifecycle/runlayer-lifecycle.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 11
  pass: local-v1

Runlayer API — frequently asked questions

Does Runlayer have an API?

Yes. APIs.io lists 1 API from Runlayer, including Runlayer Management API.

How do I authenticate with the Runlayer API?

Runlayer uses bearer-token authentication (apiKey/oauth2/openIdConnect · 4 schemes). The details are profiled on APIs.io as Runlayer Authentication.

Does Runlayer have an MCP server?

Yes. APIs.io lists 1 MCP server for Runlayer: First-party "platform self-MCP" — a hosted Runlayer MCP server that lets an assistant query and manage Runlayer itself (audit logs, analytics, server inventory, policies, plugins, skills, agents). Dis

Is the Runlayer API ready for AI agents?

Runlayer has a Kin Score of 32.9 out of 100 (thin) and an Agent Readiness score of 8.8 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/runlayer"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/runlayer/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/runlayer/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.