Install Jentic One Beta

Connect the Licitalab to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Licitalab, 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%2Flicitalab.cl%2Flicitalab" | 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%2Flicitalab.cl%2Flicitalab" | 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 Licitalab API.

Search and follow Chilean public-tender opportunities scraped from Mercado Publico and other Chile procurement systems

Assign tender opportunities across workspace members with bulk follow, unfollow, and tag operations

Track tender deadlines and milestones through the calendar and notification endpoints

Submit offers and manage guarantee documents associated with tender responses

GET STARTED

Start building with Licitalab API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Licitalab API for, with concrete tasks.

★ Tender Discovery Pipeline

Continuously surface new Chilean public-tender opportunities relevant to a workspace's business lines, then filter and assign them to the right team members. The opportunities endpoints support search, push-by-code, share, and assignment in bulk. Setup takes under a day for a workspace already authenticated against Licitalab.

List opportunities for the current workspace filtered by business line 'construction', then assign the top five to user ID 'member-42'

Bid Response Workflow

Coordinate tender bid responses by tracking deadlines, attaching offer documents, and managing guarantees. The Offers, Attachments, and Guarantee tags expose document submission and bond tracking. This replaces manual spreadsheet workflows with an API-driven response pipeline.

Upload an attachment to opportunity code 'OP-2026-0145' and create a guarantee record with amount 5000000 CLP

Workspace Notifications and Calendar

Centralize tender deadlines and updates in a workspace calendar with notifications when status changes. The Notification, Calendar, and Dashboard tags expose realtime workspace state. Useful for procurement teams managing dozens of concurrent tenders.

Fetch all unread notifications for workspace ID 'ws-123' and produce a calendar view of deadlines in the next seven days

AI Agent Procurement Assistant

An AI agent uses Jentic to call Licitalab opportunities, calendar, and notification endpoints to summarize the day's tender activity for a Chilean procurement team. The agent filters by business line, surfaces priority deadlines, and drafts assignment recommendations. Credentials are isolated through Jentic.

Search Jentic for 'find Chilean tender opportunities', load the opportunities-by-workspace schema, fetch today's matches, and post a summary

Key Endpoints

225 endpoints — jentic publishes the only available openapi specification for licitalab, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/auth/login

Authenticate user and issue bearer token

POST

/api/v1/opportunities/create

Create a new tender opportunity record

GET

/api/v1/opportunities/workspace

List opportunities for the current workspace

GET

/api/v1/opportunities/code/{code}/details

Get full details of an opportunity by code

PUT

/api/v1/opportunities/follow-list

Follow multiple opportunities in bulk

PUT

/api/v1/opportunities/assign-list

Assign multiple opportunities to a workspace member

POST

/api/v1/auth/login

Authenticate user and issue bearer token

POST

/api/v1/opportunities/create

Create a new tender opportunity record

GET

/api/v1/opportunities/workspace

List opportunities for the current workspace

GET

/api/v1/opportunities/code/{code}/details

Get full details of an opportunity by code

PUT

/api/v1/opportunities/follow-list

Follow multiple opportunities in bulk

PUT

/api/v1/opportunities/assign-list

Assign multiple opportunities to a workspace member

Why Jentic?

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

Setup

Wiring the Licitalab API by hand means logging in for a JWT bearer token, keeping it refreshed, finding which of the 225 operations cover tender discovery and bid coordination, and calling api2.licitalab.cl yourself. Through Jentic you install once, import the Licitalab API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Licitalab reads a tender by code in the path (/opportunities/code/{code}/details) but coordinates through workspace and list operations, so scope the agent to the operations it needs, such as searching opportunities or following a tender. You leave out assign or follow-list writes unless you add them, so it only calls the ones you allow.

Credential isolation

Your Licitalab bearer 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 'find Chilean tender opportunities', and Jentic returns the matching Licitalab operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Licitalab API through Jentic.

Why is there no official OpenAPI spec for Licitalab?

Licitalab does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Licitalab API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Licitalab API use?

Licitalab uses HTTP bearer authentication. Tokens are issued via /api/v1/auth/login or /api/v1/auth/google and validated through /api/v1/auth/validate. Through Jentic, bearer tokens are stored in your Jentic One instance and injected at execution time.

Can I follow Chilean public tenders programmatically with the Licitalab API?

Yes. Use POST /api/v1/opportunities/push_code to push a tender code into the workspace, PATCH /api/v1/opportunities/followed/{code} to follow it, and PUT /api/v1/opportunities/follow-list to follow many at once.

What are the rate limits for the Licitalab API?

The spec does not document explicit rate limits. Treat workspace-scoped endpoints as moderately throttled; back off on HTTP 429 and use bulk operations such as /api/v1/opportunities/added-opportunities to reduce request volume.

How do I assign a tender to a team member through Jentic?

Run pip install jentic, then search Jentic with 'assign a Licitalab tender to a member' to retrieve the /api/v1/opportunities/assign-list operation. Execute it with the opportunity codes and target member ID; Jentic handles the bearer token automatically.

Is the Licitalab API free?

Licitalab is a paid SaaS for Chilean procurement teams. API access is included with paid workspace plans; check licitalab.cl for current pricing tiers.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the 225 Licitalab operations and which bearer credentials the agent can use. You can allow read-only calls such as searching opportunities or fetching a tender by code with GET /api/v1/opportunities/code/{code}/details, while leaving out write operations like PUT /api/v1/opportunities/follow-list and PUT /api/v1/opportunities/assign-list. The agent can then only call the endpoints you have explicitly permitted.

Licitalab Cl Licitalab

Name: Licitalab API
Brand: Licitalab
Availability: InStock

Agent-ready OpenAPI document · curated by JenticProductivityCollaborationbearer225 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search Chilean public-procurement opportunities, manage tender follow-up, and coordinate workspace members and offers via 225 bearer-authenticated endpoints.

Use for: Search for new public-tender opportunities in Chile by business line, I need to follow a Mercado Publico tender by its code, List all tenders assigned to a specific team member in our workspace, Get the full details of a Chilean tender opportunity by code

Not supported: Does not handle Chilean tax filing, payroll, or banking - use for Chilean public-procurement tender discovery and bid coordination only.

Jentic publishes the only available OpenAPI specification for Licitalab, keeping it validated and agent-ready. Licitalab is a Chilean public-procurement workspace that helps businesses discover, track, and respond to government tenders sourced from Mercado Publico and other Chilean procurement bodies. The API exposes 225 endpoints covering authentication, opportunities discovery, member workspaces, calendar tracking, attachments, guarantees, business lines, and notifications. Agents can search tender opportunities by code, follow them, assign them across team members, and manage offers and guarantees through bearer-token authentication.

Jentic One on Github View OpenAPI Document

Connect the Licitalab to your agent

Capabilities

Start building with Licitalab API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Licitalab Cl Licitalab