Install Jentic One Beta

Connect the PriceLabs Customer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PriceLabs Customer 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%2Fpricelabs.co%2Fpricelabs" | 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%2Fpricelabs.co%2Fpricelabs" | 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 PriceLabs Customer API.

Pull PriceLabs dynamic nightly prices for listings over a dateFrom to dateTo range

Read each listing's min, base, recommended base, and max price with Pricing Dashboard performance metrics

Update the min, base, or max price and tags for one listing or a group of listings

Set date-specific price overrides with a fixed price or a percent change on the recommended price

GET STARTED

Start building with PriceLabs Customer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PriceLabs Customer API for, with concrete tasks.

★ Agent-managed rental pricing

An AI agent helping a short-term rental host can review and adjust PriceLabs pricing without custom integration code. Through Jentic the agent searches for 'get dynamic prices for my listings', calls the listing_prices operation for a listing and date range, and if a local event is coming up, posts a date-specific override with a percent price_type on the recommended price. The host keeps PriceLabs as the pricing engine while the agent handles the routine adjustments.

POST /v1/listing_prices for listing id '2854562' on pms 'airbnb' from 2026-12-01 to 2026-12-31, then POST /v1/listings/2854562/overrides with date '2026-12-31', price '25', and price_type 'percent'

Syncing prices into a channel manager

A property management system or channel manager can import PriceLabs recommendations instead of computing its own. The listing_prices call returns nightly prices for listings that exist in the PriceLabs account, and fetch_rate_plans returns the adjustments needed to derive prices for non-default rate plans, so the downstream system can publish a full rate grid once a day after PriceLabs refreshes.

Call POST /v1/listing_prices for every syncing listing, then GET /v1/fetch_rate_plans with listing_id and pms_name to apply rate plan adjustments before publishing

Bulk price bound updates

Before a slow season a host may want to lower minimum prices across a portfolio. POST /v1/listings accepts a listings array where each entry carries an id, a pms, and any of min, base, or max, plus up to 10 tags, so a single call can move the price floor for many listings at once.

POST /v1/listings with a listings array setting min to 89 for three listing ids on pms 'airbnb'

Market and revenue reporting

A host reviewing performance can combine PriceLabs neighborhood data, which covers the listings considered in the area along with their pricing stats, with reservation_data, which returns bookings and rental revenue from PMSs that share it. Paging with limit and offset over a start_date to end_date range builds a revenue view to compare against the local market.

GET /v1/neighborhood_data for listing_id 'SUNSETPROPS_OLSE___239' on pms 'vrm', then GET /v1/reservation_data for the same pms from 2026-10-01 to 2026-10-31 with limit 100

Key Endpoints

11 endpoints — the pricelabs customer api imports pricelabs dynamic nightly prices for short-term rental listings into any system, with prices refreshed every 24 hours.

METHOD

PATH

DESCRIPTION

POST

/v1/listing_prices

Get prices for listings

GET

/v1/listings

Get all listings in an account

POST

/v1/listings

Update one or more listings

GET

/v1/listings/{listing_id}/overrides

Get date-specific overrides

POST

/v1/listings/{listing_id}/overrides

Add or update a date-specific override

GET

/v1/neighborhood_data

Get neighborhood data for a listing

GET

/v1/reservation_data

Get PMS reservations with revenue

POST

/v1/listing_prices

Get prices for listings

GET

/v1/listings

Get all listings in an account

POST

/v1/listings

Update one or more listings

GET

/v1/listings/{listing_id}/overrides

Get date-specific overrides

POST

/v1/listings/{listing_id}/overrides

Add or update a date-specific override

GET

/v1/neighborhood_data

Get neighborhood data for a listing

GET

/v1/reservation_data

Get PMS reservations with revenue

Why Jentic?

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

Setup

Wiring PriceLabs by hand means enabling the Customer API, sending the key in the X-API-Key header, honouring a per-key rate limit, and allowing long client timeouts for slow price calls. Through Jentic you install once, import PriceLabs from the API Directory, store the key once, and your agent calls it.

Permission scoping

PriceLabs puts the listing id in the URL path for listing reads and overrides (/v1/listings/{listing_id}/overrides), so a rule can pin your agent to one listing for those operations. You choose which operations it may call, so price-changing ones like POST /v1/listings or override deletion are not included unless you add them.

Credential isolation

Your PriceLabs API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get dynamic prices for my listings' or 'set a price override', and Jentic returns the matching PriceLabs operation with its input schema, including pms and listing_id, so the agent calls the right endpoint directly.

FAQs

Specific to using PriceLabs Customer API through Jentic.

What authentication does the PriceLabs Customer API use?

Per its OpenAPI spec, the PriceLabs Customer API authenticates with an API key sent in the X-API-Key header on every operation. You enable the Customer API for your PriceLabs account and copy the key from Settings, API Details. Through Jentic the key is held by your own instance and attached at call time.

Can I override the price for specific dates with the PriceLabs Customer API?

Yes. POST /v1/listings/{listing_id}/overrides takes an overrides array where each entry has a date, a price, and a price_type of fixed or percent. A percent price is a change on the recommended price ranging from -75 to 500. DELETE on the same path removes overrides for the listed dates, and update_children set to true also removes them from child listings.

What are the rate limits for the PriceLabs Customer API?

The OpenAPI spec states that each Customer API key is limited to 60 requests per minute, capped at 1000 requests per hour, and that exceeding it returns 429 Too Many Requests. PriceLabs also recommends a client timeout of 300 seconds because processing time varies with server load.

Is there a PriceLabs MCP server?

You don't need an MCP server to give your agent PriceLabs. Jentic connects it directly from the API Directory: import it, store your X-API-Key once, and your agent calls the pricing operations it needs on demand without loading another server's tool definitions into its context.

How do I fetch listing prices through Jentic?

Search Jentic for 'get dynamic prices for my listings', load the POST /v1/listing_prices operation, and execute it with a listings array of id, pms, dateFrom, and dateTo. The response carries the nightly prices for each listing. 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 PriceLabs Customer API?

Yes. Write a rule that allows only the read operations, such as GET /v1/listings, POST /v1/listing_prices, and GET /v1/neighborhood_data, so the agent can report on prices and the market but cannot change price bounds or overrides. Every call it makes is logged for review.

PriceLabs Customer API

AI ReadinessFoundational (C+)59/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceStorefrontapiKey11 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read and adjust PriceLabs dynamic prices for vacation rental listings: fetch nightly prices, update min, base, and max prices, and set or remove date-specific overrides.

Use for: Get the PriceLabs prices for my listing for next month, I need to raise the minimum price on an Airbnb listing, Set a fixed price override for a holiday weekend, List all listings in my PriceLabs account with their base prices

Not supported: Does not take bookings, message guests, or list properties on booking channels. Use for reading and adjusting PriceLabs rental prices only.

The PriceLabs Customer API imports PriceLabs dynamic nightly prices for short-term rental listings into any system, with prices refreshed every 24 hours. It returns each listing's minimum, base, recommended base, and maximum price alongside the performance metrics shown on the Pricing Dashboard, and lets you update those price bounds and set date-specific overrides with a fixed or percent price_type. Neighborhood market data, rate plan adjustments, and reservation data with rental revenue from the connected PMS round out the surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

35%

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

30%

Example Density

How richly the API is illustrated with examples.

89%

Example Validity

Percentage of examples that conform to their schemas.

27%

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

19%

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.

41%

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

50%

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

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PriceLabs Customer API to your agent

Capabilities

Start building with PriceLabs Customer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PriceLabs Customer API

Jentic AI Readiness Score

PriceLabs Customer 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