Derive
Derive is an open‑source, self‑hostable platform where teams and AI agents publish, review, and revise work. It provides a collaborative space for AI artifacts, emphasizing openness, community contribution, and flexible deployment. The service aims to streamline AI workflow management and artifact sharing across organizations.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Derive the way a machine reads it — 41 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Derive scores 44.1/100 (developing), with a separate agent-readiness read of 40/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
the company serves an API surface but requires credentials before any description of it can be read
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Derive's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://derive.to/openapi.json→ HTTPhttps://app.derive.to/openapi.json→ HTTPhttps://derive.to/mcp→ HTTP 401https://app.derive.to/mcp→ HTTP 401https://derive.to/→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-11-06 · rubric v0.27.0
Put this on your own site. The badge is drawn live from Derive's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/derive-to/"
title="Derive on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/derive-to.svg"
alt="Derive Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/derive-to/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/derive-to/"
title="Derive on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/derive-to/card.svg"
alt="Derive Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Derive
Each block below is one kind of artifact we hold for Derive. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Derive Accounts API
Model accounts: the credential a machine uses to call a model. Write-only.
Derive Activity API
The Activity API from Derive — 1 operation(s) for activity.
Derive Agents API
Agents: named workers with instructions, a machine, and what they can reach. Also the OAuth agents a user has authorized.
Derive Analytics API
Aggregate view statistics for an artifact.
Derive Artifacts API
Documents (files and bundles): browse, publish, version, restore, and control access.
Derive Assets API
Standalone binary image assets referenced from bundles.
Derive Collections API
Shareable groups of artifacts, each with its own members.
Derive Comments API
Threaded, anchored comments with reactions, edits, and resolution.
Derive Contexts API
Papers imported from arXiv: each is a read-only Context whose artifact is the paper.
Derive Domains API
Custom domains and vanity subdomains bound to artifacts.
Derive Exports API
The Exports API from Derive — 1 operation(s) for exports.
Derive Favorites API
The caller's favorited artifacts.
Derive Folders API
The Folders API from Derive — 3 operation(s) for folders.
Derive Follows API
Follow people to build the activity feed.
Derive GitHub API
Install-backed GitHub access for reading pull requests and posting comments.
Derive Jobs API
One unit of agent work: someone asked, a schedule fired, or a graph opened a node. People ask, follow, answer, cancel, and retry; runners pull and report.
Derive Moderation API
Abuse reports and takedown / reinstate actions.
Derive Notifications API
The caller's in-app notification feed.
Derive OAuth API
OAuth 2.1 authorization-server endpoints and sign-in capabilities.
Derive Realtime API
Live presence and cursor sharing on an artifact.
Derive Review API
Review rounds on an artifact: request a review, or send it back with a note.
Derive Session API
Identity: the signed-in user, public profiles, and the people directory.
Derive Sharing API
Per-artifact collaborator roles (shares) layered over the workspace baseline.
Derive Slack API
Slack connection status and integration toggles.
Derive Templates API
The Templates API from Derive — 6 operation(s) for templates.
Derive Vitals API
Client-reported web-vitals ingestion.
Derive Webhooks API
Outgoing webhooks and their delivery log.
Derive Workspace API
The workspace itself: members, settings, invitations, and switching.
Scroll within the panel for all 28 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Derive To Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Derive To Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Derive API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Agent
JSON SCHEMAArtifact
JSON SCHEMACollection
JSON SCHEMAComment
JSON SCHEMAContextAnalysisInfo
JSON SCHEMAJob
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Derive — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/derive-to · machine-readable index on apis.io
This is an independent, third-party profile of Derive, 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.