Local Infusion

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 publishes 5 APIs on the APIs.io network, including WordPress Content API, MCP API, WordPress Abilities API, and 2 more. Tagged areas include Company, Healthcare, Health Services, Infusion Therapy, and Specialty Pharmacy.

Local Infusion’s developer surface includes authentication, engineering blog, FAQ, and 26 more developer resources.

🌐 Visit website 📡 Source on GitHub

24.3/100 emerging ▬ flat Agent 45/100 agent ready saas Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2

5 APIs 1 MCP Servers

Company Healthcare Health Services Infusion Therapy Specialty Pharmacy Ambulatory CarePatient ServicesAutoimmune Chronic Care MCP WordPress

Kin Score

Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2

Composite quality — 24.3/100 · emerging

Contract Quality 2.8 / 21

Developer Ergonomics 2.7 / 17

Access Clarity 1.8 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.5 / 10

Discoverability 6.9 / 9

Regulatory Posture 9.8 / 15

Agent readiness — 45/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 3 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Surface 0 / 5

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.

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/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/local-infusion: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Local Infusion Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Resources

Documentation 1

Reference material describing how the API behaves

OpenAPI

OpenAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

AgentSkill

LLMsTxt

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Lifecycle

Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

OAuthScopes

OAuthScopes

Authentication

Authentication

Operate 3

Status, limits, changes, and where to get help

FAQ

FAQ

Contact

Contact

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 5

The organization behind the API

Website

Blog

BlogRSS

Newsroom

Careers

Other 4

Properties that don't map to a standard resource type

Accessibility

SecondaryMarket

Overlay

ContentSignal

Source (apis.yml)

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
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:local-infusion-wp-v2-api
  name: Local Infusion WordPress Content API
  description: 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. Read access to published content is anonymous — /wp-json/wp/v2/location
    returned HTTP 200 with 75 centers and /wp-json/wp/v2/posts returned HTTP 200 with 73 posts on 2026-08-25.
  humanURL: https://mylocalinfusion.com/wp-json/
  baseURL: https://mylocalinfusion.com/wp-json/
  tags:
  - wp/v2
  tags_raw:
  - wp/v2
  properties:
  - type: OpenAPI
    url: openapi/local-infusion-wp-v2-api-openapi.yml
  - type: DataModel
    url: data-model/local-infusion-data-model.yml
  - type: ToolCrosswalk
    url: mcp/local-infusion-tool-crosswalk.yml
- 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
- aid: local-infusion:local-infusion-wp-abilities-v1-api
  name: Local Infusion WordPress Abilities API
  description: 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-gated (/wp-json/wp-abilities/v1/abilities returned HTTP
    401 anonymously on 2026-08-25).
  humanURL: https://mylocalinfusion.com/wp-json/wp-abilities/v1
  baseURL: https://mylocalinfusion.com/wp-json/
  tags:
  - wp-abilities/v1
  tags_raw:
  - wp-abilities/v1
  properties:
  - type: OpenAPI
    url: openapi/local-infusion-wp-abilities-v1-api-openapi.yml
  - type: ToolCrosswalk
    url: mcp/local-infusion-tool-crosswalk.yml
- aid: local-infusion:local-infusion-root-api
  name: Local Infusion WordPress Root API
  description: REST API index / namespace discovery, plus the /batch/v1 request batching endpoint.
  humanURL: https://mylocalinfusion.com/wp-json/
  baseURL: https://mylocalinfusion.com/wp-json/
  tags:
  - Root
  tags_raw:
  - root
  properties:
  - type: OpenAPI
    url: openapi/local-infusion-root-api-openapi.yml
- aid: local-infusion:local-infusion-oembed-1-0-api
  name: Local Infusion oEmbed API
  description: oEmbed discovery and proxy endpoints served by the same WordPress install.
  humanURL: https://mylocalinfusion.com/wp-json/oembed/1.0
  baseURL: https://mylocalinfusion.com/wp-json/
  tags:
  - oembed/1.0
  tags_raw:
  - oembed/1.0
  properties:
  - type: OpenAPI
    url: openapi/local-infusion-oembed-1-0-api-openapi.yml
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: OpenAPI
  url: openapi/_original/local-infusion-wp-rest-openapi.yml
- 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.'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/local-infusion"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/local-infusion/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/local-infusion/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

Local Infusion

Kin Score

APIs 5

Local Infusion WordPress Content API

Local Infusion MCP API

Local Infusion WordPress Abilities API

Local Infusion WordPress Root API

Local Infusion oEmbed API