Leapcure

Leapcure is a clinical-trial patient recruitment company whose mission is "where patient advocacy meets research" — connecting patients with clinical studies and helping research sites and sponsors reach and enroll participants. Leapcure was surfaced as a portfolio company of 500 Global and added to the API Evangelist network. The company publishes no product API of its own; the single machine-readable surface it operates is the WordPress REST API (wp/v2) behind its blog at blog.leapcure.com, which exposes read access to posts, pages, categories, tags, users, media, comments and search, plus authenticated write operations via WordPress application passwords. This profile was enriched by the API Evangelist pipeline from that live surface.

Leapcure publishes 11 APIs on the APIs.io network, including categories API, comments API, media API, and 8 more. Tagged areas include Company, Clinical Trials, Patient Recruitment, Healthcare, and Blog.

Leapcure’s developer surface includes authentication, engineering blog, and 14 more developer resources.

🌐 Visit website 📡 Source on GitHub

34.0/100 thin ▬ flat Agent 31/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs 1 MCP Servers

Company Clinical Trials Patient Recruitment Healthcare Blog content-api WordPress

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 34.0/100 · thin

Contract Quality 10.4 / 19

Developer Ergonomics 4.9 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.0 / 10

Contract Governance 0.4 / 9

Discoverability 5.7 / 8

Regulatory Posture 4.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 31/100 · agent ready

Machine-Readable Contract 18 / 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 5 / 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

Regulatory Posture applies to this provider. Its tags matched the Health 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

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 github.com/api-evangelist/leapcure: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 11

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

Leapcure categories API

The categories API from Leapcure — 2 operation(s) for categories.

Leapcure comments API

The comments API from Leapcure — 2 operation(s) for comments.

Leapcure media API

The media API from Leapcure — 6 operation(s) for media.

Leapcure pages API

The pages API from Leapcure — 6 operation(s) for pages.

Leapcure posts API

The posts API from Leapcure — 6 operation(s) for posts.

Leapcure search API

The search API from Leapcure — 1 operation(s) for search.

Leapcure statuses API

The statuses API from Leapcure — 2 operation(s) for statuses.

Leapcure tags API

The tags API from Leapcure — 2 operation(s) for tags.

Leapcure taxonomies API

The taxonomies API from Leapcure — 2 operation(s) for taxonomies.

Leapcure types API

The types API from Leapcure — 2 operation(s) for types.

Leapcure users API

The users API from Leapcure — 6 operation(s) for users.

Scroll for all 11

Open Collections 12

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories comments API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories media API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories pages API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories posts API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories search API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories statuses API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories tags API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories taxonomies API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories types API

OPEN COLLECTION

Leapcure Blog Content API (WordPress REST API) categories users API

OPEN COLLECTION

Scroll for all 12

MCP Servers 1

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

Leapcure MCP Server

MCP SERVER

Security Posture 2

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

Leapcure Authentication

http · 1 scheme

SECURITY

Leapcure Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

AgentSkill

AgentSkill

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Lifecycle

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: leapcure
name: Leapcure
description: Leapcure is a clinical-trial patient recruitment company whose mission is "where patient advocacy meets research"
  — connecting patients with clinical studies and helping research sites and sponsors reach and enroll participants. Leapcure
  was surfaced as a portfolio company of 500 Global and added to the API Evangelist network. The company publishes no product
  API of its own; the single machine-readable surface it operates is the WordPress REST API (wp/v2) behind its blog at blog.leapcure.com,
  which exposes read access to posts, pages, categories, tags, users, media, comments and search, plus authenticated write
  operations via WordPress application passwords. This profile was enriched by the API Evangelist pipeline from that live
  surface.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - 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-09-03'
  method: derived
