ListingsAPI

Use ListingsAPI through an already connected MCP client at https://listingsapi.com/mcp with Streamable HTTP. This skill supplies workflow instructions; it does not install an MCP client, start a local server, or bundle executable code. If the runtime has no MCP connection, explain the connection prerequisite rather than inventing an OpenClaw configuration or installing a bridge.

ListingsAPI is an external service. A paid plan is normally required for production use. The limited-availability Day Pass covers only sandbox locations and listings.

This skill is released under MIT-0; see LICENSE. That license applies to the skill, not to the hosted ListingsAPI service.

Authentication

Prefer the client's public OAuth browser flow when supported. ListingsAPI advertises dynamic client registration and PKCE, with read and write scopes; no pre-issued client secret is needed. Start with read access unless the user's task requires writes. The user completes sign-in and consent.

For an existing user-managed key, use Authorization: API <key>. If the runtime reads it from the environment, use LISTINGSAPI_API_KEY; never embed the value in this skill, generated source, logs, or chat. OAuth bearer tokens apply to the MCP endpoint; REST requests use the API key prefix. Do not create credentials or configure accounts without the user's authorization.

Read an account

Use whoami to establish the connected account, then locations_all or locations_search to identify the requested location. Resolve the location before fetching listings_premium, reviews_list, or publisher analytics. Read get_usage when usage is relevant. An empty list is possible for a new account.

Use search_docs, get_doc, and get_endpoint to check current contracts before constructing inputs. These tools and the MCP guide are the source for supported operations; do not assume every REST operation has an MCP equivalent. Archive and delete operations are not exposed through MCP.