canonical: https://jentic.com/apis/paraspot.ai/paraspot # Paraspot API The Paraspot API manages rental property units, tenancies, and the AI-generated inspection reports produced from tenant video scans. It registers and updates units and the properties that group them, issues scan links that tenants use to submit an inspection, and returns the resulting reports with their past scans, inspection type, and resident data. Media operations upload scan videos and mint presigned URLs for chunked upload, and a webhook fires when a new report is generated. ## For AI agents Manage rental property units and tenancies, issue inspection scan links, upload scan videos, and retrieve the AI-generated inspection reports. Authenticates with a bearer token. ## Scope Does not handle rent collection, payment processing, or property listing and marketing. Use for property unit, tenancy, and inspection report management only. ## Capabilities - Register and update property units and generate inspection scan links - Create and update tenancies tied to a property unit - Retrieve inspection reports and their past scans for a unit - Update a report's inspection type and the resident data attached to it - Upload scan videos and request presigned URLs for chunked media upload - Track scan status and receive a webhook when a new report is generated ## Use cases ### AI Agent Inspection Workflow An AI agent coordinating move-in and move-out inspections can create a unit, issue a scan link, and pull the resulting report through Jentic. The agent searches for each operation, supplies the unit and tenancy details, and advances the workflow, without the developer wiring the bearer token or reading the Paraspot reference docs. Example prompt: Call POST `/units/generate_scan_link` to issue a scan link for a unit, then GET `/reports/get_all` to list its reports ### Report Retrieval and Review Property managers review the AI-generated condition reports produced from tenant scans. The report operations return a report's main details, list the past scans behind it, and let a manager set the inspection type, so a dashboard can show the latest inspection and its history for each unit. Example prompt: Call GET `/reports/get` to read a report's details, then GET `/reports/get_past_scans` for its scan history ### Portfolio and Tenancy Setup Onboarding a new building means registering its properties and units and attaching tenancies. Paraspot lists and creates properties, creates units beneath them, and records tenancies, so an agent can stand up a portfolio before the first inspection is scheduled. Example prompt: Call POST `/properties/create` to add a property, then POST `/units/new` to add a unit to it ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/units/list` | List units | | POST | `/units/new` | Create a new unit | | POST | `/units/generate_scan_link` | Generate a scan link for a unit | | GET | `/reports/get_all` | List all reports for a unit | | GET | `/reports/get` | Get report main details | | GET | `/reports/get_past_scans` | List past scans for a report | | POST | `/tenancies/create` | Create a tenancy | | GET | `/properties/list` | List properties | ## Key resources - **Units** — Property units with scan-link generation and inspection submission links - **Reports** — Inspection reports, past scans, inspection type, and resident data - **Scan and Media** — Scan status, video upload, and presigned upload URLs - **Properties and Tenancies** — Properties that group units, and the tenancy records attached to them ## 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:** 53 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 64 / 100 - Developer Experience & Jentic Compatibility: 82 / 100 - AI-Readiness & Agent Experience: 28 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 62 / 100 - **View full report:** https://jentic.com/apis/paraspot.ai/paraspot/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 Paraspot API by hand means sending its bearer token, generating scan links, and uploading inspection videos through presigned URLs yourself. Through Jentic you install once, import Paraspot from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** You choose the exact Paraspot operations a rule allows, such as listing units and retrieving reports, so write operations like removing a unit or a property stay out of reach. The agent can read and advance inspections within that set and nothing beyond it. - **Credential handling:** Your Paraspot bearer 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 'generate an inspection scan link' or 'get an inspection report', and Jentic returns the matching Paraspot operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **SimplyRETS** — Real estate listing data from MLS feeds - **Zenlist** — Real estate search and client collaboration - **Cloudinary Upload** — Media upload and transformation for images and video ## FAQ ### What authentication does the Paraspot API use? The Paraspot API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context. ### Can I retrieve inspection reports with the Paraspot API? Yes. The report operations return a report's main details and the past scans behind it, and you can list every report tied to a unit. The inspection type and resident data on a report can be updated through their own operations. ### What are the rate limits for the Paraspot API? The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://www.paraspot.ai for the limits that apply to your account tier. ### How do I run an inspection workflow with the Paraspot API through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import Paraspot from the API Directory, and store your bearer token once. Your agent then searches for an intent such as 'generate an inspection scan link', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a Paraspot MCP server? You do not need an MCP server to give your agent the Paraspot API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the unit, report, and media operations on demand, which keeps your agent's context free of an extra server's tool definitions. ### Can I limit what my agent is allowed to do with the Paraspot API? Yes. Paraspot has write operations like creating and removing units and properties, so you can allow your agent only the ones a task needs, such as listing units and reading reports, while leaving out removing a unit or a property. Because you run Jentic One yourself, the agent reads inspection data but cannot delete records unless you add those operations, and every call is logged.