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 1 API contract indexed on the APIs.io network. 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 📡 Profile data on GitHub

16.0/100 emerging ▬ flat Agent 18/100 agent aware Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 1 MCP Servers 2 Agent Skills

Company Clinical Trials Patient Recruitment Healthcare Blog content-api WordPress

Kin Score

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

Composite quality — 16.0/100 · emerging

Contract Quality 0.0 / 19

Developer Ergonomics 3.1 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.0 / 10

Contract Governance 0.4 / 9

Discoverability 5.0 / 8

Regulatory Posture 2.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 18/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 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 6 / 6

Protected Resource Metadata 5 / 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 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/.

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/leapcure/"><img src="https://apis.io/badge/leapcure/card.svg" alt="Leapcure 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

7 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
Developer Ergonomics scores 20.8 — up to +15.8 composite points
Access Clarity scores 21.1 — up to +15.8 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/leapcure/apis.yml: open an issue on github.com/api-evangelist/leapcure 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 2

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 (platform)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

APIs 1

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

Leapcure Website (WordPress REST)

The public WordPress REST API (wp-json) of the Leapcure website at blog.leapcure.com: the route index of the site's content management system, catalogued as one site surface rat...

MCP Servers 1

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

Leapcure MCP Server

Remote MCP server at blog.leapcure.com over HTTP.

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Browse Leapcure blog content

AGENT SKILL

Search across the Leapcure blog

AGENT SKILL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Leapcure Blog Content Overlay

2 actions · update · leapcure-blog-content-openapi.yml

DERIVED

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-11-06'
  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:blog-leapcure-com-website-wordpress-rest
  name: Leapcure Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the Leapcure website at blog.leapcure.com: the route index of the
    site''s content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://blog.leapcure.com/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://blog.leapcure.com/wp-json
  x-platform: wordpress
  x-platform-surface: rest
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

Leapcure API — frequently asked questions

Does Leapcure have an API?

Yes. APIs.io lists 1 API from Leapcure, including Leapcure Website (WordPress REST).

How do I authenticate with the Leapcure API?

Leapcure documents its authentication (http · 1 scheme). The details are profiled on APIs.io as Leapcure Authentication.

Does Leapcure have an MCP server?

Yes. APIs.io lists 1 MCP server for Leapcure: Remote MCP server at blog.leapcure.com over HTTP.

Is the Leapcure API ready for AI agents?

Leapcure has a Kin Score of 16.0 out of 100 (emerging) and an Agent Readiness score of 18.2 (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/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"

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.