iECURE
iECURE is a clinical-stage genetic medicines company developing variant-agnostic, in vivo targeted gene insertion therapies for rare, life-threatening inherited metabolic diseases, with an initial focus on urea cycle disorders and other neurometabolic conditions of the liver. The company takes its name from iecur, the Latin word for liver, and was founded on the translational gene therapy research of James M. Wilson, M.D., Ph.D., advancing its pipeline in partnership with the University of Pennsylvania Gene Therapy Program. Its lead candidate, ECUR-506, pairs a dual-AAV delivery approach with Precision BioSciences' ARCUS nuclease to insert a functional copy of the OTC gene into the genome of infants with neonatal-onset ornithine transcarbamylase deficiency; it is in the OTC-HOPE study and has received FDA Orphan Drug, Rare Pediatric Disease, Fast Track and RMAT designations plus EU orphan designation, with clinical trial clearances in the United States, United Kingdom, Australia and the EU. Discovery-stage programs target citrullinemia type 1 and phenylketonuria. iECURE has raised roughly $115 million across a $50 million Series A in 2021 and a $65 million Series A-1 in 2022 from Versant Ventures, OrbiMed, Novo Holdings, the Qatar Investment Authority, LYFE Capital and Double Point Ventures. iECURE runs no developer program and publishes no product API, developer portal or API documentation. The only machine-readable surface reachable without credentials is the WordPress REST content API behind iecure.com, catalogued here.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles iECURE the way a machine reads it — 14 machine-readable artifacts across 10 APIs, 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 — iECURE scores 35.2/100 (thin), with a separate agent-readiness read of 38/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.
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.
Kin Score
How this is scored →scored 2026-08-24 · rubric v0.12.1
Put this on your own site. The badge is drawn live from iECURE'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/iecure/"
title="iECURE on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/iecure.svg"
alt="iECURE Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/iecure/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/iecure/"
title="iECURE on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/iecure/card.svg"
alt="iECURE 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 iECURE
Each block below is one kind of artifact we hold for iECURE. 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 10
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.
iECURE Discovery API
Route, content-type, taxonomy and status discovery documents for the iECURE WordPress REST deployment. Ten namespaces and 351 routes are registered; only these discovery documen...
iECURE Posts API
The iECURE news archive - press releases, media coverage, awards and scientific publications/presentations. 60 published posts at harvest time across six categories.
iECURE Pages API
Corporate pages - About, Approach, Programs, Careers, Contact, News, Terms of Service, Privacy Notice, Cookie Notice, Expanded Access Policy, Social Media Community Guidelines a...
iECURE Media API
The media library backing the site - 226 attachments at harvest time, including the corporate logo, pipeline artwork and leadership headshots.
iECURE Taxonomy API
Categories and tags. Six news categories are registered (news, press release, in the news, awards, pubs & pres, Uncategorized); the post_tag taxonomy is registered but empty.
iECURE Team API
The `portfolio` custom post type as deployed by iECURE, which carries team members rather than portfolio work - 35 items at harvest time, classified by the portfolio_entries tax...
iECURE Search API
Cross-content search across every published object on iecure.com. 64 objects were addressable at harvest time.
iECURE Authors API
Author directory. Anonymously readable on this deployment - unusually, since most WordPress sites gate it - returning the two accounts that have published content.
iECURE Comments API
Comment collection. Registered and anonymously reachable, but empty - no post on this deployment carries comments.
iECURE oEmbed API
oEmbed 1.0 provider endpoint for iecure.com URLs, returning JSON or XML rich/link responses.
Scroll within the panel for all 10 ·
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.
Iecure Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Iecure Rate Limits
RATE LIMITSSecurity 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.
Resources
Every other property we hold for iECURE — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/iecure · machine-readable index on apis.io
This is an independent, third-party profile of iECURE, 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.