Miso API

Name: Miso API API
Brand: Miso API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLEmbeddings SearchapiKey26 EndpointsREST

For Agents

Power product personalisation — recommendations, search, Q&A, and interaction tracking — through Miso's machine-learning APIs.

Quickstart

Get started with Miso API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get Miso product recommendations for a user"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Miso API API.

Upload product or content catalogue records and update them in bulk

Stream user interaction events into Miso to train recommendation engines

Run personalised search queries with autocomplete and multi-get support

Generate recommendations for a given user or product context

Run Q&A queries against the trained Ask engine

GET STARTED

Start building with Miso API API

Explore with Jentic

View OpenAPI Document

Use for: I need to upload my product catalogue to Miso, Send a user interaction event when a customer views a product, Run a personalised search query for a logged-in user, Get product recommendations for a specific user

Not supported: Does not handle payments, customer support, or content authoring — use for recommendations, personalised search, Q&A, and interaction tracking only.

Jentic publishes the only available OpenAPI document for Miso API, keeping it validated and agent-ready.

Miso is a personalisation and search platform that trains machine-learning engines on a site's interaction logs, product catalogue, and user data to power recommendations, search, and Q&A. The API exposes 26 endpoints across products, users, interactions, search, recommendations, ask, experiments, and bulk operations. Authentication is via an api_key query parameter, with separate Secret and Publishable keys for backend and client-side use.

Use Cases

Patterns agents use Miso API API for, with concrete tasks.

★ Catalogue Sync and Personalised Search

Keep Miso's index in sync with the live product catalogue using POST /v1/products and bulk delete via POST /v1/products/_delete, then power site search with POST /v1/search/search and autocomplete via POST /v1/search/autocomplete. Suitable for e-commerce and content sites that want personalised relevance ranking trained on real user behaviour.

Upload 500 new products to Miso via POST /v1/products and verify the index returns them in a search for a relevant query

Real-Time Recommendation Serving

Stream user interaction events via POST /v1/interactions so Miso's engines stay current, then call the Recommendation APIs to serve personalised results on product pages and home feeds. Reduces the data-engineering work needed to maintain a recommendations pipeline compared to building one in-house.

Send a 'product_detail_page_view' interaction for user_id 'u_42' on product_id 'p_99' and then fetch recommendations for that user

Generative Q&A Over Product Catalogue

Use the Ask APIs to answer customer questions against the Miso-trained Q&A engine. Pair with the Search APIs to ground responses in actual catalogue content. Useful for storefront chat assistants where answers must reference real products.

Submit a question 'Which running shoes are best for trails under £100?' to the Miso Ask API and return the cited products

AI Agent for Personalisation Operations

An agent integrated through Jentic can refresh the Miso catalogue when products change, monitor interaction throughput, and call recommendations for ad-hoc personalised emails — without holding the Secret API key. Jentic isolates the key in its vault and the agent uses Jentic's intent search to navigate the 26 Miso endpoints.

Through Jentic, refresh the Miso product catalogue from the latest CMS export and trigger a recommendation request for a sample user

Key Endpoints

26 endpoints — miso is a personalisation and search platform that trains machine-learning engines on a site's interaction logs, product catalogue, and user data to power recommendations, search, and q&a.

METHOD

PATH

DESCRIPTION

POST

/v1/products

Upload product or content records

POST

/v1/products/_delete

Bulk delete products

POST

/v1/interactions

Upload user interaction events

POST

/v1/users

Upload user records

POST

/v1/search/search

Run a personalised search

POST

/v1/search/autocomplete

Run autocomplete suggestions

POST

/v1/search/mget

Multi-get product details by IDs

POST

/v1/experiments/{experiment_id_or_slug}/events

Send an experiment event

POST

/v1/products

Upload product or content records

POST

/v1/products/_delete

Bulk delete products

POST

/v1/interactions

Upload user interaction events

POST

/v1/users

Upload user records

POST

/v1/search/search

Run a personalised search

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Miso Secret API keys are stored encrypted in the Jentic vault. Agents receive scoped execution access — the key is never exposed in prompts, logs, or agent memory and is appended to the api_key query parameter at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g. 'get Miso recommendations for a user') and Jentic returns the matching operation with its input schema, so the agent can call the right endpoint without browsing the 26-operation surface.

Time to first call

Direct Miso integration: 2-4 days to wire api_key auth, batch interaction ingestion, and recommendation calls. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Algolia

Algolia is a managed search platform with broader index features; Miso emphasises ML-trained personalisation on top of search.

Choose Algolia when fast typo-tolerant search is the priority; choose Miso when behaviour-trained personalisation is the differentiator.

Alternative

Meilisearch

Meilisearch is a self-hostable open-source search engine, an alternative when Miso's personalisation is not needed.

Choose Meilisearch for cost-controlled self-hosted search; choose Miso for managed personalisation and recommendations.

Complementary

Segment

Segment captures user events from across the stack and can fan them out to Miso's interaction endpoints.

Pair with Miso when interaction events already flow through Segment and you want one ingestion path that mirrors to Miso.

FAQs

Specific to using Miso API API through Jentic.

What authentication does the Miso API use?

The API uses an api_key query parameter. Miso issues a Secret API Key for backend calls and a Publishable API Key for client-side use. When called through Jentic, the secret key is stored in the Jentic vault and appended to requests at execution time.

Can I run personalised search through the Miso API?

Yes. POST /v1/search/search runs a personalised search query, POST /v1/search/autocomplete provides typeahead suggestions, and POST /v1/search/mget retrieves multiple products by ID. All search results are ranked using the engine trained on your interactions and catalogue.

How do I keep my Miso product catalogue in sync?

POST /v1/products uploads or updates product/content records, GET /v1/products/{product_id} reads a single product, and POST /v1/products/_delete handles bulk deletions. POST /v1/products/_ids returns the current list of indexed product IDs, useful for diffing against a CMS export.

What are the rate limits for the Miso API?

The OpenAPI specification does not publish explicit rate limits. Miso is designed for high-throughput interaction ingestion — implement client-side batching for /v1/interactions and exponential backoff on HTTP 429 responses for search and recommendation calls.

How do I stream user interactions through Jentic?

Search Jentic for 'send a Miso user interaction event' and POST /v1/interactions will be returned. Load the operation schema, supply the user_id, product_id, and interaction type, and execute. Jentic handles the api_key query parameter automatically.