Install Jentic One Beta

Connect the RICOH360 Tours API to your agent

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

Execute GraphQL query or mutation

Manage payments data programmatically

Integrate RICOH360 Tours API into automated workflows

Query and filter RICOH360 Tours API records by parameters

Monitor RICOH360 Tours API operational status and events

GET STARTED

Start building with RICOH360 Tours API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use RICOH360 Tours API for, with concrete tasks.

★ Payments Operations

Use the RICOH360 Tours API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query or mutation.

Call POST /graphql to execute graphql query or mutation

Data Retrieval and Monitoring

Query RICOH360 Tours API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary RICOH360 Tours API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call RICOH360 Tours 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 apiKey tokens manually.

Search Jentic for 'execute graphql query or mutation', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — ricoh360 tours graphql api for managing virtual tours, team api keys, and webhook subscriptions.

METHOD

PATH

DESCRIPTION

POST

/graphql

Execute GraphQL query or mutation

POST

/graphql

Execute GraphQL query or mutation

Why Jentic?

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

Setup

Wiring the RICOH360 Tours API by hand means setting its apiKey in the Authorization header, targeting the us-west-2 AppSync GraphQL host, and shaping every request as a GraphQL query or mutation over the single /graphql endpoint. Through Jentic you install once, import the RICOH360 Tours API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

This API exposes one /graphql endpoint where the operation travels in the request body, so scope the agent to the operations it needs rather than a single resource: you decide whether it runs read queries only or is also allowed to send mutations. Every operation the agent can run is one you have added to that allowed set.

Credential isolation

Your RICOH360 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 'run a tours GraphQL query' or 'update tour data', and Jentic returns the matching RICOH360 Tours API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using RICOH360 Tours API through Jentic.

What authentication does the RICOH360 Tours API use?

The RICOH360 Tours API uses an API key passed 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 execute graphql query or mutation with the RICOH360 Tours API?

Yes. Use the POST /graphql endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RICOH360 Tours 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 execute graphql query or mutation through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'execute graphql query or mutation'. Jentic returns the matching RICOH360 Tours API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RICOH360 Tours API have?

The RICOH360 Tours API exposes 1 endpoints covering graphql operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the RICOH360 Tours API operations the agent may call and which stored API key it may use. This API exposes a single POST /graphql endpoint where the operation travels in the request body, so you scope the agent to the specific operations it needs: you decide whether it runs read queries only or is also allowed to send mutations. Every operation the agent can run is one you have added to that allowed set.

RICOH360 Tours API

Name: RICOH360 Tours API
Brand: RICOH360 Tours API
Availability: InStock

AI ReadinessAI-Aware (B)63/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically execute graphql query or mutation. Covers 1 operations with apiKey authentication.

Use for: I need to execute graphql query or mutation, Find available payments operations, Get the current status of RICOH360 Tours API resources, List all records from RICOH360 Tours API

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

RICOH360 Tours GraphQL API for managing virtual tours, team API keys, and webhook subscriptions. AWS AppSync-based GraphQL implementation. The API exposes 1 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

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

24%

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.

50%

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RICOH360 Tours API to your agent

Capabilities

Start building with RICOH360 Tours API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

RICOH360 Tours API

Jentic AI Readiness Score

RICOH360 Tours 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