Install Jentic One Beta

Connect the Listings API to your agent

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

Create a business location and update writable fields such as phone, bizUrl, business hours, and primary Google category

Connect Google and Facebook accounts, trigger listing matches, and confirm which listings belong to which location

List reviews, Q&A, and social interactions for a location or across many, filtered by site, date range, and rating

Post or edit an owner response to a review on its source platform

GET STARTED

Start building with Listings API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Listings API for, with concrete tasks.

★ Agent-run review responses through Jentic

A local marketing agent can watch reviews across every location, draft owner replies, and post them back to the source platform. Through Jentic it finds the interactions list and respond operations by intent and loads their schemas, so the developer does not hand-wire the Authorization header or the review filters. Google Reviews accept a single owner reply per review, so the agent edits an existing response instead of posting a second one.

List interactions for a locationId with a startDate of 2026-10-01, pick reviews with a low rating that have no response, and post a reply to each with responseContent and its interactionId.

Multi-location listing sync

Brands with many stores keep name, phone, website, hours, and categories consistent across publishers by updating each location once in the Listings API. Only the fields sent in an update are changed, and archive and cancel-archive operations handle closures and reopenings without deleting history.

Look up locations by storeCodes 'ATX-01', then update that location's businessHours for Saturday to open 10:00am to 02:00pm.

Local performance reporting

For each location the API returns review analytics KPIs, a review volume and average rating timeline, a per-site breakdown, and Google, Facebook, and Bing insights over a date range, which together form a monthly local search report.

Fetch Google insights for a locationId with fromDate 2026-09-01 and toDate 2026-09-30, plus the review analytics overview for the same range, and summarize both.

Scheduled social publishing

Marketing teams publish, schedule, or draft one post for a brand across its connected channels, or queue many posts across brands as one asynchronous bulk job and check each row's result. Post insights and comments come back per connected channel.

Create a social post for a socialProfileId on INSTAGRAM and LINKEDIN with action SCHEDULE, scheduleDate 2026-11-14, and scheduleTime 09:30.

Key Endpoints

82 endpoints — the listings api manages business locations and keeps their listings in sync across google, facebook, bing, and other publishers.

METHOD

PATH

DESCRIPTION

POST

/api/v4/locations

Create a new location

POST

/api/v4/locations/update

Update a location

GET

/api/v4/locations/{locationId}/reviews

List interactions for a location

POST

/api/v4/locations/reviews/respond

Respond to a review

GET

/api/v4/locations/{locationId}/google-analytics

Google insights for a location

POST

/api/v4/social/posts

Publish or schedule a social post

GET

/api/v4/locations/{locationId}/listings/duplicates

Duplicate listings for a location

POST

/api/v4/connected-accounts/trigger-matches

Match listings to locations

POST

/api/v4/locations

Create a new location

POST

/api/v4/locations/update

Update a location

GET

/api/v4/locations/{locationId}/reviews

List interactions for a location

POST

/api/v4/locations/reviews/respond

Respond to a review

GET

/api/v4/locations/{locationId}/google-analytics

Google insights for a location

POST

/api/v4/social/posts

Publish or schedule a social post

GET

/api/v4/locations/{locationId}/listings/duplicates

Duplicate listings for a location

POST

/api/v4/connected-accounts/trigger-matches

Why Jentic?

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

Setup

Wiring the Listings API by hand means choosing between its Authorization header key and the RapidAPI key and host pair, then building nested input objects for each write. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Read operations such as reviews, analytics, and insights put the location id in the URL path (/api/v4/locations/{locationId}/...), so a rule can pin those reads to one location. Updates and review responses carry their ids in the request body, so for writes, rules bound which operations your agent may call, not which location; you choose them, so archiving locations or disconnecting accounts is not included unless you add it.

Credential isolation

Your Listings API 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 'respond to a Google review' or 'update store hours', and Jentic returns the matching Listings API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Listings API through Jentic.

What authentication does the Listings API use?

Per its OpenAPI spec the Listings API accepts either of two options. Directly, send your key from the developer dashboard in the Authorization header as API followed by the key. Through the RapidAPI proxy, send X-RapidAPI-Key together with X-RapidAPI-Host instead. The four day pass operations, which set up a keyless sandbox, need no authentication. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at request time.

Is there a Listings API MCP server?

You don't need an MCP server to give your agent the Listings API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers location, review, and social operations on demand instead of loading a large tool list into its context.

Can I respond to Google reviews with the Listings API?

Yes. The respond operation posts a public reply to a review or interaction on its source platform, taking responseContent and the interactionId. Google Reviews accept a single owner reply per review, so a second response is rejected; use the edit response operation with the responseId, reviewId, and new responseContent to change an existing reply.

Is there a free way to try the Listings API?

The spec describes a sandbox day pass, when offered, that needs no card. Agents can request one with the day pass signup operation, start it with the emailed code, and poll its status. It covers the locations and listings operations and syncs only to demo directories.

What are the rate limits for the Listings API?

The OpenAPI spec does not specify request rate limits. The social limits operation reports your account's social connection cap and its usage for the current billing period, which is a plan allowance rather than a request limit. See https://listingsapi.com/docs for current limits.

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

Yes. For example, write a rule that allows only the interactions list, review analytics, and Google insights reads under /api/v4/locations/1800289/, so the agent can report on that one store while location updates, review responses, and account disconnects stay outside its reach. Every call it makes is logged.

How do I update a location's hours with the Listings API through Jentic?

Search Jentic for 'update business location hours', load the update location operation, and send an input object with the location id and the businessHours you want; only the fields you send change. Jentic injects your key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Listings API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo SemapiKey (Authorization), apiKey (X-RapidAPI-Key + X-RapidAPI-Host)82 EndpointsREST

For Agents

Create and update business locations, sync and de-duplicate their listings, respond to reviews, pull Google, Facebook, and Bing insights, and publish social posts.

Use for: I need to update the opening hours for my Austin store, Respond to the latest one-star Google review, List all reviews for this location from last month, Get the Google insights for this location for September

Not supported: Does not run paid search ads, track keyword rankings, or host websites. Use for managing business location listings, reviews, local insights, and social posts only.

The Listings API manages business locations and keeps their listings in sync across Google, Facebook, Bing, and other publishers. It creates, updates, archives, and searches locations, connects Google and Facebook accounts and matches their listings to locations, flags duplicate listings, and attaches photos. It also pulls reviews, Q&A, and social interactions per location or across many, posts owner responses, reports review analytics and Google, Facebook, and Bing insights, and publishes or schedules social posts to connected Facebook, Instagram, X, LinkedIn, and Pinterest accounts.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

93%

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

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

Example Density

How richly the API is illustrated with examples.

50%

Example Validity

Percentage of examples that conform to their schemas.

74%

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: D+Signals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

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

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Listings API to your agent

Capabilities

Start building with Listings API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Listings API

Jentic AI Readiness Score

Listings 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