Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ruuster 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%2Fruuster.com%2Fruuster" | shStep 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%2Fruuster.com%2Fruuster" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Ruuster API.
Look up a listing by mlsRecordId and read its engagement and the viewers who looked at it
Find a lead by email, phone, or crmExternalId and pull its activity timeline and emails
List the most active leads in a date range with a minActions threshold
Report new-lead stats, email stats, and website traffic grouped by period or hostname
Run a comparative market analysis with POST /cma using a propertyId, mlsRecordId, or address
GET STARTED
Subscribe to lead events with webhooks, list deliveries, and replay failed ones
Poll the event feed by kinds and since for systems that cannot receive webhooks
Patterns agents use Ruuster API for, with concrete tasks.
★ Agent follow-up assistant through Jentic
A brokerage wants an AI assistant that tells agents who to call today. Through Jentic the assistant searches for 'list active leads', receives the Ruuster operation with its input schema, and calls GET /leads/activity with from, to, and minActions. For each hot lead it calls GET /leads/{leadId}/activity to see which listings they viewed, then drafts a follow-up note for the assigned agent.
Call GET /leads/activity with from '2026-11-12', to '2026-11-19', and minActions 5, then call GET /leads/{leadId}/activity for the top five leads and summarise the listings each one viewed
Listing engagement reports for sellers
Listing agents send sellers proof that the listing is getting attention. GET /properties/lookup finds the listing by mlsRecordId, GET /properties/{propertyId}/engagement returns engagement over a period with a granularity setting, and GET /properties/{propertyId}/viewers lists who viewed it. GET /properties/engagement compares engagement across all listings.
Call GET /properties/lookup with mlsRecordId '24-118842', then GET /properties/{propertyId}/engagement with from and to for the last 14 days and granularity 'day', and write a short seller update
Comparative market analysis
Before a listing appointment an agent needs comps. POST /cma takes the subject as subject.propertyId, subject.mlsRecordId, or subject.address, accepts overrides for facts like bedrooms, livingArea, and condition, and options such as options.radiusMiles and options.soldWithinMonths. GET /cma/{cmaId} retrieves the finished analysis and GET /cma lists past ones.
Call POST /cma with subject.mlsRecordId '24-118842', overrides bedrooms 4, and options.radiusMiles 1, then call GET /cma/{cmaId} and summarise the comparable sales it returns
Lead-event sync into a CRM
Brokerages push Ruuster lead events into their CRM. POST /webhooks creates a subscription with a url and the events to send, from the kinds listed by GET /webhooks/events. GET /webhooks/{webhookId}/deliveries shows delivery status and POST /webhooks/{webhookId}/replay resends events between from and to, optionally onlyFailed. GET /events offers a polling alternative.
Call GET /webhooks/events, then POST /webhooks with url 'https://example.com/ruuster' and the lead event kinds, and later call POST /webhooks/{webhookId}/replay with from, to, and onlyFailed true
35 endpoints — the ruuster api reports engagement on a real estate brokerage's ruuster-powered sites: who viewed which listings, which leads are active, how agents and emails perform, and how much traffic each site gets.
METHOD
PATH
DESCRIPTION
/leads/activity
List active leads
/leads/{leadId}/activity
Get a lead's activity
/leads/lookup
Find a lead
/properties/{propertyId}/engagement
Get listing engagement
/properties/{propertyId}/viewers
List a listing's viewers
/summary
Get the brokerage summary
/cma
Run a CMA
/webhooks
Create a webhook subscription
/leads/activity
List active leads
/leads/{leadId}/activity
Get a lead's activity
/leads/lookup
Find a lead
/properties/{propertyId}/engagement
Get listing engagement
/properties/{propertyId}/viewers
List a listing's viewers
/summary
Get the brokerage summary
/cma
Run a CMA
/webhooks
Create a webhook subscription
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Ruuster by hand means sending two headers together, x-api-key and x-email, from a server, and paging cursor-based lead and listing lists. Through Jentic you install once, import Ruuster from the API Directory, store the key and email once, and your agent calls it.
Permission scoping
Ruuster puts the listing, lead, and webhook ids in the URL path (/properties/{propertyId}, /leads/{leadId}, /webhooks/{webhookId}), so a rule can bound your agent to the operations and ids you pick. You choose the operations it may call, so ones like deleting a webhook or rotating its signing secret are not included unless you add them.
Credential isolation
Your Ruuster key and login email are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list active leads' or 'get listing engagement', and Jentic returns the matching Ruuster operation with its input schema so the agent calls the right endpoint without reading the docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Ruuster API through Jentic.
What authentication does the Ruuster API use?
The Ruuster API declares two apiKey schemes in its OpenAPI spec that are required together: apiKey, sent in the `x-api-key` header, and email, sent in the `x-email` header with the Ruuster login email the key belongs to. The key must belong to a brokerage owner or admin and is meant for server use. GET /status needs no auth. Through Jentic both values are held by your own Jentic One instance and attached at call time.
Can I run a comparative market analysis with the Ruuster API?
Yes. POST /cma runs a CMA for a subject given as subject.propertyId, subject.mlsRecordId, or subject.address. You can pass overrides for facts such as bedrooms, bathrooms, livingArea, and condition, and options such as options.radiusMiles and options.soldWithinMonths. GET /cma/{cmaId} returns the result and GET /cma lists past analyses.
What are the rate limits for the Ruuster API?
The OpenAPI spec does not specify rate limits. Check the Ruuster API documentation at https://help.ruuster.com/api for current limits.
How do I find a lead's recent activity through Jentic?
Search Jentic for 'find a lead', load GET /leads/lookup, and execute it with the lead's email, phone, or crmExternalId. Then call GET /leads/{leadId}/activity with from and to to see the listings and emails they engaged with. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Ruuster MCP server?
You don't need an MCP server to give your agent Ruuster. Jentic connects it directly from the API Directory: import it, store your key and login email once, and your agent finds the lead, listing, and CMA operations it needs on demand, without loading extra tool definitions into its context.
Can I limit what my agent is allowed to do with the Ruuster API?
Yes. For a reporting assistant, write a rule that allows only GET /leads/activity, GET /leads/{leadId}/activity, and GET /summary. The agent can rank leads and read the brokerage summary but cannot create or delete webhooks, rotate signing secrets, or run CMAs, and each call it makes is logged.
For Agents
Read listing engagement, lead activity, agent, email, and traffic stats for a brokerage's Ruuster sites, subscribe to lead-event webhooks, and run CMAs on a property.
Use for: Show me which leads viewed 123 Main St this week, Find the lead with email jane@example.com and get her recent activity, List all active leads with at least 5 actions in the last 7 days, Get the brokerage summary for last month
Not supported: Does not edit MLS listings, send marketing emails, or act as the brokerage's CRM. Use for reading engagement on Ruuster-powered brokerage sites, lead-event webhooks, and CMAs only.
The Ruuster API reports engagement on a real estate brokerage's Ruuster-powered sites: who viewed which listings, which leads are active, how agents and emails perform, and how much traffic each site gets. Listings can be looked up by MLS number with their engagement and viewers, leads can be found by email, phone, or CRM id with their activity and emails, and a brokerage summary rolls it up by period. Beyond the read-only reporting, webhook subscriptions push lead events, an event feed can be polled, and a CMA endpoint runs comparative market analyses from a listing or address.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>