# Local Infusion

**Canonical:** https://apis.io/providers/local-infusion/  
**Website:** https://mylocalinfusion.com/  
**APIs profiled:** 5

Local Infusion is a tech-enabled outpatient infusion-therapy provider operating ambulatory infusion centers across thirteen US states — Connecticut, Florida, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, New York, North Carolina, Ohio, South Carolina, Texas and Virginia — where patients with autoimmune, neurological, gastrointestinal and other chronic conditions receive specialty biologic infusions in private suites, supported by a dedicated Infusion Guide who handles referrals, prior authorization, benefits investigation and financial assistance. It sells care, not software: there is no developer programme, no product API, no SDK and no published pricing for any machine surface. It is catalogued here because its corporate WordPress site serves a live, self-describing REST API of 282 routes — including a publicly readable `location` custom post type carrying the company's 75-center directory — because the same install fronts two Model Context Protocol servers guarded by an OAuth 2.1 authorization server the host advertises through RFC 8414 and RFC 9728 metadata, and because the site carries an unusually deliberate agent-discovery layer: llms.txt, llms-full.txt, and .well-known ai-manifest, brand-facts and llm-sitemap documents, with a robots.txt that explicitly allows GPTBot, ClaudeBot, PerplexityBot and Google-Extended.

## Kin Score — 24.3 / 100 (emerging)

Scored 2026-09-01 under rubric 0.17.2. Trend: flat (+0.0 from 24.3).

| Facet | Score |
|---|---|
| Discoverability | 81.5 |
| Contract Quality | 13.2 |
| Governance | 4.5 |
| Contract Governance | 4.5 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 16.1 |
| Commercial Clarity | 10.5 |
| Access Clarity | 10.5 |

Regulatory layer — **Health**: 65.0 (matched via tags).

## Agent readiness — 44.6 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | documented |
| Auth Clarity | served |
| Idempotency | no |
| Error Semantics | verified |
| OpenAPI Examples | partial |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | yes |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | served |
| Protected Resource Metadata | verified |
| Dynamic Client Registration | no |
| Agentic Commerce | no |

## APIs (5)

- **Local Infusion WordPress Content API** — WordPress core content API (posts, pages, media, taxonomies, settings) plus the site's `location` custom post type, which carries the company's public infusion-center directory....
- **Local Infusion MCP API** — Two Model Context Protocol servers exposed by the WordPress MCP adapter. Both require authentication — mcp-oauth-server returned HTTP 401 with a correct RFC 9728 Bearer challeng...
- **Local Infusion WordPress Abilities API** — WordPress Abilities API — the named-ability registry the MCP adapter projects tools from. Routes are advertised in the public discovery document but read access is capability-ga...
- **Local Infusion WordPress Root API** — REST API index / namespace discovery, plus the /batch/v1 request batching endpoint.
- **Local Infusion oEmbed API** — oEmbed discovery and proxy endpoints served by the same WordPress install.

## MCP servers (1)

- **Local Infusion MCP Server**

## Security (2)

- **Local Infusion Authentication** — apiKey/oauth2 · 2 schemes
- **Local Infusion Domain Security** — TLSv1.3 · DMARC

## Plans (1)

- **Local Infusion Plans Pricing**

## Tags

Company, Healthcare, Health Services, Infusion Therapy, Specialty Pharmacy, Ambulatory Care, Patient Services, Autoimmune, Chronic Care, MCP, WordPress

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/local-infusion/). Scores are computed from the provider's own public artifacts under a published rubric.