Paladira developer documentation

Run a store from anything that can hold a token.

Paladira is a point-of-sale and back-office platform for food and retail businesses in Brazil — menu and catalog, orders and tables, inventory, suppliers, team permissions and reporting. This site documents the parts a program can reach: the Model Context Protocol connector merchants use today, and the HTTP surface underneath it.

Connect an assistant Explore the API

340tools advertised

141read-only

18capabilities withheld

2OAuth scopes

Start somewhere

Connect an assistantTurn the connector on for a store, authorize a host, and make the first call — the five-minute path.MCP connectorEndpoint, OAuth 2.1 authorization, scopes, and the capabilities deliberately withheld from assistants.Tool catalogAll 340 advertised tools, generated from the manifest the server actually serves.Platform APIPreviewThe HTTP endpoints behind every tool — method, path, parameters — and what opening them publicly will mean.Data handlingWhat an assistant can and cannot read, how responses are redacted, and where the LGPD documents live.Product researchWhich price-source types are live versus planned, and how to read a research run.

What is public today

Two surfaces, at different stages. The distinction is not cosmetic: one is something a merchant can switch on this afternoon, the other is documented here so that opening it is a decision rather than a discovery.

Surface	Stage	What that means
MCP connector	Available	Enabled per store by its operator. A merchant connects an assistant from Settings › AI integration with no code at all.
HTTP API	Preview	Every endpoint here is real and in production, reachable today through the connector. Direct third-party access is not open yet — see what preview means.
Webhooks	Not published	The platform emits events internally; nothing is published for third parties, and nothing on this site should be read as promising a date.

Who this is for

Merchants connect Paladira to an assistant from inside the app — no code required, and the in-product wizard is the supported path. This documentation exists for three other readers: integrators who want to know exactly what the connector exposes before authorizing it, the assistant directories that review the connector before listing it, and anyone evaluating what building on the platform would involve.

Contact

Product and integration support: suporte@paladira.com. Privacy requests and data-subject rights under the LGPD go to the data protection officer at privacidade@paladira.com, as published in the privacy policy.