Local Infusion oEmbed API
oEmbed discovery and proxy endpoints served by the same WordPress install.
Work with this as data
Every API 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 apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/local-infusion-oembed-1-0-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Local Infusion WordPress REST Oembed/1.0 API
version: wp/v2
summary: The live WordPress REST API served by the Local Infusion corporate website.
description: Derived verbatim from the route-discovery document the Local Infusion web server publishes at https://mylocalinfusion.com/wp-json/ (fetched 2026-08-25, HTTP 200).
x-derived-from: https://mylocalinfusion.com/wp-json/
x-derived-on: '2026-08-25'
x-apievangelist-method: derived
servers:
- url: https://mylocalinfusion.com
description: Production
tags:
- name: oembed/1.0
description: oEmbed discovery and proxy endpoints.
paths:
/wp-json/oembed/1.0:
get:
operationId: getOembed10
summary: GET /oembed/1.0
description: WordPress REST API route `/oembed/1.0` in namespace `oembed/1.0`, as advertised by the live route-discovery document at https://mylocalinfusion.com/wp-json/.
tags:
- oembed/1.0
responses:
'200':
description: Success
content:
application/json:
schema: {}
'401':
description: Authentication required or capability missing
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'404':
description: No route or resource found
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
parameters:
- name: namespace
in: query
schema:
default: oembed/1.0
- name: context
in: query
schema:
default: view
/wp-json/oembed/1.0/embed:
get:
operationId: getOembed10Embed
summary: GET /oembed/1.0/embed
description: WordPress REST API route `/oembed/1.0/embed` in namespace `oembed/1.0`, as advertised by the live route-discovery document at https://mylocalinfusion.com/wp-json/.
tags:
- oembed/1.0
responses:
'200':
description: Success
content:
application/json:
schema: {}
'401':
description: Authentication required or capability missing
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'404':
description: No route or resource found
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
parameters:
- name: url
in: query
schema:
type: string
format: uri
description: The URL of the resource for which to fetch oEmbed data.
required: true
- name: format
in: query
schema:
default: json
- name: maxwidth
in: query
schema:
default: 600
/wp-json/oembed/1.0/proxy:
get:
operationId: getOembed10Proxy
summary: GET /oembed/1.0/proxy
description: WordPress REST API route `/oembed/1.0/proxy` in namespace `oembed/1.0`, as advertised by the live route-discovery document at https://mylocalinfusion.com/wp-json/.
tags:
- oembed/1.0
responses:
'200':
description: Success
content:
application/json:
schema: {}
'401':
description: Authentication required or capability missing
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'404':
description: No route or resource found
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
parameters:
- name: url
in: query
schema:
type: string
format: uri
description: The URL of the resource for which to fetch oEmbed data.
required: true
- name: format
in: query
schema:
type: string
enum:
- json
- xml
default: json
description: The oEmbed format to use.
- name: maxwidth
in: query
schema:
type: integer
default: 600
description: The maximum width of the embed frame in pixels.
- name: maxheight
in: query
schema:
type: integer
description: The maximum height of the embed frame in pixels.
- name: discover
in: query
schema:
type: boolean
default: true
description: Whether to perform an oEmbed discovery request for unsanctioned providers.
components:
schemas:
WPError:
type: object
description: The WordPress REST API error envelope, observed verbatim on live 401 responses from this host. Not RFC 9457 problem+json.
properties:
code:
type: string
examples:
- rest_forbidden
- mcp_unauthorized
message:
type: string
examples:
- Sorry, you are not allowed to do that.
- MCP authentication required.
data:
type: object
properties:
status:
type: integer
examples:
- 401
securitySchemes:
mcpOAuth2:
type: oauth2
description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC 8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched 2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
flows:
authorizationCode:
authorizationUrl: https://mylocalinfusion.com/oauth/authorize
tokenUrl: https://mylocalinfusion.com/oauth/token
refreshUrl: https://mylocalinfusion.com/oauth/token
scopes:
mcp: Access the site's Model Context Protocol server.
wpNonce:
type: apiKey
in: header
name: X-WP-Nonce
description: WordPress cookie-authentication nonce. Advertised by the live server in its Access-Control-Allow-Headers response header (Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type), observed on a 401 from the MCP endpoint.