canonical: https://jentic.com/apis/realscout.com/realscout # RealScout API 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. ## For AI agents Programmatically execute graphql query. Covers 1 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for social media only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'execute graphql query', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/graphql` | Execute GraphQL query | ## Key resources - **GraphQL** — Operations related to GraphQL ## AI readiness 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. - **Score:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 94 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/realscout.com/realscout/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Twitter** — Alternative social media API - **Facebook** — Alternative social media API - **Linkedin** — Complementary social media API ## FAQ ### 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.