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.
Local Infusion is listed with 2 APIs on the APIs.io network, including MCP API, and 1 more. Tagged areas include Company, Healthcare, Health Services, Infusion Therapy, and Specialty Pharmacy.
Local Infusion’s developer surface includes authentication, engineering blog, FAQ, and 25 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Health regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/local-infusion/"><img src="https://apis.io/badge/local-infusion/card.svg" alt="Local Infusion on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
The public WordPress REST API (wp-json) of the Local Infusion website at mylocalinfusion.com: the route index of the site's content management system, catalogued as one site sur...
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's corporate WordPress site exposes two live Model Context Protocol servers under the `mcp` REST namespace, guarded by an OAuth 2.1 authorization server the same h...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: local-infusion
name: Local Infusion
description: '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.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: self-serve
trial: false
try_now: false
public: false
label: Self-serve signup
confidence: medium
source:
- authentication
- rate-limits
- security
generated: '2026-09-02'
method: derived
image: https://mylocalinfusion.com/wp-content/uploads/2024/11/Local-Infusion-window-logo.jpg
url: https://raw.githubusercontent.com/api-evangelist/local-infusion/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: enriched
x-tier-reason: enrichment pass 2026-08-25
specificationVersion: '0.23'
created: '2026-08-25'
modified: '2026-08-25'
tags:
- Company
- Healthcare
- Health Services
- Infusion Therapy
- Specialty Pharmacy
- Ambulatory Care
- Patient Services
- Autoimmune
- Chronic Care
- MCP
- WordPress
tags_raw:
- Company
- Healthcare
- Health Services
- Infusion Therapy
- Specialty Pharmacy
- Ambulatory Care
- Patient Services
- Autoimmune
- Chronic Care
- Model Context Protocol
- WordPress
apis:
- aid: local-infusion:mylocalinfusion-com-website-wordpress-rest
name: Local Infusion Website (WordPress REST)
description: 'The public WordPress REST API (wp-json) of the Local Infusion website at mylocalinfusion.com: the route index
of the site''s content management system, catalogued as one site surface rather than as separate APIs.'
baseURL: https://mylocalinfusion.com/wp-json
tags:
- WordPress
x-surface: platform-generated
properties:
- type: Documentation
url: https://mylocalinfusion.com/wp-json
x-platform: wordpress
x-platform-surface: rest
- aid: local-infusion:local-infusion-mcp-api
name: Local Infusion MCP API
description: 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 challenge and mcp-adapter-default-server returned HTTP 401 rest_forbidden,
probed anonymously 2026-08-25.
humanURL: https://mylocalinfusion.com/wp-json/mcp
baseURL: https://mylocalinfusion.com/wp-json/
tags:
- MCP
tags_raw:
- mcp
properties:
- type: OpenAPI
url: openapi/local-infusion-mcp-api-openapi.yml
- type: MCPServer
url: mcp/local-infusion-mcp.yml
- type: ToolCrosswalk
url: mcp/local-infusion-tool-crosswalk.yml
x-surface: platform-generated
x-platform: wordpress
x-platform-surface: rest
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/local-infusion-domain-security.yml
- type: OAuthScopes
url: scopes/local-infusion-scopes.yml
- type: Authentication
url: authentication/local-infusion-authentication.yml
- type: Website
url: https://mylocalinfusion.com/
- type: Blog
url: https://mylocalinfusion.com/blog/
- type: BlogRSS
url: https://mylocalinfusion.com/feed/
- type: Newsroom
url: https://mylocalinfusion.com/press/
- type: Careers
url: https://mylocalinfusion.com/careers/
- type: FAQ
url: https://mylocalinfusion.com/faqs/
- type: Contact
url: https://mylocalinfusion.com/get-started/
- type: PrivacyPolicy
url: https://mylocalinfusion.com/privacy-policy/
- type: Accessibility
url: https://mylocalinfusion.com/accessibility/
- type: SecondaryMarket
url: https://www.nasdaqprivatemarket.com/
- type: Overlay
url: overlays/local-infusion-wp-rest-overlay.yaml
- type: MCPServer
url: mcp/local-infusion-mcp.yml
- type: ToolCrosswalk
url: mcp/local-infusion-tool-crosswalk.yml
- type: AgentSkill
url: skills/_index.yml
- type: LLMsTxt
url: llms/local-infusion-llms.txt
- type: WellKnown
url: well-known/local-infusion-well-known.yml
- type: ContentSignal
url: well-known/local-infusion-robots.txt
- type: Conventions
url: conventions/local-infusion-conventions.yml
- type: ErrorCatalog
url: errors/local-infusion-problem-types.yml
- type: DataModel
url: data-model/local-infusion-data-model.yml
- type: Lifecycle
url: lifecycle/local-infusion-lifecycle.yml
- type: Conformance
url: conformance/local-infusion-conformance.yml
- type: Packages
url: packages/local-infusion-packages.yml
- type: Plans
url: plans/local-infusion-plans-pricing.yml
- type: RateLimits
url: rate-limits/local-infusion-rate-limits.yml
x-enrichment:
date: '2026-08-25'
status: enriched
artifacts_added: 32
pass: local-v1
x-enrichment-notes: 'The harvest stub carried a Website pointer of https://www.nasdaqprivatemarket.com/ — a secondary-market
venue listing, not the company. It has been corrected to https://mylocalinfusion.com/ (localinfusion.com and www.localinfusion.com
both 301 there) and the venue URL demoted to type SecondaryMarket. Deliberately absent, each a verified negative on 2026-08-25:
Idempotency (no Idempotency-Key in any of 274 operations, none in Access-Control-Allow-Headers, WordPress core provides
none); SDKs and any official package (nothing on npm, PyPI, RubyGems, crates.io, NuGet, Maven Central or the Go proxy, and
no GitHub org under local-infusion or mylocalinfusion — both 404); StatusPage (status.mylocalinfusion.com NXDOMAIN); Deprecation
(no policy, no RFC 8594 headers on any probed response); Security, SecurityTxt and TrustCenter (/.well-known/security.txt
404, no disclosure page, no bug bounty, trust.mylocalinfusion.com NXDOMAIN); Compliance (no SOC 2, ISO 27001, HITRUST or
HIPAA attestation published; /hipaa/ and /notice-of-privacy-practices/ both 404); AgentCard (/.well-known/agent-card.json
and /.well-known/agent.json both 404 — nothing written, per the search-only rule); AsyncAPI and Webhooks (no event surface;
/asyncapi.json, /asyncapi.yaml and /webhooks all 404); GraphQL (/graphql 404); Sandbox, CLI, Components, ChangeLog, Postman,
Roadmap, Pricing, SignUp, TermsOfService, DeveloperPortal, Documentation, APIReference, GettingStarted and Support (none
exists — there is no developer programme, and the site has no terms-of-service page at /terms/ or /terms-of-use/, both 404).
The MCP tool list is empty because tools/list is OAuth-gated on mcp-oauth-server and capability-gated on mcp-adapter-default-server,
and the WordPress Abilities registry it projects from is gated too; nothing was inferred. repair-api-bases.py flags marketing-base-present
on the derived servers[] block (https://mylocalinfusion.com) — that is a false positive here and was NOT changed: the derived
paths all carry the /wp-json prefix, so the site root is the correct server, exactly as in all/a2-biotherapeutics.'
Local Infusion API — frequently asked questions
Does Local Infusion have an API?
Yes. APIs.io lists 2 APIs from Local Infusion, including Local Infusion Website (WordPress REST) and Local Infusion MCP API.
Is there an OpenAPI specification for the Local Infusion API?
Yes. APIs.io indexes 1 OpenAPI specification for Local Infusion, each linked for download from this page.
How do I authenticate with the Local Infusion API?
Local Infusion documents its authentication (apiKey/oauth2 · 2 schemes). The details are profiled on APIs.io as Local Infusion Authentication.
Does Local Infusion have an MCP server?
Yes. APIs.io lists 1 MCP server for Local Infusion: Local Infusion's corporate WordPress site exposes two live Model Context Protocol servers under the `mcp` REST namespace, guarded by an OAuth 2.1 authorization server the same host advertises via RFC
Is the Local Infusion API ready for AI agents?
Local Infusion has a Kin Score of 21.3 out of 100 (emerging) and an Agent Readiness score of 42.1 (agent-ready), scored by API Evangelist on 2026-10-31.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: