Install Jentic One Beta

Connect the MayiStay API to your agent

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

Search the renter database to find a candidate before accepting a booking

Retrieve detailed reputation history for a specific renter

Submit a new anonymous review of a renter after a stay

Pull past reviews left by other RV park owners

Log a confirmed booking against a renter profile

GET STARTED

Start building with MayiStay API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MayiStay API for, with concrete tasks.

★ Pre-Booking Renter Screening

Screen incoming RV park booking enquiries against the MayiStay community database before confirming a stay. The /wf/search endpoint returns matching renter records and /wf/renter_details surfaces aggregated rating history left by other park owners, so the operator can spot repeat problem guests before they arrive. This complements but does not replace standard reservation systems.

Search /wf/search for the renter named 'Jane Smith', then call /wf/renter_details for the top match and return the average rating plus any reviews from the last 12 months.

Post-Stay Review Submission

After a renter checks out, post an anonymous review describing behaviour, condition of the site on departure, and a numeric rating. The /wf/leave_a_review endpoint records the review against the renter profile so future park owners can factor it into their screening. Reviews are anonymous to the renter but attributed to the park owner inside the MayiStay community.

Submit a review for renter_id 9876 with rating=2, summary='Left site in poor condition', and stay_dates covering last week, then return the new review id.

Booking Audit Trail

Record each confirmed booking against the renter profile so the community database accumulates a longitudinal view of where each renter has stayed. The /wf/booking_renter endpoint accepts the renter id, park id, and stay dates, building a footprint that supports future screening decisions and dispute resolution.

Log a booking for renter_id 9876 at park_id 42 from 2026-07-01 to 2026-07-08 and return the booking record.

AI Agent for Reservation Triage

Build an agent that intercepts new reservation requests, searches MayiStay for the renter, retrieves their detailed reputation, and posts a recommendation back to the park manager's inbox. The agent searches Jentic for 'check RV renter reputation', loads the schema for the search and detail endpoints, and executes the calls with vault credentials. The output is a one-paragraph triage note saving manual lookup time on every booking.

Given a reservation request with guest name 'John Doe', search MayiStay, fetch detailed history of the top match, and return a recommendation of 'approve', 'review', or 'decline' based on the average rating and last review date.

Key Endpoints

6 endpoints — mayistay is an rv park rating service that lets park owners look up renters, post anonymous ratings, and search a community-maintained reputation database before accepting a booking.

METHOD

PATH

DESCRIPTION

GET

/wf/me

Get the authenticated park owner's account

GET

/wf/search

Search the renter database

GET

/wf/renter_details

Get detailed renter rating history

POST

/wf/leave_a_review

Submit an anonymous review of a renter

GET

/wf/past_reviews

List past reviews

POST

/wf/booking_renter

Log a confirmed booking against a renter

GET

/wf/me

Get the authenticated park owner's account

GET

/wf/search

Search the renter database

GET

/wf/renter_details

Get detailed renter rating history

POST

/wf/leave_a_review

Submit an anonymous review of a renter

GET

/wf/past_reviews

List past reviews

POST

/wf/booking_renter

Log a confirmed booking against a renter

Why Jentic?

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

Setup

Wiring the MayiStay API by hand means sending your key in the Authorization header, pointing at the mayistay.com host, and mapping the reputation and review calls yourself. Through Jentic you install once, import the MayiStay API from the API Directory, store the key once, and your agent calls it.

Permission scoping

MayiStay's review and booking targets travel in the request body or query rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as searching renters and checking reputation. It calls only the operations you allow, so writing a review is not included unless you add it.

Credential isolation

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

Intent-based discovery

Agents search Jentic by intent such as 'check an RV renter's reputation', and Jentic returns the matching MayiStay operation with its input schema so the agent calls the right endpoint without browsing the MayiStay docs.

FAQs

Specific to using MayiStay API through Jentic.

What authentication does the MayiStay API use?

MayiStay uses an API key passed in the Authorization header. Through Jentic, the key is stored encrypted in your Jentic One instance and attached to outbound requests at execution time, so the raw key never enters the agent's prompt or transcript.

Can I search for renters with the MayiStay API?

Yes. GET /wf/search returns matching renter records based on the supplied query, and GET /wf/renter_details fetches the aggregated reputation history for a specific renter id. These two endpoints together cover the core screening workflow.

What are the rate limits for the MayiStay API?

MayiStay does not publish an explicit rate-limit table; the API is designed for low-volume park-management workflows rather than bulk lookups. Expect sub-second responses for individual searches and respect any 429 responses returned during high-traffic periods.

How do I leave a review for a renter through Jentic?

Search Jentic for 'leave an RV renter review', load the schema for POST /wf/leave_a_review, and execute with the renter id, rating, and summary. Jentic attaches the API-key Authorization header automatically and returns the new review id.

Are MayiStay reviews anonymous to the renter?

Yes. Reviews are attributed to the submitting park owner inside the MayiStay community but the renter cannot see who left a specific review. This is the design intent of the platform - to let owners share candid feedback without fear of retaliation.

Can I log a booking with the MayiStay API?

Yes. POST /wf/booking_renter records a confirmed booking linking a renter to a park with stay dates. Use this after a reservation is confirmed so the renter's stay history accumulates across parks for future screening.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which MayiStay operations and credentials your agent may use. You can allow read-only screening, such as GET /wf/search and GET /wf/renter_details, while withholding write operations like POST /wf/leave_a_review or POST /wf/booking_renter. The agent calls only the operations you permit, so it cannot submit a review or log a booking unless you explicitly grant those.

MayiStay API

Name: MayiStay API
Brand: MayiStay API
Availability: InStock

Community OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search RV renter reputation, leave anonymous ratings, and check past reviews before accepting a booking. Built for RV park owners to share renter intelligence.

Use for: I need to look up a renter's reputation before accepting their booking, Search for an RV renter by name, Submit an anonymous review after a guest checks out, Retrieve all past reviews left for a specific renter

Not supported: Does not handle reservation booking, payment collection, or property listings - use for RV renter reputation screening and review submission only.

MayiStay is an RV park rating service that lets park owners look up renters, post anonymous ratings, and search a community-maintained reputation database before accepting a booking. The API exposes six endpoints covering current account info, renter search, renter detail lookup, leaving a new review, retrieving past reviews, and recording a renter booking. It is purpose-built for RV park managers who want to share renter behaviour signals across operators.

Jentic One on Github View OpenAPI Document

Connect the MayiStay API to your agent

Capabilities

Start building with MayiStay API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MayiStay API