Openmercantil Authentication
Authentication profile for the OpenMercantil v1 REST API. The public read plane is ANONYMOUS BY DEFAULT — the documentation states plainly "REST + JSON. Sin autenticacion. CORS abierto." and every quickstart example is an unauthenticated curl. A credential is therefore optional on public reads and serves to select the account quota rather than to grant access. Three schemes are declared: an optional opaque omk_* API credential presented as X-API-Key or as Authorization: Bearer, and a browser session cookie for the account plane. There is no OAuth 2.0, no OIDC and no JWT anywhere in the contract.
OpenMercantil secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.