How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

AggreDyne

AggreDyne, Inc. is a privately held Houston, Texas medical device and in vitro diagnostics manufacturer, founded in 2011 by Edward R. Teitel, MD, JD and Robert C. Hux, CPA, to commercialize the AggreGuide platelet function analyzer. Its flagship product, the AggreGuide A-100, is a benchtop laser light scattering aggregometer that measures platelet aggregation from a single-use disposable cartridge in under five minutes, assessing how well a patient is responding to antiplatelet therapy such as aspirin, clopidogrel, prasugrel and ticagrelor. The company holds three FDA 510(k) clearances under product code JOZ — K122162 (2013), K163274 for the A-100 AA Assay and Instrument (2017), and K181777 for the A-100 ADP assay cartridge (2019) — and its products are CE marked. It sells to hospital laboratories, physician office laboratories in cardiology, endocrinology, neurology and family practice, and regional reference laboratories. AggreDyne is a diagnostic instrument and consumable manufacturer rather than a software or platform business: it has never published a developer program, public API, SDK, or machine-readable API contract, and as of September 2026 its corporate website is offline behind a suspended hosting account.

AggreDyne is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.

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. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

No API surface

Why this profile is thin

AggreDyne sells a benchtop laser light scattering platelet aggregometer and its single-use cartridges — an FDA 510(k) class of physical in vitro diagnostic goods (K122162, K163274, K181777, all product code JOZ), not software — and there is no developer program, GitHub organization (github.com/aggredyne is a hard 404, and a GitHub code search for "aggredyne" returns zero repositories) or integration surface of any kind attached to it. The company surface could not be walked live either: the aggredyne.com hosting account is SUSPENDED, so the origin answers every path on both aggredyne.com and www.aggredyne.com with an identical 7,768-byte cPanel "Account Suspended" page (plain HTTP 302s to /cgi-sys/suspendedpage.cgi), and its Let's Encrypt certificate, CN=cpanel.aggredyne.com, expired on 2026-05-15. That catch-all makes the HTTP 200 on every REST, GraphQL, MCP, agent-card, llms.txt and /.well-known/ probe a false positive — a random control path returns byte-identical content — so all sixteen well-known probes are recorded as misses and no WellKnown, SecurityTxt or AgentCard pointer was wired. The api./app./portal./developer./cloud. subdomains resolve only to the same shared cPanel wildcard IP 162.253.33.192, not to distinct surfaces. The harvest lead's original Website pointer, https://www.nasdaqprivatemarket.com/, was the secondary-market platform's own home page rather than this company's site and has been removed.

This is an honest zero, not a gap in our research. AggreDyne does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.

What we probed
  • http://www.aggredyne.com/HTTP 302
  • https://www.aggredyne.com/HTTP 200
  • https://www.aggredyne.com/this-path-does-not-exist-zzz9876HTTP 200
  • https://www.aggredyne.com/openapi.jsonHTTP 200
  • https://www.aggredyne.com/swagger.jsonHTTP 200
  • https://www.aggredyne.com/graphqlHTTP 200
  • https://www.aggredyne.com/llms.txtHTTP 200
  • https://www.aggredyne.com/.well-known/agent-card.jsonHTTP 200
  • https://aggredyne.com/.well-known/api-catalogHTTP 200
  • https://aggredyne.com/.well-known/security.txtHTTP 200
  • https://github.com/aggredyneHTTP 404
  • https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm?ID=K181777HTTP 200

Checked 2026-09-12. If this is out of date, tell us on the provider's repo and we will re-run the profile.

AggreDyne is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.

← All providers · Data indexed from github.com/api-evangelist/aggredyne · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of AggreDyne, 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.