Install Jentic One Beta

Connect the Showdigs API to your agent

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

Check location coverage

List all units

Get specific unit

Create listing for unit

Update listing

Use Cases

GET STARTED

Start building with Showdigs API

Explore with Jentic One

View OpenAPI Document

Automated Coverage Management

Automate coverage operations by combining multiple Showdigs API endpoints. Agents can list all units and then get specific unit in a single workflow.

Call GET /api/v1/units to list all units, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Showdigs API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'check location coverage', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

16 endpoints — api for showdigs property showing and listing management platform.

METHOD

PATH

DESCRIPTION

GET

/api/v1/coverage

Check location coverage

GET

/api/v1/units

List all units

GET

/api/v1/units/{uuid}

Get specific unit

POST

/api/v1/units/{uuid}/listing

Create listing for unit

PUT

/api/v1/units/{uuid}/listing

Update listing

GET

/api/v1/listings

Get all active listings

GET

/api/v1/listings/{uuid}

Get specific listing

DELETE

/api/v1/listings/{uuid}

Deactivate listing

GET

/api/v1/coverage

Check location coverage

GET

/api/v1/units

List all units

GET

/api/v1/units/{uuid}

Get specific unit

POST

/api/v1/units/{uuid}/listing

Create listing for unit

PUT

/api/v1/units/{uuid}/listing

Update listing

GET

/api/v1/listings

Get all active listings

GET

/api/v1/listings/{uuid}

Get specific listing

DELETE

/api/v1/listings/{uuid}

Deactivate listing

Why Jentic?

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

Setup

Wiring the Showdigs API by hand means sending your bearer token on every request against api.showdigs.com and parsing its coverage, unit, and listing responses yourself. Through Jentic you install once, import the Showdigs API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Showdigs puts the unit and listing id in the URL path (/api/v1/units/{uuid}, /api/v1/listings/{uuid}), so a rule can pin your agent to one unit or listing: it can read that unit and manage its listing and nothing else. You choose the operations it may call, so destructive ones like listing deletion are not included unless you add them.

Credential isolation

Your Showdigs 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 'check location coverage' or 'create a listing for a unit', and Jentic returns the matching Showdigs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Showdigs API through Jentic.

What authentication does the Showdigs API use?

The Showdigs API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I check location coverage with the Showdigs API?

Yes. Use the GET /api/v1/coverage endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Showdigs API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I check location coverage through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check location coverage'. Jentic returns the matching Showdigs API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Showdigs API have?

The Showdigs API exposes 16 endpoints covering coverage, units, listings operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Showdigs operations and credentials the agent may use. Since Showdigs puts the unit and listing id in the URL path (/api/v1/units/{uuid} and /api/v1/listings/{uuid}), you can pin the agent to a single unit or listing so it reads that unit and manages its listing and nothing else. You also choose which operations it may call, so destructive ones like DELETE /api/v1/listings/{uuid} stay out of reach unless you add them.

Showdigs API

Name: Showdigs API
Brand: Showdigs API
Availability: InStock

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontbearer16 EndpointsREST

For Agents

Programmatically check location coverage, list all units. Covers 16 operations with bearer authentication.

Use for: I need to check location coverage, I want to all units, Search for specific unit, Find all listing for unit

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

API for Showdigs property showing and listing management platform. The API exposes 16 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

50%

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.

50%

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

73%

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.

53%

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

60%

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 Showdigs API to your agent

Capabilities

Use Cases

Start building with Showdigs API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Showdigs API

Jentic AI Readiness Score

Showdigs 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