Leapcure website screenshot

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 13 more developer resources.

🌐 Visit website 📡 Source on GitHub
36.2/100 thin ▬ flat Agent 51/100 agent ready Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
11 APIs 1 MCP Servers
CompanyClinical TrialsPatient RecruitmentHealthcareBlogContent APIWordPress

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 36.2/100 · thin
Contract Quality 13.1 / 25
Developer Ergonomics 5.7 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 51/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. 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. Want it done for you? Prioritized profiling — $2,500 →

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

MCP Servers 1

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

leapcure-mcp.yml

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
MCPServer
 AgentSkill
AgentSkill
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Lifecycle
Lifecycle
 Conformance
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

Source (apis.yml)

apis.yml Raw ↑ 
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.
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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.20'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- 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
  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
  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
  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
  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
  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
  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:
  - 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
  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
  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:
  - 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: 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