Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RealScout 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%2Frealscout.com%2Frealscout" | 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%2Frealscout.com%2Frealscout" | 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 RealScout API.
Execute GraphQL query
Access RealScout API social media resources via REST API
Query RealScout API endpoints with structured JSON responses
Authenticate requests with bearer credentials managed by Jentic
Access RealScout API resources programmatically via REST
GET STARTED
Patterns agents use RealScout API for, with concrete tasks.
★ Social Media Operations
Use the RealScout API to perform social media operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query.
Call POST /graphql to execute graphql query
Data Retrieval and Monitoring
Query RealScout API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows.
Query the RealScout API API to retrieve current data and verify the response structure
AI Agent Integration via Jentic
AI agents discover and call RealScout 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 'execute graphql query', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — realscout graphql api for managing real estate brokerages, agents, and homebuyers.
METHOD
PATH
DESCRIPTION
/graphql
Execute GraphQL query
/graphql
Execute GraphQL query
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the RealScout API by hand means setting up its bearer auth and composing GraphQL queries and variables in the request body for the single /graphql endpoint yourself. Through Jentic you install once, import the RealScout API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The RealScout API exposes one POST /graphql operation with the query in the request body, so you limit the agent to the GraphQL operation it needs. It only calls the operation you allow, so it runs the queries you intend and reaches no other service.
Credential isolation
Your RealScout API 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 'run a GraphQL query for listings', and Jentic returns the matching RealScout API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using RealScout API through Jentic.
What authentication does the RealScout API use?
The RealScout 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 execute graphql query with the RealScout 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 RealScout 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 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'. Jentic returns the matching RealScout API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the RealScout API have?
The RealScout API exposes 1 endpoints covering graphql operations.
Can I limit what my agent is allowed to do with the RealScout API?
Yes. The RealScout API exposes a single POST /graphql operation, and because you run your own self-hosted Jentic One instance, your rules decide whether the agent may call it at all. You allow only the GraphQL operation the agent needs, so it runs the queries you intend and reaches no other service. Jentic One also holds your bearer token encrypted and injects it at execution time, so the agent never sees the raw credential.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically execute graphql query. Covers 1 operations with bearer authentication.
Use for: I need to execute graphql query, I want to integrate RealScout API into my workflow, Search for available RealScout API operations, Get the API schema for RealScout API
Not supported: Does not handle payments, communications, or crm - use for social media only.
RealScout GraphQL API for managing real estate brokerages, agents, and homebuyers. This is a GraphQL API accessible via a single POST endpoint. The API exposes 1 endpoints secured with bearer authentication.
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>