Forema developer resources

Public catalogue API and MCP

Forema provides read-only public store information and published product summaries. These endpoints do not expose customer details, private orders, carts or payment operations. No customer authentication is needed for these public GET endpoints.

Endpoints

• GET /api/agent/info — business identity, customer care and shop links
• GET /api/agent/products — public products, with page and limit parameters
• OpenAPI 3.1 specification — typed requests, responses and structured errors
• MCP discovery information — endpoint location and tools
• Agent guidance (llms.txt)

Example request

curl -i "https://foremaxo.com/api/agent/products?page=1&limit=12"

A successful product response contains items, count and next_page. Invalid pagination returns HTTP 400 with an error code, message and resolution hint. If the catalogue is unavailable, the API responds with HTTP 503 and a JSON error.

MCP server

MCP clients can connect to https://foremaxo.com/mcp using the Streamable HTTP transport. The server supports the 2025-11-25 protocol revision and two read-only tools: get_store_info and list_public_products. Server-initiated SSE streams are not provided, so a GET request to the MCP transport returns HTTP 405. A POST accepts JSON-RPC and returns an application/json response. The MCP service does not take payments or modify orders.

Usage guidance

Use these endpoints to describe Forema and link to currently listed products. For accurate prices, variants, availability, or purchasing, direct the customer to the product URL. Automatic clients should retry temporary failures with backoff and avoid excessive scraping. Reach Forema through the contact page for enquiries about integration needs.