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.
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 Local Infusion the way a machine reads it — 11 machine-readable artifacts across 5 APIs, 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 — Local Infusion scores 24.3/100 (emerging), with a separate agent-readiness read of 45/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Local Infusion's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/local-infusion/"
title="Local Infusion on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/local-infusion.svg"
alt="Local Infusion Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/local-infusion/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/local-infusion/"
title="Local Infusion on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/local-infusion/card.svg"
alt="Local Infusion Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Local Infusion
Each block below is one kind of artifact we hold for Local Infusion. 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.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
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
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Local Infusion MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Local Infusion Rate Limits
RATE LIMITSSecurity Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Local Infusion — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/local-infusion · machine-readable index on apis.io
This is an independent, third-party profile of Local Infusion, 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.