Install Jentic One Beta

Connect the Verdi Flows Webhook External API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Verdi Flows Webhook External 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%2Fmercadolibre.com%2Fmercadolibre" | 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%2Fmercadolibre.com%2Fmercadolibre" | 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 Verdi Flows Webhook External API.

Post a Solman revision event with the solman identifier and revision number to trigger the Verdi Flows workflow

Detect a timed-out downstream workflow through the 504 response and retry the same revision event

Validate a revision payload against a strict two-field schema that rejects additional properties

Use Cases

Patterns agents use Verdi Flows Webhook External API for, with concrete tasks.

★ Agent-sent revision notifications through Jentic

GET STARTED

Start building with Verdi Flows Webhook External API

Explore with Jentic One

View OpenAPI Document

Change-management to GenAI workflow handoff

Teams that track changes in Solman use this webhook to kick off downstream GenAI processing for each revision. The body carries only the record identifier and the revision number, so the sender stays simple, and the strict schema with additionalProperties set to false means any extra field is rejected rather than silently ignored.

Read the latest revision number for change record 'ASUASC2314', then POST it as revision with solman 'ASUASC2314' to the Verdi Flows external webhook

Timeout-aware retries

The webhook waits on the workflow it triggers, and returns 504 when that workflow does not respond in time. A sender that sees 504 can retry the same solman and revision pair, while 401 and 403 indicate the OAuth credentials need attention rather than a retry.

POST solman 'ASUASC2314' and revision 3 to the Verdi Flows external webhook, and if the response is 504, wait and resend the same body once

Key Endpoints

1 endpoints — the verdi flows webhook external api receives solman revision events on mercado libre's api host and hands them to a verdi flows genai workflow.

METHOD

PATH

DESCRIPTION

POST

/workspace/genai/verdi-flows/webhook/8112f51a-97ca-45a0-b198-05b2365a2a05/external

Receive a Solman revision event

POST

/workspace/genai/verdi-flows/webhook/8112f51a-97ca-45a0-b198-05b2365a2a05/external

Receive a Solman revision event

Why Jentic?

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

Setup

Wiring the Verdi Flows webhook by hand means running the OAuth 2.0 authorization-code flow against api.mercadolibre.com, refreshing the token, and posting to a long path with a fixed workflow id. Through Jentic you install once, import the webhook from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

The workflow id is fixed in the URL path of the only operation, so a rule allowing that single POST pins your agent to this one Verdi Flows workflow. Nothing else on the Mercado Libre host is reachable unless you import and allow it.

Credential isolation

Your Mercado Libre OAuth token 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 'send a Solman revision event' or 'trigger the Verdi Flows workflow', and Jentic returns the webhook operation with its input schema, including the required solman and revision fields, so the agent calls it correctly.

FAQs

Specific to using Verdi Flows Webhook External API through Jentic.

What authentication does the Verdi Flows Webhook External API use?

Per its OpenAPI spec, the webhook uses OAuth 2.0 with an authorization-code flow whose authorization and token URLs both point at the /oauth/token path on api.mercadolibre.com, and it declares no scopes. A 401 response means the credentials were invalid and a 403 means authorization failed. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

What payload does the Verdi Flows webhook expect?

A JSON object with two required fields: solman, a non-empty string identifier such as ASUASC2314, and revision, an integer of 0 or more. The schema sets additionalProperties to false, so any extra field is rejected.

What are the rate limits for the Verdi Flows Webhook External API?

The OpenAPI spec does not specify rate limits. It does document a 504 response when the downstream workflow does not respond in time. Check the Mercado Libre developer documentation at https://developers.mercadolibre.com for current limits.

Is there a Verdi Flows MCP server?

You don't need an MCP server to give your agent the Verdi Flows webhook. Jentic connects it directly from the API Directory: import it, store your OAuth credential once, and your agent posts revision events without loading another server's tool definitions into its context.

How do I send a Solman revision event through Jentic?

Search Jentic for 'send a Solman revision event', load the POST /workspace/genai/verdi-flows/webhook/8112f51a-97ca-45a0-b198-05b2365a2a05/external operation, and execute it with solman and revision in the body. A 200 response means the webhook received it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Verdi Flows Webhook External API?

Yes. The webhook path already carries a fixed workflow id, so a rule allowing only that one POST operation lets the agent deliver revision events to this workflow and nothing else on the Mercado Libre host. Every call it makes is logged, so you can audit which revisions it sent.

Mercadolibre Verdi Flows Webhook External API

AI ReadinessAI-Ready (A-)75/100

See full scorecard

Community OpenAPI document · agent-readyDeveloper ToolsCi Cdoauth21 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Notify a Mercado Libre Verdi Flows workflow that a Solman change record has a new revision by posting its solman identifier and revision number to the external webhook.

Use for: I need to tell Verdi Flows that Solman record ASUASC2314 is now at revision 2, Trigger the Verdi Flows workflow for a new Solman revision, Retry the revision webhook after the workflow timed out, Check whether the webhook accepted my revision event

Not supported: Does not list Mercado Libre products, manage orders or listings, or read the workflow's results. Use for posting Solman revision events to the Verdi Flows webhook only.

The Verdi Flows Webhook External API receives Solman revision events on Mercado Libre's API host and hands them to a Verdi Flows GenAI workflow. Its single operation accepts a JSON body with exactly two required fields, a solman identifier such as ASUASC2314 and an integer revision number, and rejects any extra properties. The call is authorized with OAuth 2.0 against the api.mercadolibre.com token endpoint, and a 504 response signals that the downstream workflow did not respond in time.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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: ASignals: 4

75%

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).

100%

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

65%

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.

67%

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: A+Signals: 1

90%

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: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Verdi Flows Webhook External API to your agent

Capabilities

Use Cases

Start building with Verdi Flows Webhook External API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mercadolibre Verdi Flows Webhook External API

Jentic AI Readiness Score

Verdi Flows Webhook External 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