amicus-therapeutics
Amicus Therapeutics is a global rare disease biotechnology company focused on discovering, developing, and commercializing medicines for people living with genetically defined conditions. Founded in 2002 and headquartered in Princeton, New Jersey, Amicus markets two approved therapies: Galafold (migalastat) — the first and only oral therapy for adults with Fabry disease who have an amenable GLA variant, approved by the European Commission in May 2016 — and the two-component Pombiliti (cipaglucosidase alfa-atga) + Opfolda (miglustat) enzyme replacement / stabilizer combination for adults with late-onset Pompe disease. Amicus operates wholly owned subsidiaries in Australia, Canada, France, Germany, Italy, Japan, the Netherlands, Spain, Switzerland, and the United Kingdom. BioMarin Pharmaceutical Inc. agreed to acquire Amicus in December 2025 for $4.8 billion; the acquisition completed on April 27, 2026 and Amicus now operates as a wholly owned subsidiary of BioMarin, having previously traded on NASDAQ under the ticker FOLD. The company maintains no publicly documented commercial developer APIs, SDKs, or GitHub organization; its digital surface is composed of corporate, product, patient-support, and clinical-trial websites.
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 amicus-therapeutics the way a machine reads it — 10 machine-readable artifacts, 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 — amicus-therapeutics scores 20.7/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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.
How we profile amicus-therapeutics
Each block below is one kind of artifact we hold for amicus-therapeutics. 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.
Semantic 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.
Amicus Therapeutics Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
amicus-therapeutics API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Amicus Clinical Trial
JSON SCHEMAAmicus Medicine
JSON SCHEMAJSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amicus Clinical Trial Structure
JSON STRUCTUREAmicus Medicine Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
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 amicus-therapeutics — 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.
Get Started 1
Portal, sign-up, and the first successful call
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Company 5
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/amicus-therapeutics · machine-readable index on apis.io