Install Jentic One Beta

Connect the Marea Alcalina API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Marea Alcalina API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmareaalcalina.com%2Fmareaalcalina" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmareaalcalina.com%2Fmareaalcalina" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Marea Alcalina API.

Create a storefront from a manifest with name, language (es, en, or pt), currency, and businessType, including products and categories in the same call

Add a product with title and price, plus optional salePrice, sku, stock, imageUrl, and tags, to an existing storefront

Publish a storefront to take it live, with 402, 422, and 451 responses telling the agent why a publish was refused

Bootstrap a merchant account, starter storefront, and restricted user key in one call, then verify it with the emailed 6-digit code

GET STARTED

Start building with Marea Alcalina API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Marea Alcalina API for, with concrete tasks.

★ Agent-built storefront through Jentic

A merchant tells an agent what they sell, and the agent builds the shop. Through Jentic it creates a storefront with a name, language, currency, and businessType, adds products, and publishes. The Marea mk_ key is injected by Jentic at call time, so the agent never holds it.

POST /v1/storefronts with name 'Panadería Luna', language 'es', currency 'MXN', and businessType 'Panadería y Repostería', then POST /v1/storefronts/{storefrontId}/products with title 'Concha' and price 15, then POST /v1/storefronts/{storefrontId}/publish

Merchant onboarding by a partner app

A developer integration signs merchants up without sending them through a web form. Creating a user with email, displayName, and sourceAgent returns the account, a restricted user key, and optionally a starter storefront, and emails a 6-digit code. When the merchant reads the code back, the verify call upgrades that same key to full scope.

POST /v1/users with email 'ana@example.com', displayName 'Ana', and sourceAgent 'my-agent', store the returned user key, then POST /v1/users/{userId}/verify with the 6-digit code the user reads back

Product and price maintenance

Shops change prices and stock often. Products can be listed with cursor pagination, with includeHidden to see products marked hide, and patched one at a time, where nested objects deep-merge and arrays are fully replaced. This lets an agent apply a sale price or hide a sold-out item without rebuilding the shop.

GET /v1/storefronts/{storefrontId}/products with includeHidden true, then PATCH /v1/storefronts/{storefrontId}/products/{productId} setting salePrice 199 on the product titled 'Pastel de chocolate'

Order and account event notifications

Integrations need to know when a merchant verifies or cancels, and when orders arrive. A webhook endpoint subscribes to events such as user.verified, user.cancelled, and order.*, and a developer endpoint covers every storefront that developer bootstrapped. The signing secret is shown once on creation and can be rotated, with no overlap window in v1.

POST /v1/webhook_endpoints with url 'https://example.com/hooks/marea' and subscribedEvents ['order.*', 'user.verified'], and store the returned signingSecret

Key Endpoints

21 endpoints — the marea alcalina api builds and publishes online storefronts for small businesses, from the product list to delivery, pickup, dine-in, and whatsapp settings.

METHOD

PATH

DESCRIPTION

POST

/v1/storefronts

Create a storefront from a manifest

POST

/v1/storefronts/{storefrontId}/products

Add a product

PATCH

/v1/storefronts/{storefrontId}/products/{productId}

Update a product

POST

/v1/storefronts/{storefrontId}/publish

Publish a storefront

POST

/v1/users

Bootstrap a merchant account

POST

/v1/users/{userId}/verify

Verify a user with the emailed code

POST

/v1/webhook_endpoints

POST

/v1/storefronts

Create a storefront from a manifest

POST

/v1/storefronts/{storefrontId}/products

Add a product

PATCH

/v1/storefronts/{storefrontId}/products/{productId}

Update a product

POST

/v1/storefronts/{storefrontId}/publish

Publish a storefront

POST

/v1/users

Bootstrap a merchant account

POST

/v1/users/{userId}/verify

Verify a user with the emailed code

POST

/v1/webhook_endpoints

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Marea by hand means handling its mk_ bearer keys, telling developer keys from user keys, and walking the email-code verification step before a user key gets full scope. Through Jentic you install once, import the Marea Alcalina API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Marea puts the storefront id in the URL path (/v1/storefronts/{storefrontId}/...), so a rule can pin your agent to one storefront and the operations you pick under it. You choose the operations it may call, so actions like publishing, webhook deletion, or user creation are not included unless you add them.

Credential isolation

Your Marea key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an online storefront' or 'add a product to my shop', and Jentic returns the matching Marea operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Marea Alcalina API through Jentic.

Is there a Marea Alcalina MCP server?

You don't need an MCP server to give your agent the Marea Alcalina API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Storefront and product operations are found by intent when needed, so no extra tool definitions sit in the agent's context.

What authentication does the Marea Alcalina API use?

Per its OpenAPI spec, operations use a bearer token in the Authorization header with a key of the form mk_dev_ (developer) or mk_user_ (user). The spec also declares an X-API-Key header carrying the same mk_ value for environments that cannot send Authorization. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Why would a storefront publish fail?

The publish operation returns 402 if the plan does not permit publishing, 422 if the storefront has no products, and 451 if the terms of service have not been accepted. Republishing is idempotent, so an agent can retry once the cause is fixed.

Can I limit what my agent is allowed to do with the Marea Alcalina API?

Yes. Write a rule that allows only product listing and product updates under /v1/storefronts/{storefrontId}/products for one storefront id, so a product-editing agent can change prices and stock in that shop but cannot publish, create users, or touch webhooks. Your own instance runs those calls.

What are the rate limits for the Marea Alcalina API?

The spec states one specific limit: resending a verification code is limited per user to 3 per hour and 5 per day. GET /v1/me returns the rate-limit window for the calling key. For other limits, see the published spec at https://api.mareaalcalina.com/v1/openapi.json.

How do I create and publish a storefront through Jentic?

Add the Marea Alcalina API to Jentic One from the directory and store your mk_ key once. Your agent searches for 'create an online storefront', calls POST /v1/storefronts with name, language, currency, and businessType, adds products, then calls the publish operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Marea Alcalina API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontbearer21 EndpointsREST

For Agents

Create and publish Marea storefronts, add and edit products, bootstrap and verify merchant accounts, and register webhooks for user and order events.

Use for: I want to set up an online menu for my bakery with WhatsApp ordering, Add a chocolate cake priced at 250 MXN to my storefront, Publish my storefront so customers can see it, Create a Marea account for a new merchant and send the verification email

Not supported: Does not process card payments, print shipping labels, or manage warehouse inventory across locations. Use for building, stocking, and publishing Marea storefronts and onboarding their merchants only.

The Marea Alcalina API builds and publishes online storefronts for small businesses, from the product list to delivery, pickup, dine-in, and WhatsApp settings. A storefront is created from a manifest with a name, language, currency, and businessType, products are added or edited under it, and a publish call takes it live. Developer keys can also bootstrap a Marea account for a user in one call, confirm it with a 6-digit email code, issue extra restricted user keys, and register signed webhook endpoints for user and order events.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Marea Alcalina API to your agent

Capabilities

Start building with Marea Alcalina API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Marea Alcalina API

Jentic AI Readiness Score

Marea Alcalina API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness