Allotex
Allotex Inc. is an ophthalmic biologics and medical device company headquartered at 27-43 Wormwood Street, Suite 160, Boston, Massachusetts, with European operations. Founded by Drs. Michael Mrochen and David Muller, it develops tissue-addition therapies for presbyopia, hyperopia and myopia. Its lead product, the Allotex TransForm corneal allograft, is a 20-micron-thick, 2.75mm-diameter disc of acellular human donor cornea shaped with an excimer laser under OCT measurement, sterilised by electron-beam radiation and shelf-stable for two years, implanted beneath a femtosecond-laser flap or on the corneal surface where it integrates with the patient's own cornea as, in the company's framing, a permanent living contact lens. Because the implant adds biocompatible human tissue rather than ablating tissue or inserting a synthetic inlay, the company positions the procedure as removable and replaceable. Allotex has run TransForm clinical trials for hyperopia and for intrastromal and sub-epithelial presbyopia correction, submitted an IDE to the U.S. FDA in May 2025 for its Allo-1 corneal implant, received FDA IDE approval for a U.S. presbyopia study in January 2026, and partners with Daicel High Performance Polymers and its TOPAS Advanced Polymers business on next-generation allograft technology. Allotex runs no developer program and publishes no product API, no developer portal, no API reference, no SDKs and no status page. The only machine-readable surface reachable without credentials is the WordPress REST content API behind us.allotex.com, catalogued here.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Allotex the way a machine reads it — 17 machine-readable artifacts across 6 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 — Allotex scores 22.2/100 (emerging), with a separate agent-readiness read of 41/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-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Allotex'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/allotex/"
title="Allotex on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/allotex.svg"
alt="Allotex Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/allotex/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/allotex/"
title="Allotex on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/allotex/card.svg"
alt="Allotex 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 Allotex
Each block below is one kind of artifact we hold for Allotex. 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 6
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.
Allotex Content API
Pages, posts, reusable blocks and navigation.
Allotex Discovery API
Route index, cross-content search and the oEmbed provider endpoint.
Allotex Identity API
Public author records.
Allotex Media API
The 218-item media library and its size variants.
Allotex Schema API
Registered post types, taxonomies and statuses.
Allotex Taxonomy API
Categories and tags.
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAllotex Content API
OPEN COLLECTIONAllotex Content Discovery API
OPEN COLLECTIONAllotex Content Identity API
OPEN COLLECTIONAllotex Content Media API
OPEN COLLECTIONAllotex Content Schema API
OPEN COLLECTIONAllotex Content Taxonomy API
OPEN COLLECTIONScroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
allotex-mcp.yml
MCP SERVERSemantic 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.
Allotex Organization Context
JSON-LDSecurity 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 Allotex — 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.
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
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 1
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 11
Properties that don't map to a standard resource type
Scroll within the panel for all 11 ·
← All providers · Data indexed from github.com/api-evangelist/allotex · machine-readable index on apis.io
This is an independent, third-party profile of Allotex, 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.