image: https://blog.leapcure.com/wp-content/uploads/2022/10/cropped-logo.png
url: https://raw.githubusercontent.com/api-evangelist/leapcure/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Clinical Trials
- Patient Recruitment
- Healthcare
- Blog
- content-api
- WordPress
tags_raw:
- Company
- Clinical Trials
- Patient Recruitment
- Healthcare
- Blog
- Content API
- WordPress
apis:
- aid: leapcure:leapcure-categories-api
  name: Leapcure categories API
  description: The categories API from Leapcure — 2 operation(s) for categories.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Categories
  tags_raw:
  - categories
  properties:
  - type: OpenAPI
    url: openapi/leapcure-categories-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-comments-api
  name: Leapcure comments API
  description: The comments API from Leapcure — 2 operation(s) for comments.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Comments
  tags_raw:
  - comments
  properties:
  - type: OpenAPI
    url: openapi/leapcure-comments-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-media-api
  name: Leapcure media API
  description: The media API from Leapcure — 6 operation(s) for media.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Media
  tags_raw:
  - media
  properties:
  - type: OpenAPI
    url: openapi/leapcure-media-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-pages-api
  name: Leapcure pages API
  description: The pages API from Leapcure — 6 operation(s) for pages.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Pages
  tags_raw:
  - pages
  properties:
  - type: OpenAPI
    url: openapi/leapcure-pages-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-posts-api
  name: Leapcure posts API
  description: The posts API from Leapcure — 6 operation(s) for posts.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Posts
  tags_raw:
  - posts
  properties:
  - type: OpenAPI
    url: openapi/leapcure-posts-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-search-api
  name: Leapcure search API
  description: The search API from Leapcure — 1 operation(s) for search.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Search
  tags_raw:
  - search
  properties:
  - type: OpenAPI
    url: openapi/leapcure-search-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-statuses-api
  name: Leapcure statuses API
  description: The statuses API from Leapcure — 2 operation(s) for statuses.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Status
  tags_raw:
  - statuses
  properties:
  - type: OpenAPI
    url: openapi/leapcure-statuses-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-tags-api
  name: Leapcure tags API
  description: The tags API from Leapcure — 2 operation(s) for tags.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Tags
  tags_raw:
  - tags
  properties:
  - type: OpenAPI
    url: openapi/leapcure-tags-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-taxonomies-api
  name: Leapcure taxonomies API
  description: The taxonomies API from Leapcure — 2 operation(s) for taxonomies.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - taxonomies
  properties:
  - type: OpenAPI
    url: openapi/leapcure-taxonomies-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-types-api
  name: Leapcure types API
  description: The types API from Leapcure — 2 operation(s) for types.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - Types
  tags_raw:
  - types
  properties:
  - type: OpenAPI
    url: openapi/leapcure-types-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
- aid: leapcure:leapcure-users-api
  name: Leapcure users API
  description: The users API from Leapcure — 6 operation(s) for users.
  humanURL: https://blog.leapcure.com/wp-json/
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - User
  tags_raw:
  - users
  properties:
  - type: OpenAPI
    url: openapi/leapcure-users-api-openapi.yml
  - type: Documentation
    url: https://blog.leapcure.com/wp-json/
  - type: APIReference
    url: https://developer.wordpress.org/rest-api/reference/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/leapcure-blog-content-overlay.yaml
- type: Authentication
  url: authentication/leapcure-authentication.yml
- type: Conventions
  url: conventions/leapcure-conventions.yml
- type: ErrorCatalog
  url: errors/leapcure-problem-types.yml
- type: DataModel
  url: data-model/leapcure-data-model.yml
- type: Lifecycle
  url: lifecycle/leapcure-lifecycle.yml
- type: Conformance
  url: conformance/leapcure-conformance.yml
- type: MCPServer
  url: mcp/leapcure-mcp.yml
- type: AgentSkill
  url: skills/leapcure-browse-blog-content.md
- type: AgentSkill
  url: skills/leapcure-search-content.md
- type: LLMsTxt
  url: llms/leapcure-llms.txt
- type: DomainSecurity
  url: security/leapcure-domain-security.yml
- type: Website
  url: https://leapcure.com
- type: Blog
  url: https://blog.leapcure.com
- type: PrivacyPolicy
  url: https://leapcure.com/privacy-policy
- type: TermsOfService
  url: https://leapcure.com/terms-of-service
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 9
  pass: local-v1

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/leapcure"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.