Your catalog, one npx away from Claude. And a REST API your developers will not hate.

Yes — a public REST API v1 covering products, variants, media, categories, brands, vendors, attributes, inventory across all eight states, and multistore overrides and locales, for both reads and writes. It uses cursor pagination, accepts idempotency keys on writes, and offers bulk endpoints of up to 500 products per call with job-status polling. Apimio publishes the full reference at app.apimio.com/developers, and the API is on Advanced PIM and Enterprise PIM.

No. The public API is REST only. Apimio uses Shopify's GraphQL Admin API internally for sync, but what is exposed to you is REST — and it is better to say that plainly than let a GraphQL expectation form and disappoint someone mid-build.

Not yet. What exists is code samples in five languages in the reference, plus the OpenAPI 3.1 spec itself, which most language toolchains can generate a client from. Packaged, published SDKs are not something Apimio ships today, and the samples should not be mistaken for one.

MCP is the protocol AI clients use to reach external tools. Apimio publishes @apimio/mcp on npm, so one npx line connects Claude or any other MCP client to a merchant catalog with 47 tools — generated live from the OpenAPI spec, which means new API capability reaches agent tooling without waiting for a separate SDK release. It runs against production: the tools read and, with a scoped key that allows it, write the real catalog. It is genuinely published and installable, not an announcement of intent.

A product catalog an LLM or AI shopping assistant can read without guessing: every attribute present, categories resolved to a standard scheme such as Google's product taxonomy, descriptions in plain language, and no channel-specific abbreviations or codes. Apimio produces this as an agent-ready feed format on the same feed engine as its Google Shopping and Meta feeds, served at a hosted URL that refreshes on schedule (Advanced and Enterprise plans). It can be mapped to what the ChatGPT and OpenAI product-feed programs ask for; it is not an official OpenAI specification. The API and MCP server give agents the same catalog interactively.

Yes — outbound webhooks for product and variant events, HMAC-SHA256 signed so you can verify the payload came from Apimio, with automatic retries and backoff, an inspectable delivery log and manual redelivery. What is not supported is inbound public webhooks: you cannot register an endpoint that writes into Apimio. Writes go through the REST API.

Monthly call quotas run to 250,000 on Advanced PIM and 1,000,000 on Enterprise PIM, with rate limits scaled to the plan. Keys are org-bound and managed under role-based permissions, and an admin can grant access to a partner agency working on a client account. Apimio does not offer API access on Basic PIM.

Advanced PIM and Enterprise PIM, or by arrangement. It is not part of Basic PIM. If you are an agency needing programmatic access to a client account, an admin on that account can grant it to you. The MCP server and the agent-ready feed follow the same plan gating in Apimio (Advanced and Enterprise plans